If I run the command /usr/lib64/nagios/plugins/check_disk -w 20% -c 10% -p /dev/mapper/VolGroup01-infoVol00 from the server that its getting monitored it outputs the information ok like the following: DISK CRITICAL - free space: /vservers/fred/data 6113 MB (5% inode=99%);| /vservers/colombia/info =108694MB;96760;108855;0;120951 If I use the mount point when running the line from the monitored server it also gives the proper output. Now, If I use the check_nrpe with the check_disk option from the nagios server is when it give incompleted output like the following: DISK UNKNOWN - free space:| If specify the mount point in the nrpe.cfg of the monitored server and then run the check_nrpe with the check_disk from the nagios server. It gives the following: DISK CRITICAL - /vservers/colombia/info does not exist Any inputs? On Dec 18, 2007 1:05 PM, mark redding <<a href="mailto:mwjredding@gmail.com">mwjredding@gmail.com</a>> wrote: > Hi, > > On 18/12/2007, Jake Solid <<a href="mailto:richardsolid@gmail.com">richardsolid@gmail.com</a>> wrote: > > Thanks for your reply. > > > > Here is how the command looks like: > > > > command[check_disk3]=/usr/lib64/nagios/plugins/check_disk -w 20% -c > > 10% -p /dev/mapper/VolGroup01-infoVol00 > > Could possibly be the length of the device name. I've always used the > mountpoint in this command rather than the device :- > > command[check_disk3]=/usr/lib64/nagios/plugins/check_disk -w 20% -c > 10% -p /vservers/colombia/info > > It may even be something as simple as a misconfiguration in the > service definition which means that it's not actually calling the > check_disk3 nrpe command at all (though not likely as you get the > problem when you run interactively too). > > -- > bright blessings, > Mark >