It is a bit misused term error if "maxclients REACHED server setting, consider raising the maxclients setting".'s More a notification server administrator is warned limit exceeded" maxclients. "It is true that exceeded this limit, leading to instability and automatically Apache problems in functioning web sites hosted on the server.
Maxclients is Apache directive that sets request limit numberSites that can be served simultaneously. All queries that will be made above this limit will be put on hold until the number set by the Directive ListenBacklog. If servers using prefork, Maxclients translates into the maximum number of processes launched to serve requests sites. S default limit of concurrent request set by the 'maxclients "is 150. If we increase this limit, we must also consider increasing the value of the directive ServerLimit (Sets the maximum value for the lifetime of the Apache process). ServerLimit default is set to 256. Increase value maxclients must be directly proportional to ServerLimit.
Beware, however, that raising these two limits well above default values can prevent the Apache server from starting up and operating system instability. The higher the value ServerLimit is higher, the more additional memory (shared memory) will be assigned.
If you encounter error "[Error] server REACHED maxclients setting, consider raising the maxclients setting"(Visible in Apache Error Log) And you decide to change the values that we talked about above, you can do this in two ways.
1. Using the WHM you can change the values of Main >> Service Configuration >> Apache Configuration >> Global Configuration (Applies to servers that have installed cPanel / WHM)
2. Change values ServerLimit si Maxclients by editing httpd.conf. Usually httpd.conf can be found in "/ usr / local / apache / conf / httpd.conf".
After you change the values in httpd.conf, restart apache server. (service httpd restart).
Stealth Settings – Fix Apache Error: server setting REACHED maxclients.