Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 488857

Summary: nss_ldap bug causes nscd to crash with `ldap_result: Assertion `ld != ((void *)0)' failed.'
Product: Red Hat Enterprise Linux 5 Reporter: jos
Component: nss_ldapAssignee: Nalin Dahyabhai <nalin>
Status: CLOSED ERRATA QA Contact: BaseOS QE <qe-baseos-auto>
Severity: high Docs Contact:
Priority: urgent    
Version: 5.2CC: akarlsso, jbastian, jplans, magnus, sturpin, syeghiay, tao
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 253-20.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 566632 (view as bug list) Environment:
Last Closed: 2009-09-02 11:49:09 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:
Bug Depends On:    
Bug Blocks: 566632    
Attachments:
Description Flags
Patch to ldap-nss.c fixing issue
none
alternate patch none

Description jos 2009-03-05 23:21:58 UTC 
Description of problem:

When using nss_ldap with user accounts in LDAP and the `nss_connect_policy oneshot' directive in /etc/ldap.conf, running `id <LDAP user>' causes id to fail and nscd to crash.

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

253-13.el5_2.1

How reproducible:

Steps to Reproduce:
1. service nscd start
2. Enable `nss_connect_policy oneshot' in /etc/ldap.conf
3. id <existing LDAP user>
  
Actual results:

# id josb
id: ../../../libraries/libldap/result.c:113: ldap_result: Assertion `ld != ((void *)0)' failed.
uid=1001(josb) gid=1000(eng)Aborted
# 

Expected results:

[root src]# ./id josb
uid=1001(josb) gid=1000(eng) groups=10000(ldap_other)
[root src]# 

Additional info:

The fix is available in http://bugzilla.padl.com/show_bug.cgi?id=350. See attachment.
Comment 1 jos 2009-03-05 23:24:46 UTC 
Created attachment 334233 [details]
Patch to ldap-nss.c fixing issue

Please consider applying this patch; it fixes this problem for me.
Comment 2 jos 2009-03-06 19:01:43 UTC 
Sorry, I spoke too soon. The attached patch causes any LDAP entries to be omitted, which is almost as bad as crashing. Further inspection of PADLs Bugzilla reveals two other bugs:

http://bugzilla.padl.com/show_bug.cgi?id=322
http://bugzilla.padl.com/show_bug.cgi?id=375

which indicates that this problem is NOT solved upstream.

Please consider shipping http://ch.tudelft.nl/~arthur/nss-ldapd/ in extras, because as it stands nss_ldap is unusable.
Comment 3 Magnus Glantz 2009-05-07 09:06:24 UTC 
I can verify this bug on RHEL 5.2 server and desktop using:
nss_ldap-254-5.el5.
nscd-2.5-18

This can be a major issue if you are administrating thousands of ldap clients and need to keep them from having persistent connections.

A thought might be that setting:
paranoia         yes
restart-interval           3600
in /etc/nscd.conf may solve this issue..

I'm going to try that out and see what happens.
Comment 4 Magnus Glantz 2009-05-07 09:32:23 UTC 
Setting
paranoia         yes
restart-interval         3600
in /etc/nscd.conf didn't do the trick..

Actually, after some testing nscd started to crash at boot.
Comment 5 Nalin Dahyabhai 2009-05-11 21:17:53 UTC 
Created attachment 343505 [details]
alternate patch
Comment 8 Magnus Glantz 2009-05-15 09:16:52 UTC 
The most recent - alternate patch (id=343505) solves the issue for me.
Comment 16 errata-xmlrpc 2009-09-02 11:49:09 UTC 
An advisory 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 therefore 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.

http://rhn.redhat.com/errata/RHBA-2009-1379.html