Red Hat Bugzilla – Bug 162712
nscd segfaulting using nss_ldap
Last modified: 2007-11-30 17:11:09 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4
Description of problem:
I originally posted this under bug #162326, but was told this is an LDAP related problem so I'm posting here. The problem is nscd is crashing when using LDAP for NSS lookups. This same configuration worked under FC3.
I'm attaching full gdb stack trace and valgrind output. Also, /proc IS mounted and I'm not sure why valgrind is complaining about /proc/self/maps.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. configure nsswitch.conf for LDAP support as follows:
$ grep ldap /etc/nsswitch.conf
passwd: files ldap
shadow: files ldap
group: files ldap
services: files ldap
protocols: files ldap
rpc: files ldap
ethers: files ldap
netgroup: files ldap
aliases: files ldap
2. setup ldap.conf
3. start nscd
Actual Results: nscd segfaults
Created attachment 116493 [details]
gdb stack trace
Created attachment 116494 [details]
valgrind --db-attach=no --tool=memcheck --error-limit=no nscd -d
Same problem, no Xen though, but the rest of the config is the same.
Created attachment 117063 [details]
gdb stack trace
This is my gdb trace. Looks similar to Dan's.
I also added a reference to the GCC bug which seems to be at the root of this
problem. Remove it if it's not the case.
*** Bug 162326 has been marked as a duplicate of this bug. ***
After the upgrade to glibc-2.3.5-10.2 the situation is better.
nscd dies two or three times per day only.
After updating glibc and nscd to 2.3.5-10.3, everything has been stable for the
last month. Not a single crash or restart required. It looks fixed to me.
Closing because bug has remained in NEEDINFO state without reply for a long
period of time.
Note that FC3 and FC4 are supported by Fedora Legacy for security
fixes only. Please install a still supported version and retest. If
it still occurs on FC5 or FC6, please reopen and assign to the correct
version. Otherwise, if this a security issue, please change the
product to Fedora Legacy. Thanks, and we are sorry that we did not
get to this bug earlier.
This bug was originally filed against a much earlier version of Fedora
Core, and significant changes have taken place since the last version
for which this bug is confirmed.
Closing because previous comments imply that it's been fixed.