Hi,
I am running several DirectAdmin webservers and there's one server that is causing problems. The problem is that once a day (sometimes twice a day) the load of the server goes sky high (300+ and sometimes to 1000(!)).
I've noticed that during the high load there are about 500-600 httpd processes. Normally (under normal load) there are 10 httpd processes.
Needless to say, during the high load it's almost impossible to see anything in ssh or /server-status. They are both very inresponsive.
When I manage to "service httpd stop" (need to run this command several times before httpd actually shuts down), and start it again immediately after shutdown, the load goes down to 0.30 (average) until the next time the load goes sky high again.
The load is NOT jumping to 300+ on fixed times. So that rules out a cronjob.
Here's an example graph of high load (as you can see twice a day):
I have no clue where to look anymore, could you point me into a direction to fix this problem?
I am running several DirectAdmin webservers and there's one server that is causing problems. The problem is that once a day (sometimes twice a day) the load of the server goes sky high (300+ and sometimes to 1000(!)).
I've noticed that during the high load there are about 500-600 httpd processes. Normally (under normal load) there are 10 httpd processes.
Needless to say, during the high load it's almost impossible to see anything in ssh or /server-status. They are both very inresponsive.
When I manage to "service httpd stop" (need to run this command several times before httpd actually shuts down), and start it again immediately after shutdown, the load goes down to 0.30 (average) until the next time the load goes sky high again.
The load is NOT jumping to 300+ on fixed times. So that rules out a cronjob.
Here's an example graph of high load (as you can see twice a day):
I have no clue where to look anymore, could you point me into a direction to fix this problem?