Welcome to the GoFuckYourself.com - Adult Webmaster Forum forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact us. |
|
Discuss what's fucking going on, and which programs are best and worst. One-time "program" announcements from "established" webmasters are allowed. |
|
Thread Tools |
04-01-2007, 05:30 AM | #1 |
Too lazy to set a custom title
Join Date: Mar 2002
Location: Australia
Posts: 17,373
|
Any util to show which PHP script is creating extreme load?
Something is fecked on my server but I can't figure out what - I can see through 'top' that a few httpd processes are going mad with CPU usage, but I cannot track down the actual script that is causing it. The server runs several sites.
Is there something that can show me which script the apache version of php is executing at that time? 'ps' doesn't work since that shows the apache process, not the script name. |
04-01-2007, 05:42 AM | #2 |
The Dirty Frenchman
Industry Role:
Join Date: Nov 2005
Location: Lost Angeles
Posts: 8,904
|
Nope, not without using zend platform.
|
04-01-2007, 05:52 AM | #3 |
Confirmed User
Industry Role:
Join Date: Oct 2002
Location: lalaland
Posts: 2,120
|
Just add some logging of the execution time of the scripts.
|
04-01-2007, 05:55 AM | #4 |
Too lazy to set a custom title
Join Date: Mar 2002
Location: Australia
Posts: 17,373
|
Yep, I already have that in my Apache logs... the problem is that I wasn't looking at that particular log! I used 'locate' to find the logs to parse but that didn't include a site I recently moved. I discovered this by accident when I started manually working through each site's logs.
I have the culprit under control now...... it's a tiny site but a cheater was sending 3-4 loads per minute which in this case was enough to cause some serious problems. |