Quote:
Originally Posted by liquidmoe
Sometimes when you have high CPU processing on httpd processes and nothing else it could be indicative of poorly structured rewrite rules in one of your .htaccess files.
You may want to take a look at that.
|
Good idea. The main site does use a 404 rewrite, and it's been working for 5 years now with up to 100,000 visitors a day at it's peak, but maybe I changed something in one of the other smaller sites.
Quote:
Originally Posted by CYF
that top output looks fine 
Every 12 or 18 hours? You have anything setup in cron that is processor intensive?
Have you checked logs for bots? Sometimes they hammer a site and bring it to a crawl.
Are you running apache? What version? What OS? |
Running CentOS, apache, basic LAMP server...CentOS release 4.8 (Final)
I will shut down all my cron jobs to make sure. I forgot about that! But shutting down MySQL should shut down any cron jobs that use MySQL data. But good idea!
I don't think it's bots or traffic, because if it was just too much traffic, then after restarting apache, it would get stuck straight away again. It happens at odd times.
Here is some interesting notes when I managed to "catch it in the act" of getting stuck. When it is starting to get stuck, I notice uptime will start to report higher and higher values. During this time I can get the apache status. Once its stuck, then I can't. But I did manage to catch it in the act, and here is what uptime showed me:
0.12 0.08 0.09
5.12 0.12 0.08
30.2 5.12 0.12
90.0 30.2 5.12
150.1 150.2 149.0
(server is now toast)
In a very short time, it's as if it gets "stuck". Once it's stuck, I shutdown apache, restart it, then everthing runs fine for 13 more hours, then it happens again.
lynx --dump localhost/whm-server-status
So, tell me what you make of these apache status reports:
http://www.photofight.com/xx.txt (started to get stuck)
http://www.photofight.com/xy.txt (a little more stuck)
http://www.photofight.com/xz.txt (now it's really stuck)
Notice the jump halfway down, where the milliseconds for a response becomes 1921913212 ?!?!? Search for 9068 and you will see q2growth.com GET /Printing-Supplies/Printing-Supplies.html HTTP/1.1
Shutdown apache and restarted:
http://www.photofight.com/xq.txt (yay its not stuck)
If it was simply too much traffic, then restarting apache would cause it to overload immediatly. So it can't be just a matter of too much traffic. There is something fishy and I can't figure it out. I can't work on ANY more websites until I figure this out too, since I don't have any money coming in while its 'stuck' and it is top priority.
I love the word stuck. Its the best way to describe it.
Ideas? Notice how requests build up, but dont get out! They just stack on top of each other!