<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40"> <head> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 11 (filtered medium)">  <style>  </style> </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> It is working as expected… It’s expecting to check FREE space, not USED space.<o:p></o:p> <o:p> </o:p> ----<o:p></o:p> check_disk (nagios-plugins 1.4.2) 1.57<o:p></o:p> Copyright (c) 1999 Ethan Galstad <nagios@nagios.org><o:p></o:p> Copyright (c) 1999-2004 Nagios Plugin Development Team<o:p></o:p> <nagiosplug-devel@lists.sourceforge.net><o:p></o:p> <o:p> </o:p> This plugin checks the amount of used disk space on a mounted file system<o:p></o:p> and generates an alert if free space is less than one of the threshold values.<o:p></o:p> <o:p> </o:p> Usage: check_disk -w limit -c limit [-p path | -x device] [-t timeout] [-m] [-e]<o:p></o:p> [-v] [-q]<o:p></o:p> <o:p> </o:p> Options:<o:p></o:p> -h, --help<o:p></o:p> Print detailed help screen<o:p></o:p> -V, --version<o:p></o:p> Print version information<o:p></o:p> -w, --warning=INTEGER<o:p></o:p> Exit with WARNING status if less than INTEGER --units of disk are free<o:p></o:p> -w, --warning=PERCENT%<o:p></o:p> Exit with WARNING status if less than PERCENT of disk space is free<o:p></o:p> -c, --critical=INTEGER<o:p></o:p> Exit with CRITICAL status if less than INTEGER --units of disk are free<o:p></o:p> -c, --critical=PERCENT%<o:p></o:p> Exit with CRITCAL status if less than PERCENT of disk space is free<o:p></o:p> -C, --clear<o:p></o:p> Clear thresholds<o:p></o:p> -u, --units=STRING<o:p></o:p> Choose bytes, kB, MB, GB, TB (default: MB)<o:p></o:p> -k, --kilobytes<o:p></o:p> Same as '--units kB'<o:p></o:p> -m, --megabytes<o:p></o:p> Same as '--units MB'<o:p></o:p> -l, --local<o:p></o:p> Only check local filesystems<o:p></o:p> -p, --path=PATH, --partition=PARTITION<o:p></o:p> Path or partition (may be repeated)<o:p></o:p> -x, --exclude_device=PATH <STRING><o:p></o:p> Ignore device (only works if -p unspecified)<o:p></o:p> -X, --exclude-type=TYPE <STRING><o:p></o:p> Ignore all filesystems of indicated type (may be repeated)<o:p></o:p> -M, --mountpoint<o:p></o:p> Display the mountpoint instead of the partition<o:p></o:p> -e, --errors-only<o:p></o:p> Display only devices/mountpoints with errors<o:p></o:p> -w, --warning=DOUBLE<o:p></o:p> Response time to result in warning status (seconds)<o:p></o:p> -c, --critical=DOUBLE<o:p></o:p> Response time to result in critical status (seconds)<o:p></o:p> -t, --timeout=INTEGER<o:p></o:p> Seconds before connection times out (default: 10)<o:p></o:p> -v, --verbose<o:p></o:p> Show details for command-line debugging (Nagios may truncate output)<o:p></o:p> Examples:<o:p></o:p> check_disk -w 10% -c 5% -p /tmp -p /var -C -w 100000 -c 50000 -p /<o:p></o:p> Checks /tmp and /var at 10%,5% and / at 100MB, 50MB<o:p></o:p> <o:p> </o:p> Send email to nagios-users@lists.sourceforge.net if you have questions<o:p></o:p> regarding use of this software. To submit patches or suggest improvements,<o:p></o:p> send email to nagiosplug-devel@lists.sourceforge.net<o:p></o:p> <o:p> </o:p> <div> <div class=MsoNormal align=center style='text-align:center'> <hr size=2 width="100%" align=center tabindex=-1> </div> From: nagios-users-bounces@lists.sourceforge.net [mailto:nagios-users-bounces@lists.sourceforge.net] On Behalf Of Martin J. Green Sent: Wednesday, July 26, 2006 11:47 AM To: nagiosplug-help@lists.sourceforge.net Cc: nagios-users@lists.sourceforge.net Subject: [Nagios-users] plugns<o:p></o:p> </div> <o:p> </o:p> Having some bizarre problems with plugins – nagios says they don’t exist (or passes bollocks output in some cases), even when I’ve explicitly told it where they are.<o:p></o:p> <o:p> </o:p> Take one example…<o:p></o:p> <o:p> </o:p> [root@agw01 nagios]# /usr/libexec/nagios/check_disk -w 85% -c 95% -p /dev/hda1<o:p></o:p> INPUT ERROR: C_DFP (95.000000) should be less than W_DFP (85.0) and both should be between zero and 100 percent, inclusive for /dev/hda1<o:p></o:p> check_disk: Could not parse arguments<o:p></o:p> Usage: check_disk -w limit -c limit [-p path | -x device] [-t timeout][-m] [-e] [-W limit] [-K limit] [-v] [-q]<o:p></o:p> [root@agw01 nagios]# /usr/libexec/nagios/check_disk -w 95% -c 85% -p /dev/hda1<o:p></o:p> DISK CRITICAL - free space: / 1776 MB (30% inode=84%);| /=4130MB;295;885;84;5905<o:p></o:p> [root@agw01 nagios]# df<o:p></o:p> Filesystem Size Used Avail Use% Mounted on<o:p></o:p> /dev/hda1 5.8G 3.8G 1.8G 69% /<o:p></o:p> /dev/hda6 32G 27G 5.5G 83% /home<o:p></o:p> [root@agw01 nagios]#<o:p></o:p> <o:p> </o:p> <![if !supportLists]>1) <![endif]>Critical & warning seem to be the wrong way round? (Critical *should* be higher than warning, right?)<o:p></o:p> <![if !supportLists]>2) <![endif]>Why did it tell me my disk was critical – its below both thresholds??<o:p></o:p> <o:p> </o:p> Anything I should be doing – can’t seem to figure out why its not picking them up.<o:p></o:p> <o:p> </o:p> ___________________________________________________________________________________________________<o:p></o:p> The questions remain the same. The answers are eternally variable.<o:p></o:p> <div> <o:p></o:p> </div> <div> Martin J. Green<o:p></o:p> </div> <div> Altien Ltd<o:p></o:p> </div> <div> E: <a href="mailto:mgreen@altien.com">mgreen@altien.com</a><o:p></o:p> </div> <o:p> </o:p> </div> </body> </html>