ping hanging.

[Arno Lehmann]

Hello,

On 1/7/2006 10:32 PM, Marc Powell wrote:
> 
>>-----Original Message-----
>>From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
>>admin at lists.sourceforge.net] On Behalf Of Hammond, Robin-David%KB3IEN
>>Sent: Friday, January 06, 2006 10:02 PM
>>To: nagios-users at lists.sourceforge.net
>>Subject: [Nagios-users] ping hanging.
>>
...
>>
>>/Warning: Attempting to execute the command "/check_ping -H 4400::34
> 
> -w
> 
>>3000.0,80% -c 5000.0,100% -p 1 -t 10 -6" resulted in a return code of
> 
> 127.
> 
>>Make sure the script or binary you are trying to execute actually
>>exists...
>>
>>over and over.
>>
>>this is particularly confusiong as i never reran configure nor did I
> 
> ever
> 
>>uninstall the /check_ping programme it is still in place and
> 
> executable.

Hmm. I *really* hope you never installed the plugins in your root directory.

>>Any ideas?
> 
> 
> 
> Return code 127 means that the plugin was not found in the location
> specified in the command definition. Nagios is apparently trying to
> execute /check_ping and not /path/to/check_ping (usually
> /usr/local/nagios/libexec/check_ping). There are four primary
> possibilities --
> 	1) your command definition does not utilize the $USER1$ macro in
> the command_line i.e. 'command_line $USER1$/check_ping -H ...'
> 	2) you have manually specified the incorrect path in the
> command_line i.e. 'command line  /check_ping -H ...'
> 	3) $USER1$ is not set to the correct plugins path in
> resource.cfg
> 	4) you have not included resource.cfg as a resource_file in
> nagios.cfg

One other possibility I encountered:
When the resource.cfg file is not readable by nagios, the above happens 
after nagios reloaded its configuration. The initial configuration file 
access happens before nagios drops its rights (when started as root), 
but afterwards, during operation, it's simply no longer permitted to 
read the resource.cfg... he easy work-around is a chown on the file 
followed by another configuration reload.

Arno

> --
> Marc
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
> _______________________________________________
> 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
> 

-- 
IT-Service Lehmann                    al at its-lehmann.de
Arno Lehmann                  http://www.its-lehmann.de


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
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