I've got a Nagios server (on CentOS 5), and a monitored node (also on CentOS 5). I initially had a problem with SSH key-exchange, but that has been solved, and I'm still receiving a No Route to Host.
Nagios server: 10.0.100.130
monitored node: 10.0.100.143
Yet, I can do the following from Nagios Server:
/usr/local/nagios/libexec/check_tcp -H 10.0.100.143 -p 5666
TCP OK - 0.000 second response time on port 5666|time=0.000361s;0.000000;0.000000;0.000000;10.000000
also can do this from the Nagios Server:
ssh 10.0.100.143 /usr/local/nagios/libexec/check_procs
PROCS OK: 603 processes
I can successfully ping 10.0.100.143 from Nagios server as well.
grep for the monitored node in /var/log/messages pulls this up:
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
am a bit confused here. any help is much appreciated