"No Route to Host" error - ssh-key exchange issue even if plugin checks work?

[Jonathan Wiggins]

On Nov 11, 2010, at 5:26 AM, Marc Powell wrote:

> 
> On Nov 10, 2010, at 7:36 PM, Jonathan Wiggins wrote:
> 
>> I see this in the messages files:
>> 
>> Nov  9 00:00:00 nagiosbox nagios: CURRENT SERVICE STATE: monitorednode;Home Page;CRITICAL;HARD;1;No route to host 
>> Nov 10 00:00:00 nagiosbox nagios: CURRENT HOST STATE: monitorednode;UP;HARD;1;PING OK - Packet loss = 0%, RTA = 0.21 ms 
>> Nov 10 00:00:00 nagiosbox nagios: CURRENT SERVICE STATE: monitorednode;Home Page;CRITICAL;HARD;1;No route to host
>> 
>> which looks like there is no packet loss on the PING to the host, but then it shows No Route To Host
> 
> 'No Route To Host' is not a nagios error message but is coming from your operating system. Based on that and the above information, I'd say that the 'Home Page' check is being told to check a different, invalid, host name or address than the ping check.
> 
> Please post the host{}, service{} and command{} definition related to the 'Home Page' check if that's not enough to get you on the right path so we can take a look at it.
> 
> --
> Marc
> ------------------------------------------------------------------------------


Hi Marc

Thanks for answering my question.

what you say above makes total sense, except that I can't find a "home page" check anywhere on the system. I can locate the check_ping, check_http, check_host_alive.. but they dont reference anything by host name or IP for that matter:

I got these from /usr/local/nagios/etc/objects/commands.cfg

'check-host-alive' command definition
define command{
        command_name    check-host-alive
        command_line    $USER1$/check_ping -H $HOSTADDRESS$ -w 3000.0,80% -c 5000.0,100% -p 5

'check_ping' command definition
define command{
        command_name    check_ping
        command_line    $USER1$/check_ping -H $HOSTADDRESS$ -w $ARG1$ -c $ARG2$ -p 5

# 'check_http' command definition
define command{
        command_name    check_http
        command_line    $USER1$/check_http -I $HOSTADDRESS$ $ARG1$
        }

Under /etc/rc.d/init.d/nagios I can see that I've got the paths right:

prefix="/usr/local/nagios"
exec_prefix="/usr/local/nagios"
exec="/usr/local/nagios/bin/nagios"
config="/usr/local/nagios/etc/nagios.cfg"

It probably doesn't help my understanding/troubleshooting that the previous admin rolled up 2 different sets of binaries, and wound up different paths; e.g. /usr/local/nagios vs /etc/nagios/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20101111/0eff9433/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
-------------- 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