NRPE :- (Return code of 126 is out of bounds - plugin may be missing)

LDB thesource at ldb-jab.org
Mon Sep 11 04:56:16 CEST 2006


Thomas Sluyter wrote:
> On 11 Sep, 2006, at 3:18, LDB wrote:
> 
> 
>>tom.welsh at bt.com wrote:
>>
>>>I am having a problem getting NRPE and checks to work with Nagios
>>>...
>>>"(Return code of 126 is out of bounds - plugin may be missing) "
>>>...
>>>define command{
>>>        command_name    check_nrpe
>>>        command_line    $USER1$ /check_nrpe -H $HOSTADDRESS$ -c  
>>>$ARG1$
>>>        }
>>
>>command_line    $USER1$ /check_nrpe -H $HOSTADDRESS$ -c $ARG1$ -a  
>>$ARG2$
>>
> 
> You are incorrect. To my knowledge check_nrpe has no option "-a". The  
> command definition posted by Tom is correct for his purposes.

Come again! :)

utility:/etc/nagios # /usr/lib/nagios/plugins/check_nrpe -h

NRPE Plugin for Nagios
Copyright (c) 1999-2003 Ethan Galstad (nagios at nagios.org)
Version: 2.0
Last Modified: 09-08-2003
License: GPL with exemptions (-l for more info)
SSL/TLS Available: Anonymous DH Mode, OpenSSL 0.9.6 or higher required

Usage: check_nrpe -H <host> [-p <port>] [-t <timeout>] [-c <command>] [-a 
<arglist...>]

Options:
  <host>     = The address of the host running the NRPE daemon
  [port]     = The port on which the daemon is running (default=5666)
  [timeout]  = Number of seconds before connection times out (default=10)
  [command]  = The name of the command that the remote daemon should run
  [arglist]  = Optional arguments that should be passed to the command.  Multiple
               arguments should be separated by a space.  If provided, this must be
               the last option supplied on the command line.





If he wants to use arguments to his command. he MUST add the -a flag. :)



> 
> 
>>and in order to pass arguments you must have compiled with specific  
>>"--" flags.
> 
> Pardon? What do you mean by this? In neither of Tom's examples is he  
> trying to pass parameters to check_nrpe, except for the name of the  
> script in question.
> 
> TOM:
> As odd as it may seem, we have always "solved" problems like these by  
> removing the service check definition from the server config.  
> Followed by a restart, followed by re-adding the service definition,  
> followed by yet another restart. It sounds like a crappy, windows- 
> like solution, but oddly enough it has worked for us in the past.  
> Can't say that I understand why though.
> 
> Cheers,
> 
> 
> Thomkas
> 
> 
> 
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> 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
> 
> 


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
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





More information about the Users mailing list