Nrpe Ssl Error
Contents |
• All times are UTC - 6 hours [ DST ] Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers nrpe disable ssl or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x check_nrpe error - could not complete ssl handshake redhat Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it check_nrpe: received 0 bytes from daemon. check the remote server logs for error messages. only takes a minute: Sign up CHECK_NRPE: Error - Could not complete SSL handshake up vote 6 down vote favorite I have NRPE daemon process running under xinetd on amazon ec2 instance and nagios server on my local machine. The https://support.nagios.com/forum/viewtopic.php?f=7&t=30146 check_nrpe -H [amazon public IP] gives this error: CHECK_NRPE: Error - Could not complete SSL handshake. Both Nrpe are same versions. Both are compiled with this option: ./configure --with-ssl=/usr/bin/openssl --with-ssl-lib=/usr/lib/i386-linux-gnu/ "allowed host" entry contains my local IP address. What could be the possible reason of this error now?? linux ssl nagios nrpe nagiosxi share|improve this question edited Jul 7 at 9:55 Harikrishnan 4,35244394 asked Dec 11 '13 at 13:23 Dushyant Gupta 1871116 2 Are you sure you don't reach http://stackoverflow.com/questions/20520334/check-nrpe-error-could-not-complete-ssl-handshake your Amazon server with a public ip ? As far as Amazon server is in the Cloud i think you go through the Internet to query it. You should try to add your public ip address in "allowed host" list –user2196728 Dec 11 '13 at 13:58 I have added the public IP address of my machine in the 'allowed host' category. But the error remains. Nagios server is running on my local IP address(172.*.*.*) and not on public IP address(121.*.*.*)(sorry if saying this is doesn't make sense, I am new to all this). i.e. this works -----> 172.*.*.*/nagios but not this ---> 121.*.*.*/nagios –Dushyant Gupta Dec 12 '13 at 7:22 one more point: when I run the command "check_nrpe -H (my amazon public IP)" from my amazon system, it still shows the same error message. –Dushyant Gupta Dec 12 '13 at 7:29 add a comment| 10 Answers 10 active oldest votes up vote 1 down vote accepted To check if you have access to it at all attempt a simple telnet on the address:port, a ping or traceroute to see where it is blocking. telnet IP port ping IP traceroute -p $port IP Also check on the target server that the nrpe daemon is working properly. netstat -at | grep nrpe You also need to check the versions of OpenSSL installed on both servers, as I have seen this break checks on occasion with the
CHECK_NRPE: Error – Could not complete SSL handshake by Ramya Nuvvula · Published : September 2, 2015 | Last Updated: February 2, 2016 We have already discussed about http://www.2daygeek.com/check-nrpe-error-could-not-complete-ssl-handshake/ Nagios installation on RHEL based systems, Nagios installation on Debian based systems, http://forums.nsclient.org/t/check-nrpe-error-could-not-complete-ssl-handshake-after-updating-from-0-4-2-to-0-4-3-solved/3685 Add Remote Linux Host to Nagios Server & Add Remote Windows Host to Nagios Server. Alternatively you can install other network monitoring tools such as Zabbix, Monitorix, Cacti, Munin & Icinga2. Many of us has been experiencing the "CHECK_NRPE: Error – Could not complete SSL handshake". Why its happening could not ? It was happen when NRPE server is not allowing to access service from Nagios server. What we can do ? Don't worry nothing is there to think much, You need to add nagios server ip into nrpe configuration file to solve the issue. I'm trying to access remote host from my nagios server. I got below error message but i could not complete can able to get the output within host (locally). # /usr/local/nagios/libexec/check_nrpe -H x.x.x.x (Remote server IP) CHECK_NRPE: Error - Could not complete SSL handshake. See the below screen shot. Our remote client not talking with Nagios server. It was working fine with localhost. # /usr/local/nagios/libexec/check_nrpe -H localhost NRPE v2.13 Add the Nagios server IP into nrpe.cfg file, if you installed nrpe alone. # vi /etc/nagios/nrpe.cfg allowed_hosts=127.0.0.1,x.x.x.x On Debian, Ubuntu, Linux Mint: $ sudo service nagios-nrpe-server restart On CentOS, Fedora or RHEL: # service nagios restart Add the Nagios server IP into nrpe file, if you installed NRPE daemon as a service under xinetd. # nano /etc/xinetd.d/nrpe only_from = 127.0.0.1 x.x.x.x # Restart the xinetd service # # service xinetd restart Verifying NRPE Service Status from log file (For Debian based system /var/log/syslog & RHEL based system /var/log/messages). # tail -f /var/log/syslog Aug 11 08:46:45 2daygeek.prod nrpe[30484]: Starting up daemon Aug 11 08:46:45 2daygeek.prod nrpe[30484]: Listening for connections on port 5666 Aug 11 08:46:45 2daygeek.prod nrpe[30484]: Allowing connections from: 127.0.0.1,x.x.x.x Verifying NRPE listening port. # netstat -tpln | grep 5666 tcp 0
version, installed the new one, copied the file to the old place and overwrote the sample config, restarted the service) a server from NSCP-0.4.2.114-x64.msi to NSCP-0.4.3.143-x64.msi and receive a error message "CHECK_NRPE: Error - Could not complete SSL handshake." My Debug log said: 2015-05-21 09:40:19: debug:D:\source\nscp\service\NSClient++.cpp:330: On crash: restart: NSClientpp 2015-05-21 09:40:19: debug:D:\source\nscp\service\NSClient++.cpp:337: Submitting crash dumps to central server: http://crash.nsclient.org/submit 2015-05-21 09:40:19: debug:D:\source\nscp\service\NSClient++.cpp:342: Archiving crash dumps in: C:\Program Files\NSClient++/crash-dumps 2015-05-21 09:40:19: debug:D:\source\nscp\service\NSClient++.cpp:409: booting::loading plugins 2015-05-21 09:40:19: debug:D:\source\nscp\service\NSClient++.cpp:171: Found: CheckDisk 2015-05-21 09:40:19: debug:D:\source\nscp\service\NSClient++.cpp:171: Found: CheckEventLog 2015-05-21 09:40:19: debug:D:\source\nscp\service\NSClient++.cpp:171: Found: CheckExternalScripts 2015-05-21 09:40:19: debug:D:\source\nscp\service\NSClient++.cpp:171: Found: CheckHelpers 2015-05-21 09:40:19: debug:D:\source\nscp\service\NSClient++.cpp:171: Found: CheckNSCP 2015-05-21 09:40:19: debug:D:\source\nscp\service\NSClient++.cpp:171: Found: CheckSystem 2015-05-21 09:40:19: debug:D:\source\nscp\service\NSClient++.cpp:171: Found: CheckWMI 2015-05-21 09:40:19: debug:D:\source\nscp\service\NSClient++.cpp:171: Found: NRPEServer 2015-05-21 09:40:19: debug:D:\source\nscp\service\NSClient++.cpp:171: Found: NSClientServer 2015-05-21 09:40:19: debug:D:\source\nscp\service\NSClient++.cpp:171: Found: Scheduler 2015-05-21 09:40:19: debug:D:\source\nscp\service\NSClient++.cpp:775: C:\Program Files\NSClient++/modules\CheckDisk.dll.dll 2015-05-21 09:40:19: debug:D:\source\nscp\service\NSClient++.cpp:777: adding C:\Program Files\NSClient++/modules\CheckDisk.dll 2015-05-21 09:40:19: debug:D:\source\nscp\service\NSClient++.cpp:775: C:\Program Files\NSClient++/modules\CheckEventLog.dll.dll 2015-05-21 09:40:19: debug:D:\source\nscp\service\NSClient++.cpp:777: adding C:\Program Files\NSClient++/modules\CheckEventLog.dll 2015-05-21 09:40:19: debug:D:\source\nscp\service\NSClient++.cpp:775: C:\Program Files\NSClient++/modules\CheckExternalScripts.dll.dll 2015-05-21 09:40:19: debug:D:\source\nscp\service\NSClient++.cpp:777: adding C:\Program Files\NSClient++/modules\CheckExternalScripts.dll 2015-05-21 09:40:19: debug:D:\source\nscp\service\NSClient++.cpp:775: