Bug 353921 – possible cron problem after glibc-2.13 upgrade

• Status: RESOLVED INVALID
• Product: Gentoo Linux

[Description Harris Landgarten 2011-02-07 04:49:23 UTC]

Since the glibc-2.13 upgrade I have been seeing these log messages every 20 min:

Feb  6 23:40:01  cron[28626]: PAM unable to dlopen(/lib64/security/pam_unix.so): /lib/libnsl.so.1: symbol __libc_rpc_getport, version GL
IBC_PRIVATE not defined in file libc.so.6 with link time reference
Feb  6 23:40:01  cron[28626]: PAM adding faulty module: /lib64/security/pam_unix.so
Feb  6 23:40:01  cron[28626]: Module is unknown

So far I haven't seen a negative effect on operation.


Reproducible: Always

[Comment 1 Harris Landgarten 2011-02-07 15:30:08 UTC]

I can now verify that no cron jobs are being run. Vixie-cron fails everytime a job is run with the log entries shown. I am changing severity to critical.

[Comment 2 Allan Gottlieb 2011-02-07 16:39:12 UTC]

(In reply to comment #1)
> I can now verify that no cron jobs are being run. Vixie-cron fails everytime a
> job is run with the log entries shown. I am changing severity to critical.
> 
Are you prelinking?  Apparently, glibc-2.13 doesn't play with prelinking.
I upgraded glibc as well, but do not prelink and my vixie-cron is working fine.
If you are prelinking, I would suggest reading those bugs.  If not prelinking
then you have hit a new problem.  Good luck.

[Comment 3 Harris Landgarten 2011-02-07 18:14:35 UTC]

No prelinking

[Comment 4 Harris Landgarten 2011-02-07 18:18:58 UTC]

Seems to be related to pam as the log entry says pam cannot open pam_unix.so because a symbol in libnsl.so.1 is not defined in libc.so.6

Also could be a bug in the new glibc

[Comment 5 Harris Landgarten 2011-02-08 02:01:02 UTC]

Problem resolved by restarting Vixie-cron. Evidently it still had the old libc.so.6 cached.