The problem isn't necessarily with one site on the server, or with any certain user accessing the site too many times, but a total of the number of connections available to Apache.
One of my favorite ways to monitor Apache usage is with the "apachectl status" or "apachectl fullstatus" command, depending on how much information you'd like to receive about the current connections. Once you take a look at that data we have an article about using that information to determine more about the Apache resources here:
Understanding the Apache scoreboard
We also have an article about doing some additional troubleshooting with the Max Request Workers area here:
How do I troubleshoot Apache Max Request Workers errors?
so between those two pages that should give you a good start and tracking down the usage. It's best to try and do this as soon as possible as you notice the problem on the machine for the best results.
Commentaires
Enregistrer un commentaire