check_nrpe shows the wrong IPv6 address in error messages
Posted: Mon Sep 25, 2017 10:03 pm
Hello all,
I am setting up check_nrpe to query a bunch of servers that all have IPv6 addresses. All machines have NRPE 3.2.1 (and the server has that same version of check_nrpe.
When I run a test:
I get the following error:
The reason for the connection failure is very simple - that IPv6 address is not the address of the machine I am trying to connect to.
All other programs on the Nagios host correctly resolve the IP of the other server. For example, dig AAAA myhost.example.com, host myhost.example.com, ping6 myhost.example.com, and others all get the correct address. Only check_nrpe gets it wrong.
The interesting thing is that the first half of the address is correct. Only the last half is totally messed up. (My boss does not want me to share the IP addresses publicly, but I can PM them if you want.)
If it makes a difference, the Nagios host is on Linode and the NRPE machines are all on AWS EC2.
I am setting up check_nrpe to query a bunch of servers that all have IPv6 addresses. All machines have NRPE 3.2.1 (and the server has that same version of check_nrpe.
When I run a test:
Code: Select all
/usr/local/nagios/libexec/check_nrpe -H myhost.example.com -p 5666 -c check_reboot_requiredCode: Select all
CHECK_NRPE: Error - Could not connect to SOME_IPv6_ADDRESS: Connection reset by peerAll other programs on the Nagios host correctly resolve the IP of the other server. For example, dig AAAA myhost.example.com, host myhost.example.com, ping6 myhost.example.com, and others all get the correct address. Only check_nrpe gets it wrong.
The interesting thing is that the first half of the address is correct. Only the last half is totally messed up. (My boss does not want me to share the IP addresses publicly, but I can PM them if you want.)
If it makes a difference, the Nagios host is on Linode and the NRPE machines are all on AWS EC2.
