Nagios Support Forum

When I issue the command from the client:
[root@dbserver nrpe]# /usr/local/nagios/nrpe/libexec/check_load -w 50,55,60 -c 60,65,70
OK - load average: 0.35, 0.41, 0.37|load1=0.350;50.000;60.000;0; load5=0.410;55.000;65.000;0; load15=0.370;60.000;70.000;0;
It works.

But when I issue the command from the nagios server:
[root@ngserver lib]# /usr/local/nagios/nrpe/libexec/check_nrpe -c check_load -nH dbserver
CHECK_NRPE: Received 0 bytes from daemon. Check the remote server logs for error messages.

No joy.

There are no informative messages in the /var/log/messages file on the remote box (dbserver).

Recently, we ran yum update on the dbserver. The nrpe processes were working well prior to that.
Some of the custom nrpe checks are working well.

So it seems to me that the nrpe on ngserver is not talking to the nrpe on dbserver.

I can telnet to dbserver:5666, so I know the port is listening.

So from what it looks like you are trying to check against the Nagios server and not an external host? I do not see the host information defined anywhere in the second command.

In the command:
[root@ngserver lib]# /usr/local/nagios/nrpe/libexec/check_nrpe -c check_load -nH dbserver

ngserver (where I'm executing the command) is the Nagios server, and dbserver is the remote box.
I was under the impression that the -H flag indicated the remote host.

Or perhaps I'm not understanding your reply.

Cerephim,

You have -nH in your command line arguments.

I think you meant -H <host ip address> -n

Try:
/usr/local/nagios/nrpe/libexec/check_nrpe -H dbserver -c check_load

[root@ngserver ~]# /usr/local/nagios/nrpe/libexec/check_nrpe -H dbserver -c check_load
CHECK_NRPE: Error - Could not complete SSL handshake.
[root@ngserver ~]# /usr/local/nagios/nrpe/libexec/check_nrpe -H dbserver -c check_load -n
CHECK_NRPE: Error receiving data from daemon.

Cerephim,

Is the NRPE agent responding at all?

try without any arguments:
Regards,

-Yancy

Apparently, the nrpe executable on dbserver was compiled using a very old library. When we did the yum update, the library must have gotten overwritten with one incompatible with the npre on the box.

When I replaced npre with a more current one, things started working.

Thanks for all your help!

Cerephim,

No problem, glad you resolved the issue.

Regards,

-Yancy