• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Apache is consuming a lot of CPU. How do I find the reason?

kevang

New Pleskian
I tried to follow the steps in this knowledge base article, but it seems it is not applicable to my Plesk version (12.0). There is no central httpd.conf. I added the configuration lines to /etc/apache2/conf-enabled/security.conf instead. But then going to http://my.server.name/server-status just gives a "Forbidden" error, even if I "Allow from all".

What am I doing wrong?

Is there another way to track down which site/s script/s are generating load?
 
Nope, that's not it. I don't have too many open files, it's the CPU share on my virtual server that is periodically getting too high.

I want to determine which site/s and script/s are causing this, as described in the knowledge base article I linked to (but which unfortunately is not applicable to my Plesk version).
 
Found it: /etc/apache2/mods-enabled/status.conf needs to be edited to allow access from the desired computer.

I also realized that this shows only the current status, thus doesn't really help with finding out which sites or scripts are causing high CPU usage on a regular basis. :( Any tips concerning that?
 
Back
Top