DO NOT REPLY [Bug 19985] New: - prefork children dying, parent unresponsive

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19985>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19985

prefork children dying, parent unresponsive

           Summary: prefork children dying, parent unresponsive
           Product: Apache httpd-1.3
           Version: 1.3.27
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Major
          Priority: Other
         Component: core
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: pedietz@west.com


We are converting out AIX platform to linux.  The Aix platform uses 1.3.22 with 
some custom c modules....we are upgrading to 1.3.27 with the same C modules.

We are running in prefork mode.

The problem we are seeing is after X minutes (anywhere from 20 minutes to 4 
hours), the preforked children will suddenly exit leaving only the parent 
process.  The parent process still has port 80 open, but since theres no 
workers, HTTP requests to it timeout.

We have 2 versions of this statically compiled app runnning, one for port 80 
and one for port 443.  Both ports lock up eventually.  We have 2 servers, and 
both servers experience this...

I have tried:
  1) setting the AcceptMutex to fcntl versus sysv
  2) compiled out mod_status/mod_info and turned off the shared memory 
scoreboard  (an mod_status was showing all channels in the G state after a 
restart so I was thinking if shared memory is corrupted).
  3) setting MaxChild to 256 and StartServers to 20.
  4) setting the log level to debug
  5) using apache1.3.28-dev and it too locks up with the same problem

I see no error logs that show why the children are exiting-- in the apache 
error log nor syslog for linux.  I see no core dumps.

We are running redhat7.3.

Where should I look next ?

We are using openssl

Server version: Apache/1.3.27 (Unix)
Server built:   May 15 2003 16:39:31
Server's Module Magic Number: 19990320:13
Server compiled with....
 -D EAPI
 -D EAPI_MM
 -D EAPI_MM_CORE_PATH="logs/mm"
 -D HAVE_MMAP
 -D HAVE_SHMGET
 -D USE_SHMGET_SCOREBOARD
 -D USE_MMAP_FILES
 -D HAVE_FCNTL_SERIALIZED_ACCEPT
 -D HAVE_SYSVSEM_SERIALIZED_ACCEPT
 -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
 -D HARD_SERVER_LIMIT=256
 -D HTTPD_ROOT="/usr/local/apache"
 -D SUEXEC_BIN="/usr/local/apache/bin/suexec"
 -D DEFAULT_PIDLOG="logs/httpd.pid"
 -D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
 -D DEFAULT_LOCKFILE="logs/accept.lock"
 -D DEFAULT_ERRORLOG="logs/error_log"
 -D TYPES_CONFIG_FILE="conf/mime.types"
 -D SERVER_CONFIG_FILE="conf/httpd.conf"
 -D ACCESS_CONFIG_FILE="conf/access.conf"
 -D RESOURCE_CONFIG_FILE="conf/srm.conf"

[Thu May 15 08:17:14 2003] [notice] Apache/1.3.27 (Unix) mod_ssl/2.8.14 
OpenSSL/0.9.7b configured -- resuming normal operations

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