|
Home > Archive > Web Servers on Unix and Linux > March 2004 > Need help : Server reached MaxClients setting
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Need help : Server reached MaxClients setting
|
|
|
| Hi,
I am running Apapche 2.0.48/PHP 4.3.4 on a Sun V240 box (Solaris 9). I
am generating HTTP requests (15 requests/second) from two clients to
the Apapche and get this error "Server reached MaxClients setting"
after some time.
The Apapche is compiled for worker MPM and I increased the number of
simulatneous connections to 600. I would appreciate if somebody can
help me.
Thanks,
Francis
| |
| Andreas Paasch 2004-02-27, 8:35 pm |
| Atul wrote:
> Hi,
>
> I am running Apapche 2.0.48/PHP 4.3.4 on a Sun V240 box (Solaris 9). I
> am generating HTTP requests (15 requests/second) from two clients to
> the Apapche and get this error "Server reached MaxClients setting"
> after some time.
>
> The Apapche is compiled for worker MPM and I increased the number of
> simulatneous connections to 600. I would appreciate if somebody can
> help me.
>
> Thanks,
> Francis
Simple math tells me that 15 * 60 = 900 ... and your setting is 600.
Increase the number of allowed connection in your config file ... and
eventually increase the number of child connections two ...
/Andreas
--
Registeret Linux user #292411
| |
|
| Andreas Paasch <Andreas@Paasch.Net> wrote in message news:<pCR%b.99296$jf4.6046856@news000.worldonline.dk>...
> Atul wrote:
>
>
> Simple math tells me that 15 * 60 = 900 ... and your setting is 600.
>
> Increase the number of allowed connection in your config file ... and
> eventually increase the number of child connections two ...
>
> /Andreas
Thanks Andreas for your response.
I don't see any timeouts for an hour and after that suddenly Apapche's
server-status starts showing incoming connections in "w (sending
reply)" and none of the connection gets closed and Apache becomes
unstable.
How the total number of simulatneous connections is interpreted by
Apache.
| |
| Andreas Paasch 2004-02-28, 6:34 pm |
| Atul wrote:
> Andreas Paasch <Andreas@Paasch.Net> wrote in message
> news:<pCR%b.99296$jf4.6046856@news000.worldonline.dk>...
>
> Thanks Andreas for your response.
>
> I don't see any timeouts for an hour and after that suddenly Apapche's
> server-status starts showing incoming connections in "w (sending
> reply)" and none of the connection gets closed and Apache becomes
> unstable.
>
> How the total number of simulatneous connections is interpreted by
> Apache.
If you are sure, that the problem occurs in the same time interval, not
approximately, but exactly, then it may not even be apache causing the
problem, rather something else which triggers apache to have the problem.
I'm thinking of some sort of DHCP server enabled ...
How apache counts exactly, is partly explain in the configuration files, but
more indepth at apache.org, the documentation.
If you have a load that you can't quite figure out when it has it's maximum,
the documentations tell you which settings to alter one by one in order to
have apache handle all requests in due time.
Last, you have an option about the max_lifetime of a child process, if you
locate the exact directive and eventually reduce the lifetime, apache might
be able to kill these hanging childprocesses faster and thus stay stable.
/Andreas
--
Registeret Linux user #292411
| |
|
| >
> If you are sure, that the problem occurs in the same time interval, not
> approximately, but exactly, then it may not even be apache causing the
> problem, rather something else which triggers apache to have the problem.
>
> I'm thinking of some sort of DHCP server enabled ...
>
> How apache counts exactly, is partly explain in the configuration files, but
> more indepth at apache.org, the documentation.
>
> If you have a load that you can't quite figure out when it has it's maximum,
> the documentations tell you which settings to alter one by one in order to
> have apache handle all requests in due time.
>
> Last, you have an option about the max_lifetime of a child process, if you
> locate the exact directive and eventually reduce the lifetime, apache might
> be able to kill these hanging childprocesses faster and thus stay stable.
>
> /Andreas
Is there need to tune the TCP parameters for Solaris if I am running
Apache under high load?
|
|
|
|
|