Hi.
Im running Directadmin 1.33.7 with Apache 2.0.63 on a CentOS 5 (Final).
Theres another server running a SQUID for one of the domains in the Directadmin.
In the apache error_log i've seend this error repetead times when the httpd goes down (all the days, arround the same hour):
"[error] server reached MaxClients setting, consider raising the MaxClients setting"
Part of my httpd.conf:
**********************************************
Timeout 60
KeepAlive On
MaxKeepAliveRequests 100
KeepAliveTimeout 15
## Server-Pool Size Regulation (MPM specific)
# prefork MPM
# StartServers: number of server processes to start
# MinSpareServers: minimum number of server processes which are kept spare
# MaxSpareServers: maximum number of server processes which are kept spare
# MaxClients: maximum number of server processes allowed to start
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule prefork.c>
StartServers 5
MinSpareServers 5
MaxSpareServers 10
MaxClients 150
MaxRequestsPerChild 0
</IfModule>
# worker MPM
# StartServers: initial number of server processes to start
# MaxClients: maximum number of simultaneous client connections
# MinSpareThreads: minimum number of worker threads which are kept spare
# MaxSpareThreads: maximum number of worker threads which are kept spare
# ThreadsPerChild: constant number of worker threads in each server process
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule worker.c>
StartServers 2
MaxClients 150
MinSpareThreads 25
MaxSpareThreads 75
ThreadsPerChild 25
MaxRequestsPerChild 0
</IfModule>
**********************************************
Im starting to notice that the timouts of the apache are failing, cause looking with the server-status, the MaxClient is working fine (there are no more than 149 process running, but as i understand, when the MaxClient reaches his limit, it restart httpd service. In the logs im not seeing this happening).
However the "Timeout" doesnt seem right, cause the column called "SS" (Seconds since beginning of most recent request) is showing values over 60 (in fact, some of them over 1000!) and from different domains (that shows me that there isnt a problem with the server running SQUID, cause it happens with other domain in the Directadmin server too).
Can someone help me with this?
Thanks in advance.
Bye!
PD: Sorry for my poor English.
Im running Directadmin 1.33.7 with Apache 2.0.63 on a CentOS 5 (Final).
Theres another server running a SQUID for one of the domains in the Directadmin.
In the apache error_log i've seend this error repetead times when the httpd goes down (all the days, arround the same hour):
"[error] server reached MaxClients setting, consider raising the MaxClients setting"
Part of my httpd.conf:
**********************************************
Timeout 60
KeepAlive On
MaxKeepAliveRequests 100
KeepAliveTimeout 15
## Server-Pool Size Regulation (MPM specific)
# prefork MPM
# StartServers: number of server processes to start
# MinSpareServers: minimum number of server processes which are kept spare
# MaxSpareServers: maximum number of server processes which are kept spare
# MaxClients: maximum number of server processes allowed to start
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule prefork.c>
StartServers 5
MinSpareServers 5
MaxSpareServers 10
MaxClients 150
MaxRequestsPerChild 0
</IfModule>
# worker MPM
# StartServers: initial number of server processes to start
# MaxClients: maximum number of simultaneous client connections
# MinSpareThreads: minimum number of worker threads which are kept spare
# MaxSpareThreads: maximum number of worker threads which are kept spare
# ThreadsPerChild: constant number of worker threads in each server process
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule worker.c>
StartServers 2
MaxClients 150
MinSpareThreads 25
MaxSpareThreads 75
ThreadsPerChild 25
MaxRequestsPerChild 0
</IfModule>
**********************************************
Im starting to notice that the timouts of the apache are failing, cause looking with the server-status, the MaxClient is working fine (there are no more than 149 process running, but as i understand, when the MaxClient reaches his limit, it restart httpd service. In the logs im not seeing this happening).
However the "Timeout" doesnt seem right, cause the column called "SS" (Seconds since beginning of most recent request) is showing values over 60 (in fact, some of them over 1000!) and from different domains (that shows me that there isnt a problem with the server running SQUID, cause it happens with other domain in the Directadmin server too).
Can someone help me with this?
Thanks in advance.
Bye!
PD: Sorry for my poor English.
