Received: (qmail 97133 invoked by uid 65534); 13 Jan 2000 05:21:45 -0000
Message-Id: <20000113052145.97132.qmail@locus.apache.org>
Date: 13 Jan 2000 05:21:45 -0000
From: Peter Friend <octavian@corp.earthlink.net>
Reply-To: octavian@corp.earthlink.net
To: submit@bugz.apache.org
Subject: Same as PR#2580, graceful restart causes "lost child" error when using piped logger
X-Send-Pr-Version: 3.110

>Number:         5575
>Category:       mod_log-any
>Synopsis:       Same as PR#2580, graceful restart causes "lost child" error when using piped logger
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed Jan 12 21:30:00 PST 2000
>Closed-Date:
>Last-Modified:
>Originator:     octavian@corp.earthlink.net
>Release:        1.3.9
>Organization:
apache
>Environment:
SunOS 5.6 Generic_105181-16 sun4u sparc SUNW,Ultra-2
>Description:
Sorry if this has been handled, I didn't see anything beyond PR#2580.

Like the other report, I get "[Wed Jan 12 21:10:12 2000] [warn] long lost child came home! (pid 10770)"
in my error logs ONLY when doing a -USR1 restart. The pid for this child is
the pid of the /bin/sh process which is the parent of the logging process. Note
that I use two piped loggers, and this error occurs ONLY for the CustomLog piped
logger. The other piped logger is used via ErrorLog and produces no error.
>How-To-Repeat:
Just do a kill -USR1 on the parent (root) Apache process when using a piped log
via the CustomLog directive. -HUP does NOT produce the error on my system.
>Fix:
I haven't had time to dig through the code for this yet, it really isn't THAT big
of a deal. I can always use -HUP, but I would rather not cut off the folks in 
mid-request, especially with our traffic levels.
>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]