• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Resolved Two bugs in Plesk 10.3.1 (and below)

King555

Regular Pleskian
Three bugs in Plesk 10.3.1 (and below)

These three bugs were in Plesk for a quite long time and still have not been fixed in 10.3.1 (with Microupdates installed):

1.) The daily (or weekly, ...) mail of Watchdog always says "Watchdog is running since" and then the time of the mail sending. I always get the daily mail at 1 am and so I get "Watchdog is running since 01:00". This does not make sense, does it?

2.) I changed the settings of the Health Monitor. But after an update it does not read my settings, although these settings are still saved (I can download them). The only solution: Download it, reset to system default and reupload. But why is this neccessary?

3.) The Watchdog monitoring of "Plesk Web Server" does not work (it says, it is not running). But the Plesk Web Server is online, I can access Plesk at any time without problems.

I use Debian 5.
 
Last edited:
King555, thank you very much for your bug reports.

We reproduced 1 & 3 problems.
Could you help to us with 2nd problem? Next information will be useful:
1. what debian do you use - x32 or x64?
2. How did you perform upgrade (from which Plesk version)?
3. Can you provide file with settings for Health Monitor?
 
Now I am not completely sure anymore, whether it's really a bug or not. But first of all, here are the requested things:

1.) x64
2.) I always upgrade to the very next version, i.e. 10.3.0 => 10.3.1 => 10.3.1 MU, I don't make bigger steps.
3.) See attachment

I can remember, that after one of the last updates (not the very last) I had to reupload my config file to make the Health Monitor work again with my settings.

When I first used the Health Monitor, I got a lot of warnings via mail. Then I changed (doubled) the percent values of the Apache CPU and RAM usage, which should be allowed (and changed the interval to 30 minutes).

Then I got a very small amount of mails for some time. After the last update I got many mails again. So I thought it's that bug again and I posted it here. But now I reuploaded the configuration and I still get those mails. So maybe it's not that bug anymore.

But my CPU usage is maximum 25-30% during the day and I get mails with Apache CPU usage Red and Yellow (which means 50 and 40 percent, if the HM reads my config).

So now you have to decide, whether there is some kind of bug.
 

Attachments

  • custom-health-config.zip
    2.6 KB · Views: 3
Issues 1 and 3 are still not resolved with the very latest version of Plesk. Will they be fixed in one of the next updates?
 
Bug 3 is still not fixed (Plesk webserver monitoring). I currently use Debian 6.0.9 x64 and latest Plesk 11.5.
 
Back
Top