Bug 157253 - Commands that depend upon the NSCD socket being available hang.
Commands that depend upon the NSCD socket being available hang.
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: nss_ldap (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
Jay Turner
Depends On:
Blocks: 190430
  Show dependency treegraph
Reported: 2005-05-09 16:28 EDT by Michael Tonn
Modified: 2015-01-07 19:09 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-19 15:02:39 EDT
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 Michael Tonn 2005-05-09 16:28:44 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)

Description of problem:
All of our servers are experiencing system hangs from time to time.  They are all using LDAP authentication.  When the condition occurs, any command that relies on the availability of the nscd socket hangs.  Invoking any of these commands with strace shows that they are waiting for a free socket.  Also, "netstat -a" shows 6 active sockets are in use.  I tried increasing the trhead count to 20, but the magic number stays at 6.  Disabling or recycling nscd always clears up the problem.

Version-Release number of selected component (if applicable):
kernel-2.4.21-27.ELsmp nss_ldap-207-15

How reproducible:

Steps to Reproduce:


Additional info:
Comment 31 RHEL Product and Program Management 2007-10-19 15:02:39 EDT
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.

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