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

[Marc Powell]

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
------------------------------------------------------------------------------
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
_______________________________________________
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