Apache httpd dies for strange reason

GSMD · 02-25-2007, 12:40 PM

The strange thing that happens is that time to time I see that my apache httpd is down with the last lines in it's error log being smth like

Code:

[Sun Feb 25 06:25:38 2007] [error] child process 8158 still did not exit, sending a SIGKILL
[Sun Feb 25 06:25:38 2007] [error] child process 18570 still did not exit, sending a SIGKILL
[Sun Feb 25 06:25:38 2007] [error] child process 18317 still did not exit, sending a SIGKILL
[Sun Feb 25 06:25:38 2007] [error] child process 18410 still did not exit, sending a SIGKILL
[Sun Feb 25 06:25:38 2007] [error] child process 18411 still did not exit, sending a SIGKILL
[Sun Feb 25 06:25:39 2007] [notice] caught SIGTERM, shutting down

could anyone please give a hint on how to trace this?

Thanks.

btmiller · 02-25-2007, 04:39 PM

Sounds like the individual child thread are hanging and have to be killed with SIGKILL. However, the main question is why Apache is trying to shut down everything in the first place. Can you read a few more lines above that in the logs and see what is going on? Are you using the default Apache that ships with Etch?

GSMD · 02-26-2007, 03:55 AM

Thanks for your reply.
The thing is that's there's nothing wrong seems to happen before those sigterms:

Code:

[Sun Feb 25 02:05:48 2007] [error] [client 74.6.87.40] File does not exist: /var/www/forum.myhost.org/robots.txt
[Sun Feb 25 05:53:35 2007] [error] [client 74.6.87.40] File does not exist: /var/www/forum.myhost.org/robots.txt
[Sun Feb 25 06:25:33 2007] [warn] child process 18306 still did not exit, sending a SIGTERM
[Sun Feb 25 06:25:33 2007] [warn] child process 8377 still did not exit, sending a SIGTERM

Yes, that's the default apache2 that comes with etch, the system is up to date.

GSMD · 02-28-2007, 01:22 AM

Actually these are the reported bugs:
* http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=398223
* http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=399776