check_nrpe version 2.15

[brandon]

I have a problem with check_nrpe 2.15
I'm trying ./check_nrpe -H 127.0.0.1 -c check_procs.sh and it's OK, because returns
PROCS OK: 117 processes | procs=117;;;0; | procs=117

however, if you want to add warnings and criticals:
./check_nrpe -H 127.0.0.1 -c check_procs.sh -a '-w 10 -c 50 -C apache2' then returns:

CHECK_NRPE: Received 0 bytes from daemon. Check the remote server logs for error messages.

and my question, where is the problem?
these problems do not exist in check_nrpe 2.12
In version 2.12 everything works beautifully

after updating something has been changed?

[tgriep]

Could you post the NRPE configuration file that defines the check_procs.sh command? It is usually found here.

Code: Select all

/usr/local/nagios/etc/nrpe/common.cfg

Also, could you run the following and post the output?

Code: Select all

ls -l /usr/local/nagios/libexec/check_proc*

[brandon]

I don't understand, because my check_nrpe connects to the other servers in versions 2.12 and everything works and problem is version 2.15
So what the definition of command?
Are there any differences in commands 2.12 and 2.15?

[tgriep]

I wanted to check and see if the settings for those commands didn't get corrupted or changed. Can you post the information?

What type of system is the NRPE daemon running on?

This is from the trouble shooting section of the NRPE install guide with the error message that you are receiving.

The check_nrpe plugin returns "CHECK_NRPE: Received 0 bytes from daemon. Check the remote server
logs for an error message."
First thing you should do is check the remote server logs for an error message. This error could be
due to the following problem:
– The check_nrpe plugin was unable to complete an SSL handshake with the NRPE daemon. An error
message in the logs should indicate whether or not this was the case. Check the versions of OpenSSL that
are installed on the monitoring host and remote host. If you're running a commercial version of SSL on the
remote host, there might be some compatibility problems.

Can you check the log files on the remote system for any clues?

[brandon]

I have servers with version 2.12 and everything is OK
I installed 2.15 and above problems
I installed a new machine with Debian NRPE squezze version 2.12, I made the same steps when installing nrpe 2.12 as at 2.15, and problems are only 2.15, NRPE 2.12 runs
libraries, plug-ins are installed on 2.12 and 2.15
The logs on the remote system:
nrpe[6502]: Error: Request contained command arguments!
nrpe[6502]: Client request was invalid, bailing out...
nrpe[2559]: There's already an NRPE server running (PID 2523). Bailing out...

[Box293]

Have you gone through this troubleshooting guide?

https://assets.nagios.com/downloads/nag ... utions.pdf

[brandon]

yes I do, because the problem is is with warnings and critical
Iam doing: ./check_nrpe -H 192.168.0.10 -c check_procs.sh and it's OK, then returns: PROCS OK: 117 processes
Iam doing ./check_nrpe -H 192.168.0.10 -c check_procs.sh -a '-w 10 -c 50 -C apache2' then returns: CHECK_NRPE: Received 0 bytes from daemon. Check the remote server logs for error messages.
so communication with a remote system

On remote system configuration nrpe.cfg:
command[check_procs.sh]=/usr/local/nagios/libexec/check_procs.sh $ARG1$

so where is the problem?

[jolson]

Based on what I'm seeing here, your problem could lie in the 'dont_blame_nrpe' directive:

# COMMAND ARGUMENT PROCESSING
# This option determines whether or not the NRPE daemon will allow clients
# to specify arguments to commands that are executed. This option only works
# if the daemon was configured with the --enable-command-args configure script
# option.
#
# *** ENABLING THIS OPTION IS A SECURITY RISK! ***
# Read the SECURITY file for information on some of the security implications
# of enabling this variable.
#
# Values: 0=do not allow arguments, 1=allow command arguments

You might try changing 'dont_blame_nrpe' to '1' in your nrpe.cfg file and re-testing.

Code: Select all

vi /usr/local/nagios/etc/nrpe.cfg

[brandon]

I set to 1 , becasue I know nagios, but version 2.12

[lmiltchev]

Did you restart nrpe daemon (or xinetd) after setting up "dont_blame_nrpe=1"?

Can you pass any arguments?

Code: Select all

./check_nrpe -H 192.168.0.10 -c check_procs.sh -a '-w 10 -c 50'
./check_nrpe -H 192.168.0.10 -c check_users -a '-w 2 -c 5'