• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Restarted after kernel update, Plesk claims 25M percent CPU used

SteveL132

Basic Pleskian
Capture.PNG
I rebooted my CentOS 6.6 system running Plesk 12.0.18.25 after doing an update that included the kernel. The system seems to be running fine (after an initial scare where Apache wasn't working right, but a service restart fixed that), but Plesk is claiming that the system's CPU usage is 25 million percent. The graph looks a bit suspicious as well. Running top tells an entirely different story, with 99.8% idle.

What might have caused this Plesk glitch?
 
A few hours later and it's back to normal. My guess is that the CPU monitoring gets confused right after a reboot.
 
Hi SteveL132,

at each reboot there are a bunch of services, OS - depending configurations and lots of other stuff running to start your server. It is absolut normal on every computer, that you experience a high CPU load and a high memory usage, when you reboot your server. Depending on your settings ( intervall of the different checks ), these loads will be reduced to a "normal" state. This is no "Plesk" issue and it's not at all a problem.
 
So you don't think a reading of 25 million percent is a problem? I already noted that the actual CPU usage was low, but Plesk presented an absurd reading and indicated it was a problem.
 
Back
Top