Received: (qmail 431 invoked by uid 2012); 28 Jan 1999 16:59:02 -0000 Message-Id: <19990128165902.430.qmail@hyperreal.org> Date: 28 Jan 1999 16:59:02 -0000 From: matthew goebel Reply-To: goebel@emunix.emich.edu To: apbugs@hyperreal.org Subject: Server's children die off, and it cannot fork off any new ones. X-Send-Pr-Version: 3.2 >Number: 3789 >Category: os-solaris >Synopsis: Server's children die off, and it cannot fork off any new ones. >Confidential: no >Severity: serious >Priority: medium >Responsible: apache >State: feedback >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Thu Jan 28 10:10:00 PST 1999 >Last-Modified: Tue Apr 20 18:33:26 PDT 1999 >Originator: goebel@emunix.emich.edu >Organization: >Release: 1.3.4 >Environment: Solaris Sparc 2.6 with all base solaris patches included as of Jan 20th. Compiled with gcc-2.8.1 SunOS portal 5.6 Generic_105181-11 sun4u sparc SUNW,Ultra-Enterprise >Description: Excerpt from error_log file httpd: [Thu Jan 28 11:09:56 1999] [notice] child pid 337 exit signal User Signal 2 (17) httpd: [Thu Jan 28 11:09:56 1999] [notice] child pid 336 exit signal User Signal 2 (17) We are not running this over nfs, or doing dns lookups. The server is plain vanilla out of the tar file compile. There does not appear to be a pattern to when it suddenly has these problems. The only other information in the error_log file is the following, our users are not always patient enough to let the program finish: httpd: [Thu Jan 28 08:45:44 1999] [error] [client 164.76.107.174] Premature end of script headers: /usr/local/apache/cgi-bin/Swebrecon >How-To-Repeat: I cannot repeat the problem on demand, it happens when it does. >Fix: Not a clue. >Audit-Trail: State-Changed-From-To: open-feedback State-Changed-By: dgaudet State-Changed-When: Tue Apr 20 18:33:26 PDT 1999 State-Changed-Why: Nothing in apache sends SIGUSR2. Can you truss the parent when it's not forking? That would provide useful info. Dean >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [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! ]