Newb question: Just had to restart apache
I noticed that my websites were inaccessible (ssh and mysql were working) so I quickly login, try the first thing that comes up: restart apache, and everything works fine again. Anyway, I don't know how to monitor this or rather: how to find out what went wrong…
Can anyone give me some pointers?
In the apache error log when restarting it I got. But that still doesn't indicate on what went wrong before to my apache choke.
[Fri Sep 06 11:00:06 2013] [warn] child process 21139 still did not exit, sending a SIGTERM
[Fri Sep 06 11:00:06 2013] [warn] child process 21007 still did not exit, sending a SIGTERM
[Fri Sep 06 11:00:06 2013] [warn] child process 21134 still did not exit, sending a SIGTERM
[Fri Sep 06 11:00:06 2013] [warn] child process 21143 still did not exit, sending a SIGTERM
[Fri Sep 06 11:00:06 2013] [warn] child process 21096 still did not exit, sending a SIGTERM
[Fri Sep 06 11:00:08 2013] [warn] child process 21139 still did not exit, sending a SIGTERM
[Fri Sep 06 11:00:08 2013] [warn] child process 21007 still did not exit, sending a SIGTERM
[Fri Sep 06 11:00:08 2013] [warn] child process 21134 still did not exit, sending a SIGTERM
[Fri Sep 06 11:00:08 2013] [warn] child process 21143 still did not exit, sending a SIGTERM
[Fri Sep 06 11:00:08 2013] [warn] child process 21096 still did not exit, sending a SIGTERM
[Fri Sep 06 11:00:10 2013] [warn] child process 21139 still did not exit, sending a SIGTERM
[Fri Sep 06 11:00:10 2013] [warn] child process 21007 still did not exit, sending a SIGTERM
[Fri Sep 06 11:00:10 2013] [warn] child process 21134 still did not exit, sending a SIGTERM
[Fri Sep 06 11:00:10 2013] [warn] child process 21143 still did not exit, sending a SIGTERM
[Fri Sep 06 11:00:10 2013] [warn] child process 21096 still did not exit, sending a SIGTERM
[Fri Sep 06 11:00:12 2013] [error] child process 21139 still did not exit, sending a SIGKILL
[Fri Sep 06 11:00:12 2013] [error] child process 21007 still did not exit, sending a SIGKILL
[Fri Sep 06 11:00:12 2013] [error] child process 21134 still did not exit, sending a SIGKILL
[Fri Sep 06 11:00:12 2013] [error] child process 21143 still did not exit, sending a SIGKILL
[Fri Sep 06 11:00:12 2013] [error] child process 21096 still did not exit, sending a SIGKILL
[Fri Sep 06 11:00:13 2013] [notice] caught SIGTERM, shutting down
[Fri Sep 06 11:00:14 2013] [notice] Apache/2.2.22 (Ubuntu) PHP/5.3.10-1ubuntu3.7 with Suhosin-Patch configured -- resuming normal operations
[Fri Sep 06 11:00:20 2013] [error] server reached MaxClients setting, consider raising the MaxClients setting
thanks!
1 Reply
server reached MaxClients setting, consider raising the MaxClients setting
??
For monitoring there are many ways to do this… on the server itself… but I normally use cheap monitoring service that can do protocol testing. HTTP for example to check to see if a website is responding. If not, it pages me.
I use monitis.com for example. Up to 20 hosts (I set up SMTP, FTP and HTTP testing) configured for minimal services for ~$10 a month.