Bug 161185

Summary: Dropped connections causes bash to hang on nss lookups
Product: [Fedora] Fedora Reporter: Enrico Scholz <rh-bugzilla>
Component: nss_ldapAssignee: Nalin Dahyabhai <nalin>
Status: CLOSED INSUFFICIENT_DATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 4   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-02-17 02:56:24 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 Enrico Scholz 2005-06-21 07:18:19 UTC
Description of problem:

When having an LDAP server which drops connections after a certain timeout, bash
will hang at actions like 'cd ~foo<tab>'. At this time, a lot of connections like

| tcp 1  0 192.168.46.2:57752   192.168.46.137:389          CLOSE_WAIT

are shown by netstat.


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

nss_ldap-234-4
bash-3.0-31


How reproducible:

100%


Steps to Reproduce:
1. setup NSS to use LDAP as passwd backend
2. setup the LDAP server to timeout after a certain time (e.g. 'idletimeout 900')
3. start a bash
4. type in 'cd ~foo' and press TAB
5. wait some time...
6. type in 'cd ~foo' and press TAB
  

Actual results:

bash hangs at step 6; 'strace' shows that it waits in a futex(2) syscalls.


Expected results:

bash expands 'foo' both in 4 and 6


Additional info:

nscd is NOT running; LDAP is not configured for TLS

Comment 1 Christian Iseli 2007-01-22 11:40:14 UTC
This report targets the FC3 or FC4 products, which have now been EOL'd.

Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?

Thanks.

Comment 2 petrosyan 2008-02-17 02:56:24 UTC
Fedora Core 4 is no longer maintained.

Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the
current Fedora release, please reopen this bug and assign it to the
corresponding Fedora version.