Since updating pam from v1.1.0 to stable version 1.1.1-r2 pam complains about a faulty module /lib/security/pam_cracklib.so in /var/log/messages when I log on to my system. Reproducible: Always Steps to Reproduce: 1.Log on using KDE 4.4.5 2.Check last messages in /var/log/messages 3. Actual Results: Each time I log on I found the following entries in /var/log/messages: Jul 30 18:14:59 frodo kdm: :0[25350]: PAM unable to dlopen(/lib/security/pam_cracklib.so): /lib/libpam.so.0: version `LIBPAM_EXTENSION_1.1.1' not found (required by /lib/security/pam_cracklib.so) Jul 30 18:14:59 frodo kdm: :0[25350]: PAM adding faulty module: /lib/security/pam_cracklib.so Expected Results: No messages in /var/log/messages All libs (/lib/security/pam_cracklib.so, /lib/libpam.so.0 and /lib/libpam.so.0.82.2) belong to the PAM package. All the files are there and world readable: -rwxr-xr-x 1 root root 13528 Jul 29 07:07 /lib/security/pam_cracklib.so lrwxrwxrwx 1 root root 16 Jul 29 07:07 /lib/libpam.so.0 -> libpam.so.0.82.2 -rwxr-xr-x 1 root root 46540 Jul 29 07:07 /lib/libpam.so.0.82.2
Could you attach build log and check 'readelf -V /lib/libpam.so.0' ?
(In reply to comment #1) > Could you attach build log and check 'readelf -V /lib/libpam.so.0' ? ~ # readelf -V /lib/libpam.so.0 Version symbols section '.gnu.version' contains 93 entries: Addr: 0000000000001280 Offset: 0x001280 Link: 3 (.dynsym) 000: 0 (*local*) 8 (GLIBC_2.0) 9 (GLIBC_2.1.2) 0 (*local*) 004: 0 (*local*) 8 (GLIBC_2.0) a (GLIBC_2.2) 8 (GLIBC_2.0) 008: 8 (GLIBC_2.0) 8 (GLIBC_2.0) 8 (GLIBC_2.0) 8 (GLIBC_2.0) 00c: b (GLIBC_2.0) 9 (GLIBC_2.1.2) 8 (GLIBC_2.0) c (GLIBC_2.2.4) 010: d (GLIBC_2.1) 8 (GLIBC_2.0) 8 (GLIBC_2.0) 8 (GLIBC_2.0) 014: 8 (GLIBC_2.0) b (GLIBC_2.0) e (GLIBC_2.8) f (GLIBC_2.3) 018: d (GLIBC_2.1) 8 (GLIBC_2.0) 8 (GLIBC_2.0) 9 (GLIBC_2.1.2) 01c: 8 (GLIBC_2.0) 10 (GLIBC_2.1) 8 (GLIBC_2.0) 11 (GLIBC_2.4) 020: 9 (GLIBC_2.1.2) 8 (GLIBC_2.0) 8 (GLIBC_2.0) 8 (GLIBC_2.0) 024: 8 (GLIBC_2.0) b (GLIBC_2.0) 8 (GLIBC_2.0) 8 (GLIBC_2.0) 028: f (GLIBC_2.3) 8 (GLIBC_2.0) 12 (GLIBC_2.3.4) 8 (GLIBC_2.0) 02c: 8 (GLIBC_2.0) 9 (GLIBC_2.1.2) 8 (GLIBC_2.0) 13 (GLIBC_2.1.3) 030: e (GLIBC_2.8) 6 (LIBPAM_MODUTIL_1.0) 2 (LIBPAM_1.0) 2 (LIBPAM_1.0) 034: 6 (LIBPAM_MODUTIL_1.0) 3 (LIBPAM_EXTENSION_1.0) 4 (LIBPAM_EXTENSION_1.1) 5 (LIBPAM_EXTENSION_1.1.1) 038: 2 (LIBPAM_1.0) 2 (LIBPAM_1.0) 3 (LIBPAM_EXTENSION_1.0) 2 (LIBPAM_1.0) 03c: 6 (LIBPAM_MODUTIL_1.0) 3 (LIBPAM_EXTENSION_1.0) 2 (LIBPAM_1.0) 4 (LIBPAM_EXTENSION_1.1) 040: 6 (LIBPAM_MODUTIL_1.0) 6 (LIBPAM_MODUTIL_1.0) 2 (LIBPAM_1.0) 2 (LIBPAM_1.0) 044: 2 (LIBPAM_1.0) 6 (LIBPAM_MODUTIL_1.0) 2 (LIBPAM_1.0) 2 (LIBPAM_1.0) 048: 7 (LIBPAM_MODUTIL_1.1) 6 (LIBPAM_MODUTIL_1.0) 7 (LIBPAM_MODUTIL_1.1) 3 (LIBPAM_EXTENSION_1.0) 04c: 6 (LIBPAM_MODUTIL_1.0) 2 (LIBPAM_1.0) 6 (LIBPAM_MODUTIL_1.0) 5 (LIBPAM_EXTENSION_1.1.1) 050: 2 (LIBPAM_1.0) 2 (LIBPAM_1.0) 2 (LIBPAM_1.0) 2 (LIBPAM_1.0) 054: 2 (LIBPAM_1.0) 2 (LIBPAM_1.0) 6 (LIBPAM_MODUTIL_1.0) 3 (LIBPAM_EXTENSION_1.0) 058: 6 (LIBPAM_MODUTIL_1.0) 6 (LIBPAM_MODUTIL_1.0) 2 (LIBPAM_1.0) 5 (LIBPAM_EXTENSION_1.1.1) 05c: 6 (LIBPAM_MODUTIL_1.0) Version definition section '.gnu.version_d' contains 7 entries: Addr: 0x000000000000133c Offset: 0x00133c Link: 4 (.dynstr) 000000: Rev: 1 Flags: BASE Index: 1 Cnt: 1 Name: libpam.so.0 0x001c: Rev: 1 Flags: none Index: 2 Cnt: 1 Name: LIBPAM_1.0 0x0038: Rev: 1 Flags: none Index: 3 Cnt: 1 Name: LIBPAM_EXTENSION_1.0 0x0054: Rev: 1 Flags: none Index: 4 Cnt: 2 Name: LIBPAM_EXTENSION_1.1 0x0070: Parent 1: LIBPAM_EXTENSION_1.0 0x0078: Rev: 1 Flags: none Index: 5 Cnt: 2 Name: LIBPAM_EXTENSION_1.1.1 0x0094: Parent 1: LIBPAM_EXTENSION_1.1 0x009c: Rev: 1 Flags: none Index: 6 Cnt: 1 Name: LIBPAM_MODUTIL_1.0 0x00b8: Rev: 1 Flags: none Index: 7 Cnt: 2 Name: LIBPAM_MODUTIL_1.1 0x00d4: Parent 1: LIBPAM_MODUTIL_1.0 Version needs section '.gnu.version_r' contains 2 entries: Addr: 0x0000000000001418 Offset: 0x001418 Link: 4 (.dynstr) 000000: Version: 1 File: libdl.so.2 Cnt: 2 0x0010: Name: GLIBC_2.1 Flags: none Version: 16 0x0020: Name: GLIBC_2.0 Flags: none Version: 11 0x0030: Version: 1 File: libc.so.6 Cnt: 10 0x0040: Name: GLIBC_2.1.3 Flags: none Version: 19 0x0050: Name: GLIBC_2.3.4 Flags: none Version: 18 0x0060: Name: GLIBC_2.4 Flags: none Version: 17 0x0070: Name: GLIBC_2.3 Flags: none Version: 15 0x0080: Name: GLIBC_2.8 Flags: none Version: 14 0x0090: Name: GLIBC_2.1 Flags: none Version: 13 0x00a0: Name: GLIBC_2.2.4 Flags: none Version: 12 0x00b0: Name: GLIBC_2.2 Flags: none Version: 10 0x00c0: Name: GLIBC_2.1.2 Flags: none Version: 9 0x00d0: Name: GLIBC_2.0 Flags: none Version: 8
Created attachment 240753 [details] Build log
Created attachment 240755 [details] emerge --info
Okay now the tricky question: did you restart xdm/kdm after updating PAM?
(In reply to comment #5) > Okay now the tricky question: did you restart xdm/kdm after updating PAM? Ahem... no. The postinstall didn't tell me to do so. And my system is running 24/7. Just logged off and restarted xdm. Problem is gone. Thanks !
Thanks, I'll add a postinst message, actually gdm works because it has a two-stage startup, so the PAM libraries are reloaded between logins, as it happens with login(1); I suspected KDM didn't do so, but I wasn't sure.
Diego, the message you provide to users misses a lot of broken things. See: http://pastebin.com/Ua6K1HV4 This is after I restarted fcron, which was also broken by the upgrade. Due to the pervasive nature of the breakage, I think this is one of those times where sysadmins should have been advised that a reboot is required, unless there is some other graceful way to handle this. I am sure you agree that it is NOT ok to have daemons silently break on production systems after an upgrade. And when /bin/login and sshd is affected, there is not always going to be a quick fix beyond rebooting the box.
lsof(8) changed some details, now the command to be run is slightly different, just updating the syntax now. But PLEASE next time OPEN A NEW BUG.
