Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MaxClients of 350 exceeds ServerLimit value of 256 servers

Status
Not open for further replies.

csgonan

MIS
May 2, 2007
118
US
I just upgraded a solaris 9 server to apache 2.2.8 from 2.2.6, using the same configuration. I am now getting the error/warning when I restart (either gracefully or not). If I change the number of MaxClients to 250, I do not get the error about MaxClients but I still get the Warning (about "attempt to change...). My server limit is 350 and even if MaxClients is the same, I get this error.

As I said, I am using the same configuration as I did with 2.2.6 and I did not have those messages. Is there a bug in 2.2.8?

Thank you

[Sat May 10 12:29:11 2008] [notice] SIGHUP received. Attempting to restart
WARNING: MaxClients of 350 exceeds ServerLimit value of 256 servers,lowering MaxClients to 256. To increase, please see the ServerLimit directive.
[Sat May 10 12:29:14 2008] [warn] WARNING: Attempt to change ServerLimit ignored during restart
[Sat May 10 12:29:14 2008] [notice] Apache/2.2.8 (Unix) mod_ssl/2.2.8 OpenSSL/0.
9.8g configured -- resuming normal operations
 
ServerLimit (I think) can only be changed done at startup. A restart is not sufficient. A graceful stop / start is required.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top