check_nrpe help with multipple argument

[shadih rahman]

I am trying to execute a check_nrpe with multiple argument and it is not
working.  I have the following definition in my nrpe.cfg

command[check_users_x64]=/usr/lib64/nagios/plugins/check_users -w 5 -c 10
command[check_load_x64]=/usr/lib64/nagios/plugins/check_load -w 15,10,5 -c
30,25,20
command[check_hda1_x64]=/usr/lib64/nagios/plugins/check_disk -w 20% -c 10%
-p /dev/hda1
command[check_zombie_procs_x64]=/usr/lib64/nagios/plugins/check_procs -w 5
-c 10 -s Z
command[check_total_procs_x64]=/usr/lib64/nagios/plugins/check_procs -w 150
-c 200
command[check_disk_x64]=/usr/lib64/nagios/plugins/check_disk -w 15% -c 10%
-p $ARG1$
command[check_disk_excluding_x64]=/usr/lib64/nagios/plugins/check_disk -w
15% -c 10% -p $ARG1$ -x $ARG2$
command[check_process_x64]=/usr/lib64/nagios/plugins/check_proc -w $ARG1$ -c
$ARG2$ -C $ARG3$
command[restart-remote_x64]=/usr/lib64/nagios/eventhandlers/remote-restart.sh
$ARG1$ $ARG2$ $ARG3$ $ARG4$


when I try to execute the following from command line I get an error.

-bash-3.2$ ./check_nrpe -H localhost -c check_process_x64 -a 10 10 nagios
NRPE: Unable to read output


however single argument works fine.

-bash-3.2$ ./check_nrpe -H localhost -c check_disk_x64 -a /var
DISK OK - free space: /var 6674 MB (72% inode=99%);|
/var=2513MB;8234;8719;0;9688

Please advise on this.  Thanks


-- 
Cordially,
Shadhin Rahman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20090402/d37c2835/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
-------------- next part --------------
_______________________________________________
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