How can I narrow down why Apache randomly stops serving pages? – Managing your servers can streamline the performance of your team by allowing them to complete complex tasks faster. Plus, it can enable them to detect problems early on before they get out of hand and compromise your business. As a result, the risk of experiencing operational setbacks is drastically lower.
But the only way to make the most of your server management is to perform it correctly. And to help you do so, this article will share nine tips on improving your server management and fix some problem about apache-2.2, mysql, wordpress, lamp, .
I am running a Turnkey Linux LAMP stack (based on Ubuntu). The server is hosting a relatively large WordPress installation with a pretty hefty amount of allocated RAM (on a dedicated machine). We get about half a million visitors a year, so it’s not overwhelming.
And yet, sometime between every four hours and every four days, the server just stops serving pages. I’ve looked in the Apache logs, and all I’ve found are some known errors where certain graphic images are no longer available. I haven’t found anything that seems to provide a clue why this is happening.
The machine itself doesn’t fail, because I can connect in via Webmin and reboot. Once I reboot, it works fine — again for a random amount of time.
So, where do I start trying to narrow down what’s happening? As far as I can tell, the Apache and MySQL processes are still running. Just nothing’s being service.
Any help would be much appreciated.
Could you have too many files open and need to issue ulimit -n [max files]? This happens quite often. The default on many systems can be as low as 256 open files.