Nagios Support Forum

I am using the Nagios Core 4.4.3

I have recently added some Linux servers to the monitoring.
They all are giving the Same Error:

"Check_NRPE: Error - Could not connect to xxx.xxx.xxx.xxx: Connection reset by peer"

I have checked the server nrpe.cfg file and Nagios Server IP is allowed there.

Also Server Firewall is allowing the connection by the Nagios Server as well.

Kindly suggest.

Can you post your check command, and the nrpe.cfg file from one of the servers?

Please find here with the command:

define command {

command_name check_nrpe
command_line $USER1$/check_nrpe -H $HOSTADDRESS$ -c $ARG1$
}

and nrpe.cfg is attached herewith. before uploading the file I have changed the Nagios Server IP to xxx.xxx.xxx.xxx

Kindly suggest

That all looks correct. In your nrpe.cfg file, you should set debug=0 to debug=1, try to connect, and then see if there are any errors in the log file. Try that and let me know what happens.

Please find attached the log file.
i have replaced the nagios server ip with the xxx.xxx.xxx.xxx

Kindly look into it.

It looks like there's a ton of SSL handshake errors. Can you try adding --no-ssl to your check command, and see if it connects?

I don't want to change the command, because the same command is working for the other servers.

So kindly suggest, is it really required to change the command and i don't want to break the monitoring for other servers.

If the current command is working for a number of other servers, then you can put the -n switch in the $ARG1$ for the servers where it is not working. Or create a copy of the existing command, and add the -n to the copy, then apply the copy to each of the servers that require the -n. Would either of those options work for you?

Does this mean that there is something in the Server which is giving the SSL Error?
if yes, What could be the reason?

Because we already have the servers working without any error.

Also i have checked by changing the Command for One Service Check Disk All, Now the Error is Changed:

CHECK_NRPE: Receive header underflow - only -1 bytes received (4 expected).

Kindly Suggest