httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 41367] - Logging to a pipe causes hanging children when doing a graceful restart
Date Mon, 15 Jan 2007 17:14:04 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=41367>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=41367





------- Additional Comments From dave64@andrew.cmu.edu  2007-01-15 09:14 -------
Thanks for looking at this so quickly, Jeff.  For various reasons, we can't move
to apache 2.x yet, and the fix you pointed out doesn't appear to exist for the
1.3.x branch.  I understand what you mean, in theory, that if the child logger
(cronolog, for example) should crash, you can fork/exec a new child and log
using the same file descriptors since they'll be duplicated again from the
parent to the child on fork/exec.  The problem we're seeing, however, is that
the httpd processes never know that the child logging process went away.  They
get stuck in a blocking write() call on the pipe file descriptor forever.  Since
httpd holds open the write and read end of the pipe, there will always be a
reader and the write() calls neither complete nor fail.  Instead, they block
forever.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message