check_local_disk basic question

[Jim Avery]

2009/3/5 Lance Raymond <lraymond at weatherflow.com>:
> Still new to it, but so far things are good.  I have added a remote
> host, monitoring load via snmp successfully, but my old alarm keeps
> tripping due to disk space.
>
> df -h shows;
> Filesystem       Size  Used Avail Use% Mounted on
> /fs here             660G  597G   64G  91% /
>
> so it seems 91% is in use, nagios is showing (nice and green);
> DISK OK - free space: / 27867 MB (92% inode=99%):
>
> The config for that machine (servername.cfg) shows;
> check_command                   check_local_disk!20%!10%!/
>
>
> So to me that says when 20% left warn me, 10% critical alarm, right?

You're right, but your check_disk plugin seems to be giving you wrong
results.  I wonder is it something peculiar to whichever
operating-system you are using?

I just tried it here on Ubuntu 8.04 LTS Server and got these results
(which I believe are fine):

$ /usr/local/nagios/libexec/check_disk -w 20% -c 10% -p /
DISK OK - free space: / 25541 MB (81% inode=97%);| /=5741MB;26353;29647;0;32942

$ df -h /
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda1              33G  5.7G   25G  19% /

You could also check your command definition to make sure there's
nothing silly in there, but I presume you're using the default from
your original install which should normally work fine.

Cheers,

Jim

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
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