Facebook
Twitter-
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!
-
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.
Update from 12.0.18 Update #2 to 12.0.18 Update #3 Server health issues
- Thread starter Alex--
- Start date
- Status
I have checked and found that bug PPP-932 is not fixed yet. Fix is planned for next Plesk version.
The problem in that we do not convert jiffies into percent. CPU plugin report data as JIFFIES, not percent.
From collectd FAQ http://collectd.org/faq.shtml()
---------------------------------------------------------------------
Why don't the CPU states sum up to 100%?
Because the CPU plugin does not collect the CPU usage in percent, but rather in "jiffies". A jiffy is the time-unit which the scheduler in the operating systems uses to manage run times of applications. Under Linux, the default configuration is to have 100 jiffies per second, which leads many users to believe they're getting a percentage. You can, however, configure your kernel at compile time to use 250 or 1000 jiffies per second, usually resulting in a more responsive system but IO-throughput is decreased. Especially on busy systems, virtual systems and systems with a "tickless kernel" there may not always be the exact number of intended jiffies in one second, resulting in the variance you've notice in the graphs.
By the way, that you see this issue in collectd but not in other similar tools is due to the fact that collectd collects data much more frequently. Over the timespan of five minutes these variations usually even out pretty good and you're being sold a percentage but actually get - jiffies…
---------------------------------------------------------------------
The problem in that we do not convert jiffies into percent. CPU plugin report data as JIFFIES, not percent.
From collectd FAQ http://collectd.org/faq.shtml()
---------------------------------------------------------------------
Why don't the CPU states sum up to 100%?
Because the CPU plugin does not collect the CPU usage in percent, but rather in "jiffies". A jiffy is the time-unit which the scheduler in the operating systems uses to manage run times of applications. Under Linux, the default configuration is to have 100 jiffies per second, which leads many users to believe they're getting a percentage. You can, however, configure your kernel at compile time to use 250 or 1000 jiffies per second, usually resulting in a more responsive system but IO-throughput is decreased. Especially on busy systems, virtual systems and systems with a "tickless kernel" there may not always be the exact number of intended jiffies in one second, resulting in the variance you've notice in the graphs.
By the way, that you see this issue in collectd but not in other similar tools is due to the fact that collectd collects data much more frequently. Over the timespan of five minutes these variations usually even out pretty good and you're being sold a percentage but actually get - jiffies…
---------------------------------------------------------------------
- Status
