Page 2 of 5
Re: Could not complete SSL handshake (check_nrpe is fine)
Posted: Fri Mar 21, 2014 3:12 pm
by hazmat
In nrpe.cfg I have, for example:
Code: Select all
command[check_disk]=/usr/local/nagios/libexec/check_disk -w $ARG1$ -c $ARG2$ -p $ARG3$
In the cfg on the nagios server I have:
Code: Select all
check_command check_nrpe!check_disk!20%!10%!/var
Is there any problem here?
Re: Could not complete SSL handshake (check_nrpe is fine)
Posted: Mon Mar 24, 2014 1:41 pm
by lmiltchev
You need to pass the "-a" flag with nrpe to pass the arguments. The way you have it set up it's not going to work. I would suggest:
On the client:
Code: Select all
command[check_disk]=/usr/local/nagios/libexec/check_disk $ARG1$
In Nagios:
Code: Select all
check_command check_nrpe!check_disk!-a '-w 20% -c 10% -p /var'
Re: Could not complete SSL handshake (check_nrpe is fine)
Posted: Mon Mar 24, 2014 2:10 pm
by hazmat
Thanks, but that made no difference in nrpe reporting "Error: Could not complete SSL handshake", but changed the Status Information in the Nagios web console from "CHECK_NRPE: Error receiving data from daemon." to "(No output returned from plugin)".
Re: Could not complete SSL handshake (check_nrpe is fine)
Posted: Mon Mar 24, 2014 4:44 pm
by lmiltchev
Did you restart xinetd after modifying the nrpe.cfg on the client?
Re: Could not complete SSL handshake (check_nrpe is fine)
Posted: Mon Mar 24, 2014 4:45 pm
by abrist
hazmat wrote:"(No output returned from plugin)".
This error is usually returned by the agent, and can imply a missing plugin, a bad path, or bad permissions. Can you show us a listing of the following directory on the remote host:
Additionally, you will need to enable:
In the remote host's nrpe.cfg in order to pass arguments.
If you can check the version number of nrpe remotely, then the networking side of things is currently working. You most likely have issues with the command definitions, or with the nrpe.cfg on the remote host.
In fact, I you get a chance, post your remote host's nrpe.cfg as an attachment or in code wraps and we will take a look.
Re: Could not complete SSL handshake (check_nrpe is fine)
Posted: Tue Mar 25, 2014 8:27 am
by hazmat
Thanks. xinetd was restarted. Everything in /usr/local/nagios/libexec is 755, nagios:nagios.
nrpe.cfg is attached. The only two commands not commented out at the bottom are two I was playing with.
Thanks again.
Re: Could not complete SSL handshake (check_nrpe is fine)
Posted: Tue Mar 25, 2014 4:32 pm
by abrist
Have you added the sudoer line? I ask because you have declared the following in your nrpe.cfg:
If you do not need escalated privileges, I suggest you comment out the line and restart nrpe/xinetd.
Re: Could not complete SSL handshake (check_nrpe is fine)
Posted: Wed Mar 26, 2014 8:07 am
by hazmat
I did add sudo privileges to user nagios, just in case, but also just commented that out and restarted xinetd. No change, though.
Re: Could not complete SSL handshake (check_nrpe is fine)
Posted: Wed Mar 26, 2014 1:04 pm
by abrist
Alright, lets walk through all of this one more time.
From the remote host, in the libexec directory:
Code: Select all
./check_nrpe -H localhost
./check_disk -w 20% -c 10% -p /var
From the nagios server:
Code: Select all
./check_nrpe -H <remote host ip>
./check_nrpe -H <remote host ip> -c check_disk
./check_nrpe -H <remote host ip> -c check_disk -a '-w 20% -c 10% -p /var'
Re: Could not complete SSL handshake (check_nrpe is fine)
Posted: Wed Mar 26, 2014 1:22 pm
by hazmat
Thanks so much for staying on this.
On remote host:
$ ./check_nrpe -H localhost
NRPE v2.12
./check_disk -w 20% -c 10% -p /var
DISK OK - free space: /var 5143 MB (68% inode=99%);| /var=2382MB;6348;7141;0;7935
On nagios server:
# ./check_nrpe -H <IP>
NRPE v2.12
# ./check_nrpe -H <IP> -c check_disk
check_disk: Could not parse arguments
Usage: check_disk -w limit -c limit [-W limit] [-K limit] {-p path | -x device}
[-C] [-E] [-e] [-g group ] [-k] [-l] [-M] [-m] [-R path ] [-r path ]
[-t timeout] [-u unit] [-v] [-X type]
# ./check_nrpe -H <P> -c check_disk -a '-w 20% -c 10% -p /var'
CHECK_NRPE: Received 0 bytes from daemon. Check the remote server logs for error messages.
From the remote server log:
Mar 26 14:16:32 xinetd[12968]: START: nrpe pid=19778 from=<IP>
Mar 26 14:16:32 nrpe[19778]: INFO: SSL/TLS initialized. All network traffic will be encrypted.
Mar 26 14:16:32 nrpe[19778]: Error: Request contained command arguments!
Mar 26 14:16:32 nrpe[19778]: Client request was invalid, bailing out...
Mar 26 14:16:32 xinetd[12968]: EXIT: nrpe status=0 pid=19778 duration=0(sec)
Does this mean that the nrpe I have wasn't built to allow arguments? As I said, this is a production server where I cannot have a compiler on unfortunately.