Red Hat Bugzilla – Bug 454315
nss_ldap EPIPE when forking process
Last modified: 2011-03-24 10:01:24 EDT
Description of problem:
With nss_ldap-253-12, after a few commands in a shell, the shell stops working
(ie. any command executed returns immediately without performing any work).
Attaching to the shell process via strace shows that after the fork, there is a
write to a socket that should be connected to the LDAP server, but that is not
connected and thus results in EPIPE being returned. Falling back to version
253-5 eliminates this issue.
Version-Release number of selected component (if applicable):
Typically after executing a few commands in a shell of an LDAP user, the problem
starts occurring. Once it starts occurring, there is no way to recover other
than to exit the shell and start a new one.
Steps to Reproduce:
1. Login as an LDAP user
2. Execute some commands until the shell stops working
3. Attach to the shell process via strace to verify that it is indeed due to
SIGPIPE that the child process exits abnormally
Simple commands, such as ls, do nothing.
Commands should continue to work properly.
Created attachment 311193 [details]
strace of shell that is exhibiting this problem
This appears to be fixed with nss_ldap-253-13.el5_2.1. See bug #448014 and bug
#455271 for more details. I think this report can be closed.
I'm running centos 5.2 with nss_ldap-253-13.el5_2.1 and see the same problem, but it only affects systems intermittently.
Created attachment 376957 [details]
unblock sigpipe while closing the connection in the child
Jonathan, is there any chance that when you're seeing this, there's signal blocking involved? I'm attaching a patch to try to work around that.
(In reply to comment #4)
> Created an attachment (id=376957) [details]
> unblock sigpipe while closing the connection in the child
> Jonathan, is there any chance that when you're seeing this, there's signal
> blocking involved? I'm attaching a patch to try to work around that.
I can't as I don't work at the place anymore - but I've forwarded a note of this ticket to my old employees to let them know that there's a patch available.
RHEL5.5-Client-20100112.nightly (i386, x86_64)
RHEL5.5-Server-20100112.nightly (all archs)
RHTS test created, see QA whiteboard.
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.