Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 54697

Summary: nscd locks immediately if started with -t 1 and nss_ldap is used
Product: [Retired] Red Hat Linux Reporter: Jure Pecar <jure.pecar>
Component: glibcAssignee: Jakub Jelinek <jakub>
Status: CLOSED UPSTREAM QA Contact: Aaron Brown <abrown>
Severity: medium Docs Contact:
Priority: medium    
Version: 9CC: fweimer
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-04-17 08:41:30 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:

Description Jure Pecar 2001-10-16 16:17:18 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.8 i686)

Description of problem:
nscd is started with 6 threads by default (nscd.conf). while debugging some
other problems i started it through strace with -t 1 -d and observed
immediate lockup when a uid/gid should get resolved from ldap.

Version-Release number of selected component (if applicable):
redhat 7.1.94 (glibc and nscd 2.2.4-5)

How reproducible:
Always

Steps to Reproduce:
1. have a ldap based uid/gid resolving and some nfs dir mounted somewhere,
with files/dirs owned by uids from ldap.
2. start nscd with one thread only
3. do a ls -l in the nfs mounted dir
	

Actual Results:  ls -l locks forever (at least until nscd is stopped) while
ls -ln works. nscd actualy says that the first uid the ls -l should resolve
is not in it's cache, but that's as far it gets.

Expected Results:  i would expect the decrease in number of threads would
only impact peformance, not functionallity. but there's something odd about
it, it works ok if i say -t 2. could this be related to other nscd lockups
people are expiriencing (including me)?

Additional info:

mostly the same as at #54646
Comment 1 Ulrich Drepper 2003-04-17 08:41:30 UTC 
This problem should now be fixed in the official glibc CVS sources.  The next
binary we produce should contain the fix.
Comment 2 jmccann 2003-05-20 20:46:44 UTC 
I'm seeing this too with NIS+ with the default number of threads.  Will there be
a new binary for RH9?  Or are the glibc+nscd RPMs in rawhide stable enough to
use in production?  Thanks.
Comment 3 Ulrich Drepper 2003-11-04 21:30:58 UTC 
Try the binaries at

ftp://people.redhat.com/jakub/glibc/errata/2.3.2-27.9.4/             
                                                                  

which are supposed to be the next RHL9 errata.