os-solaris/4093: The web server stops responding to client requests although it remains running.

[Larry Glaze <lg...@iddg.com>]

>Number:         4093
>Category:       os-solaris
>Synopsis:       The web server stops responding to client requests although it remains running.
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Fri Mar 19 14:50:02 PST 1999
>Last-Modified:
>Originator:     lglaze@iddg.com
>Organization:
apache
>Release:        1.3.4
>Environment:
uname -a: SunOS ultra73 5.6 Generic_105181-11 sun4u sparc SUNW,Ultra-5_10
OS: Solaris 2.6
Compiler: gcc version 2.8.1
>Description:
Apache stops responding to client requests. It remains running, however, but
gives absolutely no errors in either its own error_log or in the server syslog.
Apache usually has about 150 processes running when responding properly. 
When it stops responding, the number of processes will drop down to 40 or so. My
guess is that apache thinks it is idle now and starts killing off some
of its child processes. This problem existed before we compiled in mod_perl. The
version of mod_perl we are using is 1.18. Everything besides this version of
mod_perl came with the apache source.

I have seen a couple other people mention this bug but haven't seen any responses
about a possible fix. For now I have to run a monitoring script which will restart
apache when it stops responding.

Here is the output of "httpd -v" and "httpd -l":
httpd -v:
Server version: Apache/1.3.4 (Unix)
Server built:   Mar  4 1999 23:02:34

httpd -l:
Compiled-in modules:
  http_core.c
  mod_env.c
  mod_log_config.c
  mod_mime.c
  mod_negotiation.c
  mod_status.c
  mod_include.c
  mod_autoindex.c
  mod_dir.c
  mod_cgi.c
  mod_asis.c
  mod_imap.c
  mod_actions.c
  mod_userdir.c
  mod_alias.c
  mod_access.c
  mod_auth.c
  mod_setenvif.c
  mod_perl.c
>How-To-Repeat:
Unsure. It happens randomly.
>Fix:
No.
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> 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!         ]