Bug 110586 - nss_ldap causes getent/pam segfaults
nss_ldap causes getent/pam segfaults
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: nss_ldap (Show other bugs)
ia64 Linux
medium Severity high
: ---
: ---
Assigned To: Nalin Dahyabhai
Jay Turner
Depends On:
  Show dependency treegraph
Reported: 2003-11-21 10:56 EST by Christopher C. Weis
Modified: 2015-01-07 19:06 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-01-16 12:16:38 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Christopher C. Weis 2003-11-21 10:56:52 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1)

Description of problem:
First, one quick annoyance...  ldapsearch doesn't seem to read
ldap.conf, it seems to be looking at /etc/openldap/ldap.conf.  Should
this be a symlink?

Onto the issue: I configured ldap.conf so that ldapsearch'es work
fine.  However, whenever I add "ldap" to nsswitch.conf, things start

Here are the relevant entries in my nsswitch.conf file, which by the
way, along with the rest of our ldap setup, have been working great on
all our RH9 boxen for half a year now.

passwd:     files ldap
shadow:     files
group:      files ldap

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. add "ldap" to passwd or group (possibly others) in nsswitch.conf
2. "getent passwd" or "getent group"

Actual Results:  [root@a-lnx006 etc]# getent passwd
wnn:x:49:49:Wnn System Account:/home/wnn:/sbin/nologin
Segmentation fault
[root@a-lnx006 etc]#

Expected Results:  a whole bunch more passwd entries, and not segfault

Additional info:

This is the default RH WS 3 for Itanium load.  I haven't done any
updates (yet).
Comment 1 Nalin Dahyabhai 2003-11-21 15:58:49 EST
The /etc/ldap.conf and /etc/openldap/ldap.conf configuration files are
read by different libraries, and support different configuration
directives.  The coincidence in their naming is unfortunate and confusing.

Can you append the output of
 ldapsearch -x -b '' -s base supportedSASLmechanisms
to this report?  (If you get any values, then this is likely a dup of
Comment 2 Christopher C. Weis 2003-11-21 16:14:03 EST
Here you go...  This does look like a duplicate of the other bug.  Any
idea what's going on?

[root@a-lnx006 root]# ldapsearch -x -b '' -s base supportedSASLmechanisms
version: 2
# filter: (objectclass=*)
# requesting: supportedSASLmechanisms
supportedSASLMechanisms: GSSAPI
# search result
search: 2
result: 0 Success
# numResponses: 2
# numEntries: 1
[root@a-lnx006 root]#
Comment 3 Nalin Dahyabhai 2003-11-21 16:20:29 EST
Hmm, yes, the package was built wrong (links with libsasl2 instead of
libsasl).  That's being fixed for RHBA-2003:339.
Comment 4 Dag Wieers 2004-01-13 09:30:44 EST
We've downloaded RHBA-2003-339 and recompiled it on a fresh RHEL3 AMD
x86_64. While using it, we get a dlopen error and unresolved symbols:

    PAM unable to dlopen(/lib/security/$ISA/pam_ldap.so)
    PAM [dlerror: /lib/security/../../lib64/security/pam_ldap.so:
undefined symbol: _pam_ldap_readconfigfromdns]
    PAM adding faulty module: /lib/security/$ISA/pam_ldap.so
    Failed password for illegal user ##user## from ##ip## port 33347 ssh2
    Illegal user ##user## from ##ip##

After disabling the included dnsconfig-patch, everything works as
expected. Is it possible there's a missing define
_LDAP_PAM_LDAP_DNSCONFIG_H when compiling the default package for x86_64.
Comment 5 Jay Turner 2004-01-16 12:16:38 EST
An errata has been issued which should help the problem described in this bug report. 
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen 
this bug report if the solution does not work for you.

Comment 6 Dag Wieers 2004-01-29 10:40:50 EST
The RHEL3 U1 update fixes the pam_ldap problem on x86_64 with a clean
RHEL3 installation. Thanks.

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