check_disk with many ARGS over nrpe

[Kyle O'Donnell]

Here is the command running locally:

/opt/nagios/libexec/check_disk -e -w 10% -c 5% -p / -w 10% -c 5% -p
/var -w 10% -c 5% -p /opt/gw -w 10% -c 5% -p /opt -w 10% -c 5% -p
/usr/local/groundwork -w 10% -c 5% -p /tmp -w 10% -c 5% -p
/var/opt/universal
DISK OK| /=1781MB;8924;9420;0;9916 /var=885MB;7141;7538;0;7935
/opt/gw=10489MB;333060;351563;0;370067 /opt=609MB;16068;16961;0;17854
/usr/local/groundwork=3515MB;14745;15564;0;16384
/tmp=83MB;1784;1883;0;1983 /var/opt/universal=10MB;222;234;0;247

Here is the line in my nrpe.cfg:

command[check_diskthresh7]=/opt/nagios/libexec/check_disk -e -w $ARG1$
-c $ARG2$ -p $ARG3$ -w $ARG4$ -c $ARG5$ -p $ARG6$ -w $ARG7$ -c $ARG8$
-p $ARG9$ -w $ARG10$ -c $ARG11$ -p $ARG12$ -w $ARG13$ -c $ARG14$ -p
$ARG15$ -w $ARG16$ -c $ARG17$ -p $ARG18$ -w $ARG19$ -c $ARG20$ -p
$ARG21$


Here is the command run via check_nrpe:

/opt/nagios/libexec/check_nrpe -H localhost -p 5666 -n -u -t 25 -c
check_diskthresh7 -a 10% 5% / 10% 5% /opt 10% 5% /var 10% 5% /tmp 10%
5% /opt/gw 10% 5% /opt/universal 10% 5% /var/opt/universal
Unknown argument
Usage: check_disk -w limit -c limit [-W limit] [-K limit] {-p path | -x device}
[-C] [-E] [-e] [-g group ] [-k] [-l] [-M] [-m] [-R path ] [-r path ]
[-t timeout] [-u unit] [-v] [-X type]


Shouldn't the command work over NRPE, or have I just been starring at
it too long and missed something simple.

Thanks,
Kyle

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
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