Apache 1.3.34 randomly crashes

[modem]

I upgraded to Apache 1.3.34 per the thread on the versions forum and all went well. I have the latest Zend and PHP and all was working great. Then two days after upgrading a client emails me asking why I took their website down for a few hours. Come to find out after checking /var/log/httpd/error_log I saw that Apache was randomly shutting itself down and restarting. Here are some of the lines of the log:

*****************************************
Fri Oct 21 21:51:01 2005] [warn] child process 21488 still did not exit, sending a SIGTERM
[Fri Oct 21 21:51:01 2005] [warn] child process 21489 still did not exit, sending a SIGTERM
[Fri Oct 21 21:51:01 2005] [warn] child process 21490 still did not exit, sending a SIGTERM
[Fri Oct 21 21:51:01 2005] [warn] child process 21491 still did not exit, sending a SIGTERM
[Fri Oct 21 21:51:01 2005] [warn] child process 21492 still did not exit, sending a SIGTERM
[Fri Oct 21 21:51:01 2005] [warn] child process 21493 still did not exit, sending a SIGTERM
[Fri Oct 21 21:51:01 2005] [warn] child process 21494 still did not exit, sending a SIGTERM
[Fri Oct 21 21:51:01 2005] [warn] child process 21495 still did not exit, sending a SIGTERM
[Fri Oct 21 21:51:01 2005] [warn] child process 27568 still did not exit, sending a SIGTERM
[Fri Oct 21 21:51:01 2005] [warn] child process 28008 still did not exit, sending a SIGTERM
[Fri Oct 21 21:51:01 2005] [warn] child process 28009 still did not exit, sending a SIGTERM
[Fri Oct 21 21:51:01 2005] [warn] child process 28010 still did not exit, sending a SIGTERM
[Fri Oct 21 21:51:01 2005] [warn] child process 28011 still did not exit, sending a SIGTERM
[Fri Oct 21 21:51:01 2005] [warn] child process 28012 still did not exit, sending a SIGTERM
[Fri Oct 21 21:51:01 2005] [warn] child process 28013 still did not exit, sending a SIGTERM
[Fri Oct 21 21:51:01 2005] [warn] child process 28014 still did not exit, sending a SIGTERM
[Fri Oct 21 21:51:01 2005] [warn] child process 28015 still did not exit, sending a SIGTERM
[Fri Oct 21 21:51:01 2005] [warn] child process 28016 still did not exit, sending a SIGTERM
[Fri Oct 21 21:51:01 2005] [warn] child process 28017 still did not exit, sending a SIGTERM
[Fri Oct 21 21:51:01 2005] [warn] child process 6092 still did not exit, sending a SIGTERM
[Fri Oct 21 21:51:07 2005] [warn] module perl_module is already loaded, skipping
[Fri Oct 21 21:51:08 2005] [notice] Apache configured -- resuming normal operations
[Fri Oct 21 21:51:08 2005] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)

*****************************************

Can anyone tell me why this is doing this? In the meantime I'm downgrading to 1.3.33 again.

Brad

 

[squirrelhost]

try this:

have a look for the

ScoreBoardFile directive in your
httpd.conf - my guess is that the file
specified doesn't exist.

comment this line out, and
restart your httpd.

then check your error log again.


(posted this in the wrong thread the
other day, but should fix your problem)

 

[modem]

Actually I downgraded to Apache 1.3.33 and that seems to have solved the problem.

 

[Chrysalis]

thats not solving the problem since you now running an outdated vulnerable version, its a workaround.

 

[modem]

I agree, but it solved the problem of apache crashing suddenly and breifly causing customers to get irate that it's down for a few moments, but it is only a temporary work around. Until I can figure out a solution I'm balancing customer happiness along with security. It's a fine line.