• 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.

Watchdog: "Disks monitoring" strange behaviour

King555

Regular Pleskian
I'm using Plesk 10.1.1 under Debian 5. Since the update from 10.0.1 to 10.1.1 there is a strange behaviour in the Watchdog "Disks monitoring" feature:

When the icon under the headline "Tools" shows "Enable", which meant that the monitoring is currently disabled in previous versions of Watchdog, the "M"-icon below says, that monitoring is enabled and I can click on the device name.

If I click "Enable" (the icon), the "M"-icon says, monitoring is disabled and I can't click the device name.

So how can I determine whether monitoring of disks is enabled or disabled? There is an asynchronism between the upper and the lower icon.

Edit: The Watchdog daily mail, which now works again with 10.1.1, shows me that disk monitoring ist NOT working. So this seems to be a bug!
 
Last edited:
Now I installed Plesk 10.2.0 and after clicking the disk monitoring button I got a message like "cannot write to monitrc". After that, I cannot open the disk monitoring status. I get the following error:

ERROR: WDCPExc

--------------------------

Disk: unable to select: no such row in the table

--------------------------
0: Disk.php:30
Disk->Disk(string '/dev/md1')
1: modules.watchdog.disk.properties.php:20
plesk__modules__watchdog__disk__properties->accessItem(string 'GET', NULL null)
2: UIPointer.php:595
UIPointer->access(string 'GET')
3: plesk.php:42

I already disabled and re-enabled Watchdog and I tried to click the disk monitoring button. But this has no effect. I always get this error message after opening the detailed status.

Any ideas?
 
Back
Top