Re: Monit fails to monitor filesystem, says "'var' unable to, read filesystem /dev/dm-12 state"

[Odin Kroeger]

Am 22.02.2011 18:02, schrieb Jan-Henrik Haukeland:
> Please upgrade to Monit 5.2.4 and let us know if the problem persist.
> You can download a precompiled binary of Monit from
> http://mmonit.com/monit/download/ and replace it with your existing
> version.

I did so and the problem persists (but see below); however, the output
from monit -Iv has become far more useful, the relevant portion reads:

Device /dev/dm-13 not found in /etc/mtab
-------------------------------------------------------------------------------
    ./monit() [0x40903d]
    ./monit() [0x40977f]
    ./monit() [0x425e6b]
    ./monit() [0x41a6e3]
    ./monit() [0x41a798]
    ./monit() [0x418a8f]
    ./monit() [0x41896b]
    ./monit() [0x40b697]
    ./monit() [0x40bf08]
    /lib/libc.so.6(__libc_start_main+0xfd) [0x7f02bcf4cc4d]
    ./monit() [0x40422a]
-------------------------------------------------------------------------------
'var' unable to read filesystem /dev/dm-13 state
-------------------------------------------------------------------------------
    ./monit() [0x40903d]
    ./monit() [0x40977f]
    ./monit() [0x406c77]
    ./monit() [0x418dd5]
    ./monit() [0x41896b]
    ./monit() [0x40b697]
    ./monit() [0x40bf08]
    /lib/libc.so.6(__libc_start_main+0xfd) [0x7f02bcf4cc4d]
    ./monit() [0x40422a]
-------------------------------------------------------------------------------


Knowing this, I could solve the issue by modifying /etc/monitrc as follows:

  check device var with path /dev/mapper/ister-var    ->
  check device var with path /var

Apparently, this is the preferred syntax anyway (reading the manual
again left me wondering why I specified a device rather than a path in
the first place), but maybe you could add a note about this somewhere.


Thanks,

Odin Kroeger