DO NOT REPLY [Bug 21645] - Child processes die after each request ( after connection is closed) on OpenBSD

[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=21645>.
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=21645

Child processes die after each request ( after connection is closed) on OpenBSD





------- Additional Comments From trawick@apache.org  2003-07-16 10:48 -------
What is logged in error_log?  Are the requests logged in access_log?  If there
is a piped logger, disable it.

If the child exited with a fatal signal (e.g., segmentation fault), you need to
get a coredump and then send us a backtrace so we know what code crashed.  This
usually requires 

a) using the CoredumpDirectory directive to point to a location with plenty of
free space
b) setting ulimits to allow core files to be written prior to starting Apache
c) possibly some OS-specific hacks to get core files from setuid processes (I'm
not familiar with OpenBSD requirements in this area)

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