Re: Apache Goes Up and Down : server reached MaxClients setting,

Hi Tina,
>> > I am running RedHat 7.3/Apache/1.3.27 (Unix) mod_log_bytes/1.2
>> mod_bwlimited/1.0 PHP/4.3.2 FrontPage/5.0.2.2634 mod_ssl/2.8.14
>> OpenSSL/0.9.6b.
>> >
>> > My Apache server goes up and down very frequently. When i checked
>> the Logs it says :
>> > [Thu Jul 17 22:28:54 2003] [error] server reached MaxClients
>> setting, consider raising the MaxClients setting
>> >
<snip>
>> We need more information. How many domains are being served off this
>> machine, what is the MaxClients, MaxKeepAlive, KeepAliveTimeout, and
>> MaxRequestsPerChild settings?
> MaxClients 256
> MaxKeepAliveRequests 100
> KeepAliveTimeout 15
> MaxRequestsPerChild 0

How many domains? The apache defaults are generally good for 1 or 2
domains but should be performance tweaked beyond that, especially if you
have high-availability needs. If you have a number of domains, you should
maybe look into apache-2.x as the resource handling capability has been
vastly improved and the modules are just about ready for prime time. Check
the 2.0 mailing lists first to reconnoiter any issues (mostly 3rd party
module related) that might arise before making the changeover though.

Tina, go back and read the docs on configuring apache (the apache docs,
not the redhat docs). MaxRequestPerChild set to 0 can bring the whole
system down if you're running a poorly written web app process or module
that is leaking memory or other resources. What happens if you set this to
1000?

Also, if you have the memory, try setting the MaxClients to 1000. Check
top to see the memory usage by each child process first, then do the math.

Are you running an RRS news service or anything else that might have the
client automatically logging in to get updates off one or more of the
domains hosted?

-- 
Keith Mastin
BeechTree Information Technology Services Inc.
Toronto, Canada
(416)696 6070