I’m posting this here because I think it might save some people some time.
Last night and all of this morning I have been struggling with errors of the following type:
[Wed Sep 09 11:58:57 2009] [error] server reached MaxClients setting, consider raising the MaxClients setting
I have recently moved a client to a new Plesk server, and Apache would occasionally stop responding. Investigation showed that the MaxClients setting in Apache was being reached, due to a misconfiguration, and that httpd would just stop responding. Not a wonderful thing to have happen on a large site.
So, naturally, I checked out
/etc/httpd/conf/httpd.conf, found the MaxClients setting, edited, saved, and restarted Apache. No dice.
Then I discover that any increase in MaxClients should ensure that ServerLimit – so I checked, restarted, no dice. Still.
As it turns out, a Plesk server overwrites a bunch of stuff that you set in
/etc/httpd/conf/httpd.conf using a file located at
This was the file that was setting my MaxClients to 10! Grr!
Edited the file, stopped and restarted Apache, so far, no more timeouts!
And with a sum total of 3 minutes work, OK Sushi is now running the latest Textpattern version, 4.2.0
What’s new under the hood? Well, I subscribe to the mailing list, and as such see all the SVN commits, so I know there is quite a bit happening here. The new admin interface looks great. I no longer get a silly error in the footer of it, either.
This sexy new CMS version does not change the fact that my design is getting old, and isn’t achieving what I want it to. So, I’m putting together a sort of ‘roadmap’ for where I want to take my website. Maybe, just maybe, by speaking these words in public, I might be able to set aside some time to actually do it.
OK? Sound good?
I laughed at this – users with IE6 receive it at Momentile.com