• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • 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.

Apache2 process using 100% of CPU

SalvadorS

Regular Pleskian
Hello,

I am running plesk 10.3.1 in Debian 6.

I have some type of problem in the server. I have a lot of apache2 process which are using 100% of CUP load:

If I do a top:

9462 www-data 20 0 410m 118m 4092 R 45.9 1.2 0:48.97 apache2
9668 www-data 20 0 410m 117m 3080 R 44.0 1.2 0:27.71 apache2

If I kill the process. New process will be created with also 100% cpu load used.

If I execute this:

lsof -p 9668

I can see that particular apache2 process is handling some kind of process with the logs:

apache2 9668 www-data 709w REG 254,1 0 4260587 /var/www/vhosts/*/statistics/logs/access_log
apache2 9668 www-data 710w REG 254,1 0 4260588 /var/www/vhosts/*/statistics/logs/access_ssl_log
apache2 9668 www-data 711w REG 254,1 62810 4212463 /var/www/vhosts/*/statistics/logs/access_log
apache2 9668 www-data 712w REG 254,1 0 4212464 /var/www/vhosts/*/statistics/logs/access_ssl_log
apache2 9668 www-data 713w REG 254,1 12093 4212405 /var/www/vhosts/*/statistics/logs/access_log
apache2 9668 www-data 714w REG 254,1 0 4212406 /var/www/vhosts/*/statistics/logs/access_ssl_log
apache2 9668 www-data 715w REG 254,1 25496 4211132 /var/www/vhosts/*/statistics/logs/access_log
apache2 9668 www-data 716w REG 254,1 0 4211133 /var/www/vhosts/*/statistics/logs/access_ssl_log
apache2 9668 www-data 717w REG 254,1 15645 4210821 /var/www/vhosts/*/statistics/logs/access_log
apache2 9668 www-data 718w REG 254,1 0 4210822 /var/www/vhosts/*/statistics/logs/access_ssl_log
apache2 9668 www-data 719w REG 254,1 0 4210726 /var/www/vhosts/*/statistics/logs/access_log
apache2 9668 www-data 720w REG 254,1 0 4210727 /var/www/vhosts/*/statistics/logs/access_ssl_log

* are all the domains in the server. I don´t know how to stop it. I kill cron.daily and also statistics but still have the same problem. Any help?
 
What's the output of the following commands?
netstat -tenp| grep ${offending_apache_pid}
for pid in `pgrep -u www-data`; do echo -n "$pid " ; find /proc/${pid}/cwd -printf "%l\n" ; done
 
Hello,

Thanks for the update. I re-run the cron daily script and when it finished problem "dissapear" so no the server works fine.

Thanks a lot.
 
Back
Top