• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Health Monitor Problem - Execution failed

futureweb

Regular Pleskian
Hello,

since we upgraded our Plesk Server to 11.5 the Health-Monitor is giving us some problems.
I tried to do a Hardware Refresh because the Partition Size changed - but it always gives me this Error:

Error: Execution failed. Command: /bin/df Arguments: Array ( [0] => -Pl ) Details: /bin/df: ` (deleted)/var/named/chroot/etc/named.rfc1912.zones': No such file or directory /bin/df: ` (deleted)/var/named/chroot/etc/named.iscdlv.key': No such file or directory /bin/df: ` (deleted)/var/named/chroot/etc/named.root.key': No such file or directory

Output on CLI is also weird?
[root@kdn7 ~]# df
df: ` (deleted)/var/named/chroot/etc/named.rfc1912.zones': No such file or directory
df: ` (deleted)/var/named/chroot/etc/named.iscdlv.key': No such file or directory
df: ` (deleted)/var/named/chroot/etc/named.root.key': No such file or directory
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/vzfs 283115520 98676120 184439400 35% /
none 3145728 4 3145724 1% /dev
/dev/vzfs 283115520 98676120 184439400 35% /var/named/chroot/etc/named
/dev/vzfs 283115520 98676120 184439400 35% /var/named/chroot/var/named
/dev/vzfs 283115520 98676120 184439400 35% /var/named/chroot/etc/rndc.key
/dev/vzfs 283115520 98676120 184439400 35% /var/named/chroot/usr/lib64/bind

But the Files exists:
[root@kdn7 ~]# ll /var/named/chroot/etc/named.rfc1912.zones
-rw-r----- 0 root named 931 Jun 21 2007 /var/named/chroot/etc/named.rfc1912.zones

[root@kdn7 ~]# ll /var/named/chroot/etc/named.iscdlv.key
-rw-r--r-- 0 root named 2389 Jul 31 2012 /var/named/chroot/etc/named.iscdlv.key

[root@kdn7 ~]# ll /var/named/chroot/etc/named.root.key
-rw-r--r-- 0 root named 487 Jul 19 2010 /var/named/chroot/etc/named.root.key

mount also thinks they are deleted?
[root@kdn7 ~]# mount -l
/dev/vzfs on / type vzfs (rw,relatime)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /dev type devtmpfs (rw,relatime,size=3145728k,nr_inodes=786432,mode=755)
none on /dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
/dev/vzfs on (deleted)/var/named/chroot/etc/named.rfc1912.zones type vzfs (rw,relatime)
/dev/vzfs on (deleted)/var/named/chroot/etc/named.iscdlv.key type vzfs (rw,relatime)
/dev/vzfs on (deleted)/var/named/chroot/etc/named.root.key type vzfs (rw,relatime)
/dev/vzfs on /var/named/chroot/etc/named type vzfs (rw,relatime)
/dev/vzfs on /var/named/chroot/var/named type vzfs (rw,relatime)
/dev/vzfs on /var/named/chroot/etc/rndc.key type vzfs (rw,relatime)
/dev/vzfs on /var/named/chroot/usr/lib64/bind type vzfs (rw,relatime)

Not really sure what's going wrong here? Hope someone here can help me out. :)

Thank you
Andreas Schnederle-Wagner
 
df: ` (deleted)/var/named/chroot/etc/named.rfc1912.zones': No such file or directory
df: ` (deleted)/var/named/chroot/etc/named.iscdlv.key': No such file or directory
df: ` (deleted)/var/named/chroot/etc/named.root.key': No such file or directory

This most probably means that filesystem (vzfs) of the VPS is corrupted, and there are broken vzlinks, as files are basically exist in the container. So, it is problem in Virtuozzo side and should be fixed with Virtuozzo utilities on hardware node.
 
This most probably means that filesystem (vzfs) of the VPS is corrupted, and there are broken vzlinks, as files are basically exist in the container. So, it is problem in Virtuozzo side and should be fixed with Virtuozzo utilities on hardware node.

Hi Igor,

could you maybe point me in the right direction which Virtuozzo Commands / Command Options to look at?

Thank you
Andreas
 
Sorry, I'm not familiar with Virtuozzo enough. I suggest you contact Support Team.
 
Sorry, I'm not familiar with Virtuozzo enough. I suggest you contact Support Team.

No Virtuozzo Pro sitting next to you? ;-)

Guess I figured it out myself ... (quite some time ago when I last needed this Command ...): vzfsutil --call=ignore --oall=ignore -i -p -t /vz/template /vzCT202/private/202/ (only do scan - no repairs)

Will see what it reports and report back.

Andreas
 
alright - did a check with vzfsutil - and no problems mit the VZFS got reported - seems like the VZFS is working as expected?!
 
Back
Top