CHECK_NRPE: Error - Could not complete SSL handshake

[Figueroa, Daniel]

I'm unable to execute as a test from my SUSE 9.2 Nagios server -

 [root at Z3 root]# /usr/local/nagios/libexec/check_nrpe -H HPUX_srvr -c check_load

>>I'm receiving the following error and can use your help in understanding why?

CHECK_NRPE: Error - Could not complete SSL handshake

I was told I have to be up-to-date on plugins, which I am -

Note: The HPUX_srvr is a HP-UX 10.20 running nrpe-1.8-B.10.20.depot.  The Nagios server is
using the latest "Nagios Plugins HP-UX" from NagiosExchange.org, such as check_load.

On the HPUX_srvr box, I've configured the inetd.conf file to launch - 

nrpe   stream tcp nowait rose /usr/sbin/tcpd /usr/local/nagios/bin/nrpe -c /usr/ local/nagios/bin/nrpe.cfg

Doing a netstat on my HPUX box, I can see the service is listening, per /etc/service configuration.

tcp        0      0  *.nrpe                 *.*                    LISTEN

# The following are my entries in the nrpe.cfg file::  
command[check_users]=@libexecdir@/check_users -w 5 -c 10
command[check_load]=@libexecdir@/check_load -w 15,10,5 -c 30,25,20
command[check_disk1]=@libexecdir@/check_disk -w 20 -c 10 -p /dev/hda1
command[check_disk2]=@libexecdir@/check_disk -w 20 -c 10 -p /dev/hdb1
command[check_zombie_procs]=@libexecdir@/check_procs -w 5 -c 10 -s Z
command[check_total_procs]=@libexecdir@/check_procs -w 150 -c 200

>>How does @libexecdir@ know where my check_users lives?

Thanks in advance,
Daniel



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
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