View Full Version : Normal load only have 200+ tasks, but sometime suddenly get High load with 500+ tasks

10-28-2010, 08:40 PM
Guys i am despert here, already get this problem for a week sometime suddenly get high load, and still dont find where is the problem yet

normally the top result like this, load only 0.71, only have 200+ tasks

other screenshots : http://i291.photobucket.com/albums/ll284/basketmen/topnormal2.jpg

but sometime suddenly get high load (usually 1-3 times a day), load very high 90-200, with 500+ tasks

other screenshots : http://i291.photobucket.com/albums/ll284/basketmen/tophighload2.jpg

Daily Process Log, i already repair and optimize all table, like you can see the mysql process is very low (in white line, not in yellow or red line), so its looks like the problem is not in mysql
The red line is maybe apache

Nb1. I use a dedicated server, only host 1 site, here is my server specs
Intel Single Xeon E3110 3.0ghz L2 cache 6MB
Memory 4 GB DDR2 RAM
Harddisk 500 GB Sata 7200rpm
Cent OS 5.4

Nb2. I already check no backup/cronjob or related scheduled active right now

Nb3. I already disabled the feature one by one, Even i already block all search engine spider now using robots.txt disallow for 2 days, no spiders again in my website until the problem found, its ok i just need to found the source problem

Nb4. I dont think my hosting support can help it, and they cost very expensive for that extra managed service ($69/hour), i want to find the source problem by my self, please analyze and give advice to found the source problem

10-29-2010, 08:46 PM
Looking at the multiple 'D' states of many of those httpd processes, coupled with the hideous 96.2% of processes WAiting for I/O, id be asking myself what httpd (apache) is trying to open *or* if it's having trouble reading from a shared NFS drive/mount (outside possibly that it the drive could be failing).

The starting point would be the access/error logs when this happens - slim possibility of a Slow loris type of attack - that tends to show as low resource use, machine responding normally but Apache unreachable. Again, logs, logs, logs (apache/syslog/daemon) is the starting point.