CHECK_NRPE: Error - Could not complete SSL handshake.

[jonas kellens]

Probably one of the most asked questions. I don't know why in my case
things aren't working.

[nagios at itcenter1 ~]$ ps aux |grep nrpe
nagios    9194  0.0  0.1   8220  1712 ?        Ss   08:39
0:00 /usr/local/nagios/bin/nrpe -c /usr/local/nagios/etc/nrpe.cfg -d
nagios   12480  0.0  0.0   3936   748 pts/0    S+   09:58   0:00 grep
nrpe

[nagios at itcenter1 ~]# vi /usr/local/nagios/etc/nrpe.cfg
allowed_hosts=127.0.0.1, public_ip_nagios

[nagios at itcenter1 ~]$ /usr/local/nagios/libexec/check_nrpe -H localhost
NRPE v2.12

[nagios at itcenter1 ~]$ netstat -at | grep 5666
tcp        0      0 *:5666                      *:*
LISTEN 

TCP port 5666 is open on firewall...

[nagios at itcenter1 ~]$ rpm -qa | grep ssl
openssl-devel-0.9.8e-12.el5
app-ssl-5.0-10
openssl-0.9.8e-12.el5

But on Nagios :

[nagios at nagios objects]$ /usr/local/nagios/libexec/check_nrpe -H
ip_public_server
CHECK_NRPE: Error - Could not complete SSL handshake.

Other hosts work fine :
[nagios at nagios objects]$ /usr/local/nagios/libexec/check_nrpe -H
ip_other_public_server
NRPE v2.12


So what am I forgetting here ?!

Thanks ! Jonas.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20091109/9853a6be/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
-------------- 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