• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

High Apache CPU Usage

C

CraigLath218

Guest
--------------------------------------------------------------
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Panel 10.1.1, CentOS 5 (we tried 64 bit and 32), Dual Quad Core Xeon 2.66 - 6GB Ram - RAID 10 15K SCSI Drives

PROBLEM DESCRIPTION AND STEPS TO REPRODUCE

Apache CPU usage is constantly very high. Sits in the 80 to 90% spikes up to 140%. I can't find any real documentation that says exactly what the apache CPU usage referes to. Is that a fraction of CPU time total. Does it actually matter that it is above 80 to 90%? Actual CPU usage is showing in the 5% range (in the control panel). We tried switching to FastCGI with no real effect. We also removed Watson with no effect (then we put it back).

A few httpd processes seem to get stuck and stay around for minutes. I watched one that hung out for maybe 5 minutes. This was right after a reboot so I don't think any users were downloading big files.

Has anyone else had any issues with this or found a solution?

ACTUAL RESULT

Really high Apache CPU Usage

EXPECTED RESULT

Not really high Apache CPU Usage

ANY ADDITIONAL INFORMATION
 

Attachments

  • top.jpg
    top.jpg
    147.2 KB · Views: 65
Suggestion

Load is high,

Try:

netstat -napt

it will tell you who is connected on port 80 or 443

Find out the source & destination IP(s), check /var/log/httpd/access_logs & error_log & /var/www/vhosts/<domain>/statistics/logs/access_log & error_log

I'd also suggest download apachetop, it will definitely help.
 
Its a pretty broad area of investigation there :p

I'd also throw mod_top into the ring as another tool for collecting more information.
 
Can anyone tell me what the Apache CPU % mesure actually means. Obviously it's not a mesure of actual CPU usage, is it simply a measure of the percentage of CPU time being used by apache? For example my CPU is running at 10% and apache is using 5%. Does this mean that the Apache CPU% will show as 50%?

I can't seem to find any mention of this in the Plesk documentation, but perhaps I have the wrong user guide.

Thank you for the posts with the debugging suggestions, I'm still trying to make sense of what exactly the results mean other than the fact that we have a busy server.
 
So the current theory is that Plesk 10 health monitoring stats cannot account for multi core processors. In our case with 8 total cores a 50% apache load would actually be 16% processor load. That seems to be consistant with what we are seeing on our server.

Can anyone confirm this?
 
Same situation.. apache CPU usage is rediculously high considering there's almost no traffic.
The server runs multicore, too. This has to be a bug with plesk - whereever I search in the shell (processes etc.) the values of CPU time/usage don't even get close to the values mentioned inside plesk. Hope this has been fixed in 10.3, gonna run the update now...
 
You can adjust the health monitoring XML file, increase the thresholds, to reduce the number of warnings.
 
Back
Top