Just noticed the following warning in the mail logs. Postfix seems to still be working but I have not seen this before.
Feb 26 16:39:57 server postfix/postfix-script[29781]: warning: /var/spool/postfix/lib/x86_64-linux-gnu/libnss_nis-2.13.so and /lib/x86_64-linux-gnu/libnss_nis-2.13.so differ
Feb 26 16:39:57 server postfix/postfix-script[29783]: warning: /var/spool/postfix/lib/x86_64-linux-gnu/libnss_hesiod-2.13.so and /lib/x86_64-linux-gnu/libnss_hesiod-2.13.so differ
Feb 26 16:39:57 server postfix/postfix-script[29785]: warning: /var/spool/postfix/lib/x86_64-linux-gnu/libnss_files-2.13.so and /lib/x86_64-linux-gnu/libnss_files-2.13.so differ
Feb 26 16:39:57 server postfix/postfix-script[29787]: warning: /var/spool/postfix/lib/x86_64-linux-gnu/libnss_compat-2.13.so and /lib/x86_64-linux-gnu/libnss_compat-2.13.so differ
Feb 26 16:39:57 server postfix/postfix-script[29789]: warning: /var/spool/postfix/lib/x86_64-linux-gnu/libnss_nisplus-2.13.so and /lib/x86_64-linux-gnu/libnss_nisplus-2.13.so differ
Feb 26 16:39:57 server postfix/postfix-script[29791]: warning: /var/spool/postfix/lib/x86_64-linux-gnu/libresolv-2.13.so and /lib/x86_64-linux-gnu/libresolv-2.13.so differ
Feb 26 16:39:57 server postfix/postfix-script[29794]: warning: /var/spool/postfix/lib/x86_64-linux-gnu/libnss_dns-2.13.so and /lib/x86_64-linux-gnu/libnss_dns-2.13.so differ
Tried a restart of postfix and its still giving the same errors. FYI the other 2 one pro and another gpl are all ok. So is just one server with this issue.
It’s tough to understand exactly what’s going on there due to the different language, but it does appear that the user experiencing that problem just manually copied the libraries over that were causing a problem to resolve the issue.
You can certainly give that a try – copy the libraries in question from /lib over to /var/spool/postfix/lib/, I do suspect that’ll fix it.
However, in theory that’s what restarting Postfix should do, I’m not quite sure why that’s not occurring automatically.
Just for anyone in the future. I ending up rebooting the server and the problem above has been fixed. So Eric you were right with what you said, it just needed something a but more brutal. A postfix restart didnt do it a reboot did.