• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

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