Bug 20146 - gdm failes with pam configured to use LDAP
gdm failes with pam configured to use LDAP
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: gdm (Show other bugs)
6.2
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Havoc Pennington
Aaron Brown
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-11-01 10:12 EST by Need Real Name
Modified: 2007-04-18 12:29 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-11-01 15:35:47 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2000-11-01 10:12:43 EST
Says "No such file or directory" but it is definately there... 
gdm doesn't have libcrypt linked, but almost everything else does.
All other pam-enabled programs seem to be working fine with ldap.
Using gdm-2.0beta4-0_helix_7 (ok..its not supplied by rh...but I checked
the RH 6.2 shipped ones and that doesn't have libcrypt linked either)

From /var/log/messages:

Nov  1 15:13:48 wilf gdm[1658]: PAM unable to
dlopen(/lib/security/pam_ldap.so)
Nov  1 15:13:48 wilf gdm[1658]: PAM [dlerror: libldap.so.1: cannot open
shared object file: No such file or directory]
Nov  1 15:13:48 wilf gdm[1658]: PAM adding faulty module:
/lib/security/pam_ldap.so
Nov  1 15:13:48 wilf gdm[1658]: PAM unable to
dlopen(/lib/security/pam_unix_auth.so)
Nov  1 15:13:48 wilf gdm[1658]: PAM [dlerror:
/lib/security/pam_unix_auth.so: undefined symbol: crypt, version GLIBC_2.0]
Nov  1 15:13:48 wilf gdm[1658]: PAM adding faulty module:
/lib/security/pam_unix_auth.so
Nov  1 15:13:48 wilf gdm[1658]: PAM unable to
dlopen(/lib/security/pam_unix_acct.so)
Nov  1 15:13:48 wilf gdm[1658]: PAM [dlerror:
/lib/security/pam_unix_acct.so: undefined symbol: crypt, version GLIBC_2.0]
Nov  1 15:13:48 wilf gdm[1658]: PAM adding faulty module:
/lib/security/pam_unix_acct.so
Nov  1 15:13:48 wilf gdm[1658]: PAM unable to
dlopen(/lib/security/pam_cracklib.so)
Nov  1 15:13:48 wilf gdm[1658]: PAM [dlerror:
/lib/security/pam_cracklib.so: undefined symbol: crypt, version GLIBC_2.0]
Nov  1 15:13:48 wilf gdm[1658]: PAM adding faulty module:
/lib/security/pam_cracklib.so
Nov  1 15:13:48 wilf gdm[1658]: PAM unable to
dlopen(/lib/security/pam_pwdb.so)
Nov  1 15:13:48 wilf gdm[1658]: PAM [dlerror: /lib/security/pam_pwdb.so:
undefined symbol: crypt, version GLIBC_2.0]
Nov  1 15:13:48 wilf gdm[1658]: PAM adding faulty module:
/lib/security/pam_pwdb.so
Nov  1 15:13:48 wilf gdm[1658]: PAM unable to
dlopen(/lib/security/pam_unix_session.so)
Nov  1 15:13:48 wilf gdm[1658]: PAM [dlerror:
/lib/security/pam_unix_session.so: undefined symbol: crypt, version
GLIBC_2.0]
Nov  1 15:13:48 wilf gdm[1658]: PAM adding faulty module:
/lib/security/pam_unix_session.so


Ta.
Comment 1 Havoc Pennington 2000-11-01 14:18:08 EST
I don't think gdm should need to link to -lcrypt; I would guess the problem
is with the PAM stuff. Nalin do you have a clue?
Comment 2 Nalin Dahyabhai 2000-11-01 15:35:45 EST
What are the contents of /etc/pam.d/gdm?

You seem to have a couple of things screwy here.  It looks like the openldap
package isn't installed because the shared libraries won't load, but you
mentioned other PAM-aware programs work correctly.  And then there are the large
number of errors due to not having the crypt() function defined.

When you run "ldd /lib/security/pam_pwdb.so" and "ldd
/lib/securitypam_unix_auth.so", does the resulting list include libcrypt.so.1? 
If so, then we know the modules themselves are okay, as they're supposed to be
linked against libcrypt.

If the modules are okay, I'd suspect something's wrong with your copy of
libcrypt.  Which version of the glibc package do you have installed ("rpm -q
glibc")?
Comment 3 Need Real Name 2000-11-01 16:23:47 EST
Ah. Didn't think to ldd libldap.so. That showed up the problem right away.
Its linked against libldap.so.1, but I'm running with libldap.so.2.

Cheers for your help!

Note You need to log in before you can comment on or make changes to this bug.