Hi Matthew,
I'm using check_snmp on OID: HOST-RESOURCES-MIB::hrFSRemoteMountPoint
You will get an output, like this:
HOST-RESOURCES-MIB::hrFSRemoteMountPoint.29 = STRING: "10.224.6.25:
/data/nfs/cp_backup"
The related check_snmp command would look like this:
-o HOST-RESOURCES-MIB::hrFSRemoteMountPoint.29 -s '"10.224.6.25:
/data/nfs/cp_backup"'
If you combine this and check_disk via check_multi, you should get an
accurate result.
Be aware, that the hrFSRemoteMountPoint.N may change during a reboot, but
you could also different script to get all RemoteMountPoints and search for
the desired one.
Regards
Oliver
Am Mo., 17. Dez. 2018, 18:18 hat Matthew Pounsett <m...@conundrum.com>
geschrieben:
>
> Before I start writing code that might be reinventing the wheel... does
> anyone have a favourite method for monitoring the presence of an NFS
> mount?
>
> check_disk is fine if the NFS volume is mounted and something goes wrong
> with it (like the NFS server going down) but gives a false positive if the
> volume simply isn't mounted. In that case it gives an OK result based on
> the closest enclosing volume of the mount point.
>
> For example, if I'm using check_disk to monitor an NFS volume mounted at
> /mnt/foo, it will correctly fail if the remote NFS server stops responding,
> but will report success if I 'umount /mnt/foo'. In that case it'll report
> OK and give the stats for the root ("/") volume.
>
>
>
