Check_NRPE plugin issue after 3.0b7 upgrade.

[Marc Powell]

> -----Original Message-----
> From: nagios-users-bounces at lists.sourceforge.net [mailto:nagios-users-
> bounces at lists.sourceforge.net] On Behalf Of Lorand S. D'Caltan
> Sent: Wednesday, December 19, 2007 8:51 AM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Check_NRPE plugin issue after 3.0b7 upgrade.
> 
> I've migrated from 1.0 to 3.0b7 recently and I'm running into a couple
of
> issues, the most pressing of which is a problem with the check_nrpe
> plugin's return of data.


> This is the relevant part of the nrpe.cfg located on one of the
affected
> hosts:
> command[check_disk2]=/usr/local/nagios/libexec/check_disk -w 20 -c 15
-p
> /dev/sda10
> 
> Now this command works fine, and outputs this in Nagios:
> /db Partition
> 
> 
> OK 12-19-2007 09:37:54 4d 11h 53m 8s 1/3 DISK OK - free space: /db
3653 MB
> (4% inode=99%):
> 
> So, my problem here is that Nagios clearly sees that there is 4% of
disk
> space free, and yet still thinks the service is in an OK state. I need
it

You're only telling check_disk to warn if there are less than 20 KB
free, critical if less than 15 KB. If you mean to be talking about
percentages, you need to include the '%' sign. See --help for specifics
but here is the example --

Examples:
 check_disk -w 10% -c 5% -p /tmp -p /var -C -w 100000 -c 50000 -p /
    Checks /tmp and /var at 10% and 5%, and / at 100MB and 50MB

--
Marc


-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null