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

[Jonathan Wiggins]

On Nov 11, 2010, at 9:09 PM, Morris, Patrick wrote:

> On 11/11/2010 11:46 AM, Jonathan Wiggins wrote:
>> 
>>> '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.
>> 
>> 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:
>> 
> 
> Try something like "grep -R 'Home Page' /usr/local/magios/etc; grep -R 
> 'Home Page' /etc/nagios.  It's on the system somewhere, and once you 
> find it you may have your answer. Without any information about how it's 
> set up, it's impossible to say with any certainty why it's breaking.
> 

Hey Patrick, thanks for replying.

I had seen the "Home Page" in the snippet of the .cfg below --  but guess I glossed over it.  in the individual .cfg file for this server in question this exists:

define host{
	use linux-server ; Inherit default values from a template
        host_name mywebbox ; The name we're giving to this server
        alias mywebbox ; A longer name for the server
        address 10.0.100.143 ; IP address of the server
}
define service{
        use generic-service
        host_name                       mywebbox
        service_description             Home Page
        check_command                   check_http!ww2
}

the IP listed above is correct for the host. But again, no reference to an IP defined in the commands below

'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$
        }

what is weird though..

i ran this plugin check again, for grins n giggles:

/usr/local/nagios/libexec/check_tcp -H 10.0.100.143 -p 5666
TCP OK - 0.002 second response time on port 5666|time=0.001501s;0.000000;0.000000;0.000000;10.000000

but when i hop onto the monitored node, and run this:

grep nrpe /var/log/messages
Nov 17 18:41:35 mywebbox xinetd[9523]: START: nrpe pid=24837 from=10.0.100.130
Nov 17 18:41:35 mywebbox nrpe[24837]: Error: Could not complete SSL handshake. 5 
Nov 17 18:41:35 mywebbox xinetd[9523]: EXIT: nrpe status=0 pid=24837 duration=0(sec)

you can see that its failing the SSL handshake. But... I went and tested SSH key exchange b/t both hosts, and it works perfectly.  Any help is greatly appreciated.




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20101117/18f134a5/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
-------------- 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