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 636656

Summary: The nss_ldap module fails directly after server connection has been lost
Product: Red Hat Enterprise Linux 5 Reporter: Dmitri Pal <dpal>
Component: sssdAssignee: Stephen Gallagher <sgallagh>
Status: CLOSED ERRATA QA Contact: Chandrasekar Kannan <ckannan>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.2CC: astrand, benl, dpal, grajaiya, jgalipea, jplans, ossman, sean
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: sssd-1.2.1-27.1.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 470003 Environment:
Last Closed: 2011-01-13 22:37:06 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: 470003    
Bug Blocks:    

Comment 2 Dmitri Pal 2010-09-22 21:00:31 UTC
*** Bug 470003 has been marked as a duplicate of this bug. ***

Comment 4 Jenny Severance 2010-09-29 19:06:25 UTC
Please add steps to verify the setup and verification of this bug.

Comment 6 Pierre Ossman 2010-12-23 09:08:36 UTC
Attachment 322527 [details] on bug 470003 has a test case:

"Reproduce by starting test case and then restarting the LDAP server while
getpwnam-twice is sleeping. The next getpwnam() call will fail."

Comment 7 Dmitri Pal 2010-12-24 03:12:33 UTC
(In reply to comment #6)
> Attachment 322527 [details] on bug 470003 has a test case:
> 
> "Reproduce by starting test case and then restarting the LDAP server while
> getpwnam-twice is sleeping. The next getpwnam() call will fail."

Did you use SSSD? This bug is a clone to address the issue in SSSD or better say to make sure that SSSD does not have an issue.

Comment 8 Pierre Ossman 2010-12-25 11:49:10 UTC
Ah, sorry no. As bug 470003 was closed as duplicate, I assumed it was the same component. The summary also refers to nss_ldap, not sssd.

Should we interpret the fact that bug 470003 is closed this way as nss_ldap no longer being supported on RHEL 5 and everyone should switch to sssd? That seems a bit harsh given that RHEL 5 is supposed to be very stable component-wise.

Comment 9 Dmitri Pal 2010-12-31 20:58:49 UTC
nss_ldap is broken in many ways. It lacks a lot of the functionality related to connectivity, caching, fail over etc. SSSD is the component that was added to address all these troubles. nss_ldap is still supported and will be but rather than enhancing it we would prefer investing into SSSD. If there is a clear bug in nss_ldap we will definitely fix it. But this issue IMO is on the boundary of the bug/enhancement that is why we suggest evaluating SSSD.

Comment 11 errata-xmlrpc 2011-01-13 22:37:06 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/RHEA-2011-0044.html