Page 1 of 1
check_ssh plugin generating failures in logs
Posted: Wed Sep 10, 2014 9:49 am
by ssa_nagios
I have noticed recently that when running the check_ssh command from my Linux Nagios XI server to a remote solaris machine I get the following in the /var/adm/messages file
[ID 800047 local6.crit] fatal getpeername failed: Transport endpoint is not connected
I'm trying to determine the root cause of this issue.
The correct value is being returned to Nagios XI, but I'm concerned as to what is causing the error in the logs.
Re: check_ssh plugin generating failures in logs
Posted: Wed Sep 10, 2014 4:39 pm
by lmiltchev
Can you show us the actual check that you are running from the command line, along with the output of it?
Re: check_ssh plugin generating failures in logs
Posted: Thu Sep 11, 2014 6:24 am
by ssa_nagios
Here is the command and result from the Nagios XI server:
Code: Select all
# ./check_ssh -H ##################
SSH OK - ReflectionForSecureIT_8.0.1.57 (protocol 2.0) | time=0.131372s;;;0.000000;10.000000
On the remote host in the logs it is showing:
[ID 800047 local6.crit] fatal getpeername failed: Transport endpoint is not connected
I have performed an nslookup, both forward and reverse lookups, and they all come back with the correct results. I was told that the error "getpeername" results with the Nagios server is missing a PTR record. But as I mentioned above the lookups are coming back correct.
Re: check_ssh plugin generating failures in logs
Posted: Thu Sep 11, 2014 12:54 pm
by lmiltchev
We haven't run across this error before. You can try increasing the verbosity by running:
Probably the best route to go would be to turn on debugging on the remote box, and see if you are going to find some extra info in the logs, that can point you to the right direction.
Re: check_ssh plugin generating failures in logs
Posted: Thu Sep 18, 2014 12:58 pm
by ssa_nagios
Ok I will dig deeper into this issue. you can close this ticket for now.