Monit fails to start if monitored filesystem is missing

[Former user]

Hello,

After upgrading from 5.20 to 5.25 Monit fails to start with error such as:

Starting daemon monitor: monitLookup for '/home/7d6cc10a' filesystem failed -- not found in /proc/self/mounts Filesystem '/home/7d6cc10a' not mounted /etc/monit/monitrc:230: Cannot read usage of filesystem /home/7d6cc10a '4' failed!

Filesystem indeed isn't there because of the disk issue which is being repaired, but otherwise machine is working fine. Monit should alert about this, but start normally and continue to monitor other services. There is no reason stuff like CPU, memory, network and services not to be monitored just if one disks dies. Please note that it was working like that in the past, so this could be considered as a regression.

Regards, Vedran

[Tildeslash]

Duplicate of #693.

[Tildeslash]

Hello,

the problem is solved already in the development version, we'll release the new version ca. within two weeks.

You can get the development snapshot if you want:

wget https://bitbucket.org/tildeslash/monit/get/master.tar.gz
tar -xzf master.tar.gz
cd tildeslash*
./bootstrap
./configure
make