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: 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: 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: 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: 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: 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: 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: 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
Any ideas what has happened ?
Hmm, what distro/version is it that you’re using there?
Sorry should have added that. Debian 7 and its the gpl version 4.14 on this server.
Im just going to head off and check the other 3 now to see if the same thing is happening.
Hmm, that is an odd issue.
You may want to try restarting Postfix to see if that resolves the issue.
I believe Debian 7 is one of the systems that puts Postfix into a chroot, and sync’s some files from the main system to that chroot as it’s started.
Stopping and then re-starting Postfix should force a re-sync of those files.
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.
Any other ideas
I found this page and translated it. But since I’m not smart enough to truly know if this is the same thing, can you take a look and let me know.
Its in German sorry.
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.
Thanks for the help yet again.
This seems like some kind of bug in the way postfix gets its upgrades.