We are using Nagios 3.0.5 and one of our services monitors a
particular job on a particular server:
define service{
...
check_command check_nrpe!check_myown1_job
}
and in the nrpe.cfg file we define that command:
command[check_myown1_job]=/usr/lib/nagios/plugins/check_procs -c 1:1
-a /home/myuser01/src/server/scripts/sync_api/
make_async_xmlrequest_libraries.py
We just upgraded NRPE and this check started failing - it reported 0
processes. However, the process was running and the command works
fine when run locally on the target machine.
After some trial and error, I discovered that the arguments to the
target process seem to be cut off.
This works:
command[check_myown1_job]=/usr/lib/nagios/plugins/check_procs -c 1:1
-a /home/myuser01/src/server/scripts/sync_api/make_as
but this fails:
command[check_myown1_job]=/usr/lib/nagios/plugins/check_procs -c 1:1
-a /home/myuser01/src/server/scripts/sync_api/make_asy
The commands are identical except that the second one has one
additional character ('y'). Any command longer than the first one
fails.
This also works:
command[check_myown1_job]=/usr/lib/nagios/plugins/check_procs -c 1:1
-a make_as
but this also fails:
command[check_myown1_job]=/usr/lib/nagios/plugins/check_procs -c 1:1
-a make_asy
So, it does not seem to be a problem in the argument string passed
in, but rather in the arguments read from the remote machine.
Is there some setting that controls size of the argument on the
target machine that will allow me to specify the entire argument?
Bob Swerdlow
Chief Engineer
Emergent Discovery
rswerd...@emergentdiscovery.com
207-774-3100
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Nagios-users mailing list
Nagios-users@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
