Bug 175929

Summary: pam-0.99.2.1-1 is broken (version LIBPAM_EXTENSION_1.0 not defined)
Product: [Fedora] Fedora Reporter: Reuben Farrelly <reuben-redhatbugzilla>
Component: pamAssignee: Tomas Mraz <tmraz>
Status: CLOSED RAWHIDE QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: pam-0.99.2.1-2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-12-16 22:42:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Reuben Farrelly 2005-12-16 13:40:13 UTC 
Something is wrong with the latest pam in rawhide.  After updating it I can no
longer log in, and this is logged:

Dec 17 02:31:43 tornado dovecot-auth: PAM [dlerror: /lib/security/pam_unix.so: s
ymbol pam_syslog, version LIBPAM_EXTENSION_1.0 not defined in file libpam.so.0 w
ith link time reference]
Dec 17 02:31:43 tornado dovecot-auth: PAM unable to dlopen(/lib/security/pam_uni
x.so)
Dec 17 02:31:43 tornado dovecot-auth: PAM [dlerror: /lib/security/pam_unix.so: s
ymbol pam_syslog, version LIBPAM_EXTENSION_1.0 not defined in file libpam.so.0 w
ith link time reference]
Dec 17 02:31:43 tornado dovecot-auth: PAM adding faulty module: /lib/security/pa
m_unix.so
Dec 17 02:31:43 tornado dovecot-auth: PAM adding faulty module: /lib/security/pa
m_unix.so
Dec 17 02:31:43 tornado dovecot-auth: PAM unable to dlopen(/lib/security/pam_lim
its.so)
Dec 17 02:31:43 tornado dovecot-auth: PAM unable to dlopen(/lib/security/pam_lim
its.so)
Dec 17 02:31:43 tornado dovecot-auth: PAM [dlerror: /lib/security/pam_limits.so:
 symbol pam_syslog, version LIBPAM_EXTENSION_1.0 not defined in file libpam.so.0
 with link time reference]
Dec 17 02:31:43 tornado dovecot-auth: PAM [dlerror: /lib/security/pam_limits.so:
 symbol pam_syslog, version LIBPAM_EXTENSION_1.0 not defined in file libpam.so.0
 with link time reference]

Also noted after the upgrade:

ls -la /usr/lib/libpam*
lrwxrwxrwx 1 root root 24 Dec 17 02:41 /usr/lib/libpamc.so ->
../../lib/libpamc.so.*.*
lrwxrwxrwx 1 root root 28 Dec 17 02:41 /usr/lib/libpam_misc.so ->
../../lib/libpam_misc.so.*.*
lrwxrwxrwx 1 root root 23 Dec 17 02:41 /usr/lib/libpam.so -> ../../lib/libpam.so.*.*

These are all now broken links (which may or may not be significant but is a bug
nonetheless...)

Reverting to the old version (0.80) from before todays' rawhide update works
around the problem.
Comment 1 Tomas Mraz 2005-12-16 13:56:03 UTC 
The first thing is a little strange - probably the symlinks did not get updated
on upgrade? Where /lib/lipam*.so.0 points to?
Also if you run ldconfig manually, does it help?

The second thing is a clear bug, I'm just fixing that.
Comment 2 Reuben Farrelly 2005-12-16 14:00:54 UTC 
Rerunning ldconfig manually makes no difference, I'm still left with dangling
symlinks.

The /lib/libpam stuff points to here..

[root@tornado packages]# ls -la /lib/libpam*
lrwxrwxrwx 1 root root    17 Dec 17 03:00 /lib/libpamc.so.0 -> libpamc.so.0.81.0
-rwxr-xr-x 1 root root  9900 Dec 16 13:05 /lib/libpamc.so.0.81.0
lrwxrwxrwx 1 root root    21 Dec 17 03:00 /lib/libpam_misc.so.0 ->
libpam_misc.so.0.81.1
-rwxr-xr-x 1 root root  8804 Dec 16 13:05 /lib/libpam_misc.so.0.81.1
lrwxrwxrwx 1 root root    16 Dec 17 03:00 /lib/libpam.so.0 -> libpam.so.0.81.1
-rwxr-xr-x 1 root root 43204 Dec 16 13:05 /lib/libpam.so.0.81.1
[root@tornado packages]#

Not sure quite why the new version 0.99 refers to files of 0.81.0 however these
are the ones in the RPM itself.
Comment 3 Tomas Mraz 2005-12-16 14:37:05 UTC 
That's strange, have you verified that the login still doesn't work?
Also have you restarted dovecot after the upgrade?

The dangling symlinks of course cannot be fixed by ldconfig as they are a real bug.
Comment 4 Reuben Farrelly 2005-12-16 22:35:18 UTC 
Ok it looks like each application needing PAM support requires a reload.  I
restarted a handful manually and they are all OK now.
Probably a matter of good luck that I've not had to do this before, so it looks
like no real bug here afterall.
Comment 5 Tomas Mraz 2005-12-16 22:42:29 UTC 
It isn't necessary after every pam update but this time we went to much
different version so it was required.

The dangling symlinks problem should be resolved in pam-0.99.2.1-2.