Support Forums

Full Version: Apache Fail.
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hola SF.

I have a VPS that I'm currently running CentOS on (and of course Apache for a HTTPd), I don't exactly monitor it seeing as I only host a few sites on it and monitoring is a pain. I went to my blog just then to grab a link for someone and Apache was dead...I just did 'service httpd start' and it didn't complain about it already running or anything like that and it was functioning perfectly after the [re?]start - I looked at the logs anyway.

error.log Wrote:[...normal 404s.etc]
[Sun Oct 04 04:03:48 2009] [warn] child process 21293 still did not exit, sending a SIGTERM
[Sun Oct 04 04:03:48 2009] [warn] child process 21294 still did not exit, sending a SIGTERM
[Sun Oct 04 04:03:48 2009] [warn] child process 21295 still did not exit, sending a SIGTERM
[Sun Oct 04 04:03:48 2009] [warn] child process 30670 still did not exit, sending a SIGTERM
[Sun Oct 04 04:03:48 2009] [warn] child process 30671 still did not exit, sending a SIGTERM
[Sun Oct 04 04:03:48 2009] [warn] child process 30672 still did not exit, sending a SIGTERM
[Sun Oct 04 04:03:49 2009] [warn] child process 983 still did not exit, sending a SIGTERM
[Sun Oct 04 04:03:49 2009] [warn] child process 984 still did not exit, sending a SIGTERM
[Sun Oct 04 04:03:50 2009] [notice] SIGHUP received. Attempting to restart
[root@katelyn ~]#

So yea...service sent a SIGHUP but I've never seen Apache do anything like this (Apache has never died on me before) - does anyone have any idea as to why this happened; just curious.