Page 2 of 3

Re: Debian not work with NRPE $ARG$

Posted: Tue Mar 26, 2019 8:34 am
by liberodark
Yes have found :

Code: Select all

grep "Check CPU" -R /etc/nagios/objects
/etc/nagios/objects/hosts/Debian_9.cfg:	service_description	Check CPU
/etc/nagios/objects/hosts/Debian_9.cfg:	display_name	Check CPU

Code: Select all

cat /etc/nagios/objects/hosts/Debian_9.cfg
define host {
	use	Linux_NRPE
	check_command	check-host-alive
	host_name	Debian 9
	alias	Debian 9
	display_name	Debian 9
	address	10.10.99.39
}

define service {
	host_name	Debian 9
	use	GENERIC_GRAPH
	check_command	check_memory_nrpe!70%!90%
	service_description	Check Memory
	display_name	Check Memory
}

define service {
	host_name	Debian 9
	use	GENERIC_GRAPH
	check_command	check_disk_nrpe!-w 20% -c 10% -p / -m
	service_description	Check Disk
	display_name	Check Disk
}

define service {
	host_name	Debian 9
	use	GENERIC_SERVICE
	check_command	check_service_nrpe
	service_description	Check Service
	display_name	Check Service
}

define service {
	host_name	Debian 9
	use	GENERIC_GRAPH
	check_command	check_cpu_nrpe!70!90
	service_description	Check CPU
	display_name	Check CPU
}

define service {
	host_name	Debian 9
	use	GENERIC_GRAPH
	check_command	check-host-alive
	service_description	Check Host
	display_name	Check Host
}

define service {
	host_name	Debian 9
	use	GENERIC_GRAPH
	check_command	check_swap_nrpe!20%!10%
	service_description	Check Swap
	display_name	Check Swap
}

Re: Debian not work with NRPE $ARG$

Posted: Tue Mar 26, 2019 8:44 am
by scottwilkerson
This all looks correct, where are you seeing?

Code: Select all

NRPE: Command 'cpu!70!90' not defined

Re: Debian not work with NRPE $ARG$

Posted: Tue Mar 26, 2019 8:48 am
by liberodark
Here :

https://i.imgur.com/wAPXLmK.jpg

Is only for all Debian's but CentOS work !

Re: Debian not work with NRPE $ARG$

Posted: Tue Mar 26, 2019 9:08 am
by scottwilkerson
Can you share your nrpe.cfg from the Debian server?

Re: Debian not work with NRPE $ARG$

Posted: Tue Mar 26, 2019 9:19 am
by liberodark
Yes not problem

This a nrpe.cfg on all debian :

Code: Select all

cat nrpe.cfg
#############################################################################
# Sample NRPE Config File
# Written by: Ethan Galstad ([email protected])
#
# Last Modified: 2016-05-10
#
# 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



# 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



# 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/nagios/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



# LISTEN QUEUE SIZE
# Listen queue size (backlog) for serving incoming connections.
# You may want to increase this value under high load.

#listen_queue_size=5



# 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. Network addresses with a bit mask
# (i.e. 192.168.1.0/24) are also supported. Hostname wildcards are not currently
# supported.
#
# 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,10.10.99.15



# 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=1



# BASH COMMAND SUBTITUTION
# This option determines whether or not the NRPE daemon will allow clients
# to specify arguments that contain bash command substitutions of the form
# $(...).  This option only works if the daemon was configured with both
# the --enable-command-args and --enable-bash-command-substitution configure
# script options.
#
# *** ENABLING THIS OPTION IS A HIGH SECURITY RISK! ***
# Read the SECURITY file for information on some of the security implications
# of enabling this variable.
#
# Values: 0=do not allow bash command substitutions,
#         1=allow bash command substitutions

allow_bash_command_substitution=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



# 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



# WEAK 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



# SSL/TLS OPTIONS
# These directives allow you to specify how to use SSL/TLS.

# SSL VERSION
# This can be any of: SSLv2 (only use SSLv2), SSLv2+ (use any version),
#        SSLv3 (only use SSLv3), SSLv3+ (use SSLv3 or above), TLSv1 (only use
#        TLSv1), TLSv1+ (use TLSv1 or above), TLSv1.1 (only use TLSv1.1),
#        TLSv1.1+ (use TLSv1.1 or above), TLSv1.2 (only use TLSv1.2),
#        TLSv1.2+ (use TLSv1.2 or above)
# If an "or above" version is used, the best will be negotiated. So if both
# ends are able to do TLSv1.2 and use specify SSLv2, you will get TLSv1.2.

#ssl_version=SSLv2+

# SSL USE ADH
# This is for backward compatibility and is DEPRECATED. Set to 1 to enable
# ADH or 2 to require ADH. 1 is currently the default but will be changed
# in a later version.

#ssl_use_adh=1

# SSL CIPHER LIST
# This lists which ciphers can be used. For backward compatibility, this
# defaults to 'ssl_cipher_list=ALL:!MD5:@STRENGTH' in this version but
# will be changed to something like the example below in a later version of NRPE.

#ssl_cipher_list=ALL:!MD5:@STRENGTH
#ssl_cipher_list=ALL:!aNULL:!eNULL:!SSLv2:!LOW:!EXP:!RC4:!MD5:@STRENGTH

# SSL Certificate and Private Key Files

#ssl_cacert_file=/etc/ssl/servercerts/ca-cert.pem
#ssl_cert_file=/etc/ssl/servercerts/nagios-cert.pem
#ssl_privatekey_file=/etc/ssl/servercerts/nagios-key.pem

# SSL USE CLIENT CERTS
# This options determines client certificate usage.
# Values: 0 = Don't ask for or require client certificates (default)
#         1 = Ask for client certificates
#         2 = Require client certificates

#ssl_client_certs=0

# SSL LOGGING
# This option determines which SSL messages are send to syslog. OR values
# together to specify multiple options.

# Values: 0x00 (0)  = No additional logging (default)
#         0x01 (1)  = Log startup SSL/TLS parameters
#         0x02 (2)  = Log remote IP address
#         0x04 (4)  = Log SSL/TLS version of connections
#         0x08 (8)  = Log which cipher is being used for the connection
#         0x10 (16) = Log if client has a certificate
#         0x20 (32) = Log details of client's certificate if it has one
#         -1 or 0xff or 0x2f = All of the above

#ssl_logging=0x00



# 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_users]=/usr/lib/nagios/plugins/check_users -w 5 -c 10
command[check_load]=/usr/lib/nagios/plugins/check_load -w 15,10,5 -c 30,25,20
command[check_hda1]=/usr/lib/nagios/plugins/check_disk -w 20% -c 10% -p /dev/hda1
command[check_zombie_procs]=/usr/lib/nagios/plugins/check_procs -w 5 -c 10 -s Z
command[check_total_procs]=/usr/lib/nagios/plugins/check_procs -w 150 -c 200


# 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/lib/nagios/plugins/check_users -w $ARG1$ -c $ARG2$
#command[check_load]=/usr/lib/nagios/plugins/check_load -w $ARG1$ -c $ARG2$
#command[check_disk]=/usr/lib/nagios/plugins/check_disk -w $ARG1$ -c $ARG2$ -p $ARG3$
#command[check_procs]=/usr/lib/nagios/plugins/check_procs -w $ARG1$ -c $ARG2$ -s $ARG3$

# local configuration:
# if you'd prefer, you can instead place directives here

include=/etc/nagios/nrpe_local.cfg

# you can place your config snipplets into nrpe.d/
# only snipplets ending in .cfg will get included

include_dir=/etc/nagios/nrpe.d/

Re: Debian not work with NRPE $ARG$

Posted: Tue Mar 26, 2019 9:42 am
by scottwilkerson
You are also including this file can you attach it as well

Code: Select all

/etc/nagios/nrpe_local.cfg
also, when you compiled this did you add --enable-command-args to the ./configure command?

e.g.

Code: Select all

./configure --enable-command-args
This would be required

Re: Debian not work with NRPE $ARG$

Posted: Tue Mar 26, 2019 9:50 am
by liberodark
Ok

Code: Select all

 cat     /etc/nagios/nrpe_local.cfg
######################################
# Do any local nrpe configuration here
######################################
Yes have use this argument but now is just a "apt install -y nagios-nrpe-server nagios-plugins-basic ufw bc"

And on debian the package is compiled with "--enable-command-args"


On this screen see Centos 7 + Debian 9
https://i.imgur.com/moYzBJZ.png

Re: Debian not work with NRPE $ARG$

Posted: Tue Mar 26, 2019 10:06 am
by scottwilkerson
The pre-build deb packages do not have them enabled

Here is a writeup on how to enable them with the packages
https://www.claudiokuenzler.com/blog/71 ... patibility

Otherwise you would need to compile from source
https://support.nagios.com/kb/article.php?id=515

Re: Debian not work with NRPE $ARG$

Posted: Tue Mar 26, 2019 10:09 am
by liberodark
but have compiled and is not work but is strange for what on centos is enable ?

Re: Debian not work with NRPE $ARG$

Posted: Tue Mar 26, 2019 10:12 am
by scottwilkerson
liberodark wrote:but have compiled and is not work but is strange for what on centos is enable ?
They are packaged by different organizations that have different parameters of what is used when compiling the packages.

We do not create the debian or CentOS packaged in the repositories, just the source code.

Make sure you have removed the package before trying to compile from source or you may still be using the package from the repository