View Single Post
  #4  
Old 25th June 2013, 21:53
mzandstra mzandstra is offline
Junior Member
 
Join Date: Mar 2013
Posts: 13
Thanks: 0
Thanked 0 Times in 0 Posts
Default

I was able to get a piece of the main httpd error log right as this issue was occuring

Code:
[Tue Jun 25 13:43:08 2013] [error] server reached MaxClients setting, consider raising the MaxClients setting
[Tue Jun 25 13:43:10 2013] [error] child died with signal 9
[Tue Jun 25 13:43:47 2013] [error] child died with signal 9
[Tue Jun 25 13:43:49 2013] [error] child died with signal 9
[Tue Jun 25 13:43:55 2013] [error] child died with signal 9
[Tue Jun 25 13:43:59 2013] [error] child died with signal 9
[Tue Jun 25 13:44:03 2013] [error] child died with signal 9
[Tue Jun 25 13:44:05 2013] [error] child died with signal 9
[Tue Jun 25 13:44:07 2013] [error] child died with signal 9
[Tue Jun 25 13:44:08 2013] [error] child died with signal 9
[Tue Jun 25 13:44:09 2013] [error] child died with signal 9
[Tue Jun 25 13:44:10 2013] [error] child died with signal 9
[Tue Jun 25 13:44:12 2013] [error] child died with signal 9
[Tue Jun 25 13:44:13 2013] [error] child died with signal 9
[Tue Jun 25 13:44:13 2013] [error] child died with signal 9
[Tue Jun 25 13:44:15 2013] [error] child died with signal 9
[Tue Jun 25 13:45:18 2013] [error] child died with signal 9
[Tue Jun 25 13:45:19 2013] [error] child died with signal 9
[Tue Jun 25 13:45:29 2013] [error] child died with signal 9
From my memory monitor:

Code:
06-25-2013 13:44:02 - 63 MB Free with 42 httpd processes of average size 24894
My question is, why did httpd wait for those 42 processes to spawn before killing them off? It should never have let that many spawn in the first place.
Reply With Quote