On Mon, Jan 25, 2010 at 11:36 AM, Mark Watts <m.watts@xxxxxxxxxxxxxxxx> wrote: > On Mon, 2010-01-25 at 09:44 -0500, Jeff Trawick wrote: >> On Mon, Jan 25, 2010 at 8:56 AM, Vikrama Sanjeeva >> <viki.sanjeeva@xxxxxxxxx> wrote: >> > Hello All, >> > >> > This is regarding production servers. Recently Apache server hit MaxClient >> > settings; resulting in crash of sites. However, sites was back to normal >> > after restarting Apache. >> >> The expected symptom is that Apache is unresponsive to additional >> requests until some of the child processes finish what they're working >> on. >> >> Restarting Apache without increasing MaxClients isn't helpful; if it >> is a hard restart it trashes the current connections. >> >> > I read about MaxClient settings and increase it from 200 to 250 (as I read >> > somewhere that 256 is a limit). >> >> Run apachectl -V to see the limit; it should be in the tens of thousands. > > Umm, does it? > > > # apachectl -V my bad; it doesn't, as you point out for httpd 2.2.x: prefork's hard limit is 200000 child processes; worker's limits are 20000 child processes and 20000 threads per process (expect to hit system limits long before that) --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|