lots of check_nrpe entries logged on server. How to turn off

[gprichardson]

Hi all,

Last week I migrated my old 3.5.1 Nagios server to a new server running 4.2.2, Plugins 2.1.3, and nrpe 3.0.1. Everything went pretty smoothly, however there's now a TON of entries being logged into the server's /var/log/messages (server is running CentOS 6.8).

Code: Select all

Nov 14 13:23:00 engmon check_nrpe: Remote xxx.xxx.xxx.xxx accepted a Version 2 Packet
Nov 14 13:23:00 engmon check_nrpe: Remote xxx.xxx.xxx.xxx accepted a Version 3 Packet
Nov 14 13:23:00 engmon check_nrpe: Remote xxx.xxx.xxx.xxx does not support Version 3 Packets
Nov 14 13:23:00 engmon check_nrpe: Remote xxx.xxx.xxx.xxx accepted a Version 3 Packet
Nov 14 13:23:00 engmon check_nrpe: Remote xxx.xxx.xxx.xxx accepted a Version 2 Packet
Nov 14 13:23:00 engmon check_nrpe: Remote xxx.xxx.xxx.xxx accepted a Version 3 Packet
Nov 14 13:23:00 engmon check_nrpe: Remote xxx.xxx.xxx.xxx accepted a Version 3 Packet
Nov 14 13:23:00 engmon check_nrpe: Remote xxx.xxx.xxx.xxx accepted a Version 3 Packet
Nov 14 13:23:02 engmon check_nrpe: Remote xxx.xxx.xxx.xxx accepted a Version 3 Packet
Nov 14 13:23:03 engmon check_nrpe: Remote xxx.xxx.xxx.xxx accepted a Version 3 Packet

I get why I'm seeing some messages for "Version 2 Packet" as I have some Windows servers running an older version of NsClient++ that I can't update yet. But I don't get why I'm seeing all the other check_nrpe messages (accepted a Version 3 Packet). Is there any way to either turn the messages off or at least get them to log to their own log file? Having them logged to /var/log/messages makes it really difficult to view the messages file looking for any other log entries.

Thanks for any help!

-Gary

[avandemore]

What are the contents of /usr/local/nagios/etc/nrpe.cfg?

[gprichardson]

What are the contents of /usr/local/nagios/etc/nrpe.cfg?

On my monitoring server? There isn't one. I didn't have one on my 2.5 server either. I've included an nrpe.cfg from one of the clients being monitored.

Code: Select all

#############################################################################
# Sample NRPE Config File 
# Written by: Ethan Galstad ([email protected])
# 
# Last Modified: 11-23-2007
#
# NOTES:
# This is a sample configuration file for the NRPE daemon.  It needs to be
# located on the remote host that is running the NRPE daemon, not the host
# from which the check_nrpe client is being executed.
#############################################################################


# LOG FACILITY
# The syslog facility that should be used for logging purposes.

log_facility=daemon



# PID FILE
# The name of the file in which the NRPE daemon should write it's process ID
# number.  The file is only written if the NRPE daemon is started by the root
# user and is running in standalone mode.

pid_file=/var/run/nrpe.pid



# PORT NUMBER
# Port number we should wait for connections on.
# NOTE: This must be a non-priviledged port (i.e. > 1024).
# NOTE: This option is ignored if NRPE is running under either inetd or xinetd

server_port=5666



# SERVER ADDRESS
# Address that nrpe should bind to in case there are more than one interface
# and you do not want nrpe to bind on all interfaces.
# NOTE: This option is ignored if NRPE is running under either inetd or xinetd

#server_address=127.0.0.1



# NRPE USER
# This determines the effective user that the NRPE daemon should run as.  
# You can either supply a username or a UID.
# 
# NOTE: This option is ignored if NRPE is running under either inetd or xinetd

nrpe_user=nagios



# NRPE GROUP
# This determines the effective group that the NRPE daemon should run as.  
# You can either supply a group name or a GID.
# 
# NOTE: This option is ignored if NRPE is running under either inetd or xinetd

nrpe_group=nagios



# ALLOWED HOST ADDRESSES
# This is an optional comma-delimited list of IP address or hostnames 
# that are allowed to talk to the NRPE daemon.
#
# Note: The daemon only does rudimentary checking of the client's IP
# address.  I would highly recommend adding entries in your /etc/hosts.allow
# file to allow only the specified host to connect to the port
# you are running this daemon on.
#
# NOTE: This option is ignored if NRPE is running under either inetd or xinetd

allowed_hosts=127.0.0.1
 


# 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

dont_blame_nrpe=0



# COMMAND PREFIX
# This option allows you to prefix all commands with a user-defined string.
# A space is automatically added between the specified prefix string and the
# command line from the command definition.
#
# *** THIS EXAMPLE MAY POSE A POTENTIAL SECURITY RISK, SO USE WITH CAUTION! ***
# Usage scenario: 
# Execute restricted commmands using sudo.  For this to work, you need to add
# the nagios user to your /etc/sudoers.  An example entry for alllowing 
# execution of the plugins from might be:
#
# nagios          ALL=(ALL) NOPASSWD: /usr/lib/nagios/plugins/
#
# This lets the nagios user run all commands in that directory (and only them)
# without asking for a password.  If you do this, make sure you don't give
# random users write access to that directory or its contents!

# command_prefix=/usr/bin/sudo 



# DEBUGGING OPTION
# This option determines whether or not debugging messages are logged to the
# syslog facility.
# Values: 0=debugging off, 1=debugging on

debug=0



# COMMAND TIMEOUT
# This specifies the maximum number of seconds that the NRPE daemon will
# allow plugins to finish executing before killing them off.

command_timeout=60



# CONNECTION TIMEOUT
# This specifies the maximum number of seconds that the NRPE daemon will
# wait for a connection to be established before exiting. This is sometimes
# seen where a network problem stops the SSL being established even though
# all network sessions are connected. This causes the nrpe daemons to
# accumulate, eating system resources. Do not set this too low.

connection_timeout=300



# WEEK RANDOM SEED OPTION
# This directive allows you to use SSL even if your system does not have
# a /dev/random or /dev/urandom (on purpose or because the necessary patches
# were not applied). The random number generator will be seeded from a file
# which is either a file pointed to by the environment valiable $RANDFILE
# or $HOME/.rnd. If neither exists, the pseudo random number generator will
# be initialized and a warning will be issued.
# Values: 0=only seed from /dev/[u]random, 1=also seed from weak randomness

#allow_weak_random_seed=1



# INCLUDE CONFIG FILE
# This directive allows you to include definitions from an external config file.

#include=<somefile.cfg>



# INCLUDE CONFIG DIRECTORY
# This directive allows you to include definitions from config files (with a
# .cfg extension) in one or more directories (with recursion).

#include_dir=<somedirectory>
#include_dir=<someotherdirectory>



# COMMAND DEFINITIONS
# Command definitions that this daemon will run.  Definitions
# are in the following format:
#
# command[<command_name>]=<command_line>
#
# When the daemon receives a request to return the results of <command_name>
# it will execute the command specified by the <command_line> argument.
#
# Unlike Nagios, the command line cannot contain macros - it must be
# typed exactly as it should be executed.
#
# Note: Any plugins that are used in the command lines must reside
# on the machine that this daemon is running on!  The examples below
# assume that you have plugins installed in a /usr/local/nagios/libexec
# directory.  Also note that you will have to modify the definitions below
# to match the argument format the plugins expect.  Remember, these are
# examples only!


# The following examples use hardcoded command arguments...

command[check_root]=/usr/local/nagios/libexec/check_disk -w 20% -c 10% -p /
command[check_export]=/usr/local/nagios/libexec/check_disk -w 20% -c 10% -p /export
command[check_export2]=/usr/local/nagios/libexec/check_disk -w 20% -c 10% -p /export2
command[check_backup]=/usr/local/nagios/libexec/check_disk -w 20% -c 10% -p /backup
command[check_archive]=/usr/local/nagios/libexec/check_disk -w 20% -c 10% -p /archive
command[check_mem]=/usr/local/nagios/libexec/check_mem.sh -w 10 -c 5
command[check_cpu]=/usr/local/nagios/libexec/check_cpu.sh -w 10 -c 0
command[check_load]=/usr/local/nagios/libexec/check_load -w 15,10,5 -c 30,25,20
command[check_zombie_procs]=/usr/local/nagios/libexec/check_procs -w 15 -c 20 -s Z
command[check_total_procs]=/usr/local/nagios/libexec/check_procs -w 150 -c 200 
command[check_ssh]=/usr/local/nagios/libexec/check_ssh -t 20 localhost
command[check_http]=/usr/local/nagios/libexec/check_http -H localhost
command[check_smtp]=/usr/local/nagios/libexec/check_smtp -H localhost
command[check_mailq]=/usr/local/nagios/libexec/check_mailq -H localhost -w 5 -c 10
command[check_ntp]=/usr/local/nagios/libexec/check_ntp -H tick.enterasys.com -w 0.5 -c 1



# The following examples allow user-supplied arguments and can
# only be used if the NRPE daemon was compiled with support for 
# command arguments *AND* the dont_blame_nrpe directive in this
# config file is set to '1'.  This poses a potential security risk, so
# make sure you read the SECURITY file before doing this.

#command[check_users]=/usr/local/nagios/libexec/check_users -w $ARG1$ -c $ARG2$
#command[check_load]=/usr/local/nagios/libexec/check_load -w $ARG1$ -c $ARG2$
#command[check_disk]=/usr/local/nagios/libexec/check_disk -w $ARG1$ -c $ARG2$ -p $ARG3$
#command[check_procs]=/usr/local/nagios/libexec/check_procs -w $ARG1$ -c $ARG2$ -s $ARG3$
 

Does the 3.x version of nrpe now require me to have an nrpe.cfg file on the server? I haven't read anywhere where it says that.

[avandemore]

The quick way would be to comment out that statement in the source, recompile and install the altered binary. This would include lines 171 - 172 in nrpe-3.0.1/src/check_nrpe.c.

Code: Select all

 171         if (result != -1)
 172                 syslog(LOG_NOTICE, "Remote %s accepted a Version %d Packet", rem_host, packet_ver);

Unfortunately, there is no other configuration option for this ATM. I have created FR 10119 for this issue.

[gprichardson]

Thanks for the info. I commented out those lines of code and recompiled. Worked like a charm! It's no longer flooding /var/log/messages.

Thanks again for the help!

-Gary

[dwhitfield]

Fantastic! Is it ok to close the thread?

[gprichardson]

Oh, yes, it can be closed. My apologies if this is something I could/should have done myself.

-Gary

[dwhitfield]

No need to apologize. We just like to make sure so people don't come back with additional information only to find the thread has been locked.