>Number: 5225 >Category: other >Synopsis: Child processes die and Apache does not respond >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Sun Oct 31 00:20:01 PDT 1999 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: >Environment: SunOS sun00856 5.6 Generic_105181-13 sun4u sparc SUNW,UltraSPARC-IIi-Engine gcc version 2.8.1 >Description: Unexpectedly, Apache children will all go away. The main process does not start new ones and this is in the error log:
[Sun Oct 31 01:20:09 1999] [warn] child process 15743 did not exit, sending another SIGHUP [Sun Oct 31 01:20:10 1999] [warn] child process 15744 did not exit, sending another SIGHUP [Sun Oct 31 01:20:10 1999] [warn] child process 15745 did not exit, sending another SIGHUP [Sun Oct 31 01:20:10 1999] [warn] child process 15746 did not exit, sending another SIGHUP [Sun Oct 31 01:20:10 1999] [warn] child process 15747 did not exit, sending another SIGHUP [Sun Oct 31 01:20:10 1999] [warn] child process 15748 did not exit, sending another SIGHUP [Sun Oct 31 01:20:10 1999] [warn] child process 15749 did not exit, sending another SIGHUP [Sun Oct 31 01:20:10 1999] [warn] child process 15750 did not exit, sending another SIGHUP [Sun Oct 31 01:20:10 1999] [warn] child process 15751 did not exit, sending another SIGHUP [Sun Oct 31 01:20:10 1999] [warn] child process 15752 did not exit, sending another SIGHUP [Sun Oct 31 01:20:10 1999] [warn] child process 15753 did not exit, sending another SIGHUP [Sun Oct 31 01:20:10 1999] [warn] child process 15755 did not exit, sending another SIGHUP [Sun Oct 31 01:20:10 1999] [warn] child process 15757 did not exit, sending another SIGHUP [Sun Oct 31 01:20:10 1999] [warn] child process 15758 did not exit, sending another SIGHUP [Sun Oct 31 01:20:10 1999] [warn] child process 15759 did not exit, sending another SIGHUP [Sun Oct 31 01:20:10 1999] [warn] child process 15760 did not exit, sending another SIGHUP [Sun Oct 31 01:20:10 1999] [warn] child process 15761 did not exit, sending another SIGHUP [Sun Oct 31 01:20:10 1999] [warn] child process 15762 did not exit, sending another SIGHUP [Sun Oct 31 01:20:10 1999] [warn] child process 15763 did not exit, sending another SIGHUP [Sun Oct 31 01:20:10 1999] [warn] child process 15764 did not exit, sending another SIGHUP [Sun Oct 31 01:20:10 1999] [warn] child process 15767 did not exit, sending another SIGHUP [Sun Oct 31 01:20:11 1999] [warn] child process 15780 did not exit, sending another SIGHUP [Sun Oct 31 01:20:11 1999] [warn] child process 15781 did not exit, sending another SIGHUP [Sun Oct 31 01:20:33 1999] [notice] SIGHUP received. Attempting to restart [Sun Oct 31 01:21:02 1999] [notice] Apache/1.3.9 (Unix) PHP/3.0.12 configured -- resuming normal operations However, normal operations are not resumed. There are no child processes. apahcectl graceful and restart do not help. The create new lines in the error log like: [Sun Oct 31 01:47:53 1999] [notice] SIGHUP received. Attempting to restart [Sun Oct 31 01:48:16 1999] [notice] Apache/1.3.9 (Unix) PHP/3.0.12 configured -- resuming normal operations However, no childs exist. The only resolution is to apachectl stop and then apachectl start. >How-To-Repeat: It only seems to happen when another process is not working. The first time it happened, we simply had a cron job that sent a bad param to ps. Everytime that job ran, this would happen. This last time our MySQL process had spiked. I have seen MySQL and other processes spike before on other OS'es and not seen this problem. >Fix: No Idea. >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, you need] [to include <[EMAIL PROTECTED]> 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! ]
