No handler for command: check_nrpe_mem

[blaha]

Hi, please help me. I don't now what is wrong. I install Nagios server https://www.digitalocean.com/community/ ... untu-14-04. But I have Windows 7 64bit and 2008 r2 64bit clients and my problem is with monitoring memory and disk space. I configured clients ini file and nagios server cfg files. Thanks Jan

[Box293]

For the memory check you've defined it all in the check command check_Mem, so you need to update your service definition to use this command:

Code: Select all

define service{
        use                     generic-service
        host_name               NB-Homer
        service_description     Memory Usage
        check_command           check_Mem
}

For the disk space, there is no "check_disk" command in NSClient++. Have a look at these command examples:
http://sites.box293.com/nagios/guides/c ... disk-usage

Does this help?

[blaha]

Hi, I uninstalled NSCP-0.4.1.73-x64 client and install NSClient++-0.3.8-x64. Then I followed the instructions from https://support.nagios.com/forum/viewto ... =7&t=24911. It works, but result of Memory Usage is: "(No output on stdout) stderr: execvp(check_nrpe, ...) failed. errno is 2: No such file or directory".


****************commands.cfg ***************
# check_nrpe_memory
define command {
command_name checkMEM
command_line check_nrpe -H $HOSTADDRESS$ -p 5666 -c checkMEM -a MaxWarn=$ARG1$ MaxCrit=$ARG2$ ShowAll type=physical
}

*********************************
and

*************Homer.cfg**************

define service{
use generic-service
host_name Homer
service_description Memory Usage
check_command checkMEM!90!95
}

***************************************

and

*************nrpe.cfg file***********
#############################################################################
# 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. 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,192.160.100.103,192.168.110.44



# 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



# 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/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_users]=/usr/local/nagios/libexec/check_users -w 5 -c 10
command[check_load]=/usr/local/nagios/libexec/check_load -w 15,10,5 -c 30,25,20
command[check_hda1]=/usr/local/nagios/libexec/check_disk -w 20% -c 10% -p /dev/hda1
command[check_zombie_procs]=/usr/local/nagios/libexec/check_procs -w 5 -c 10 -s Z
command[check_total_procs]=/usr/local/nagios/libexec/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/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$
#command[memory]=/usr/local/nagios/libexec/check_Mem -w $ARG1$ -c $ARG2$

***************************************

What is wrong?

Thank you for help!
Jan

[rkennedy]

The issue is how your check_nrpe_memory command is defined -

Code: Select all

command_line check_nrpe -H $HOSTADDRESS$ -p 5666 -c checkMEM -a MaxWarn=$ARG1$ MaxCrit=$ARG2$ ShowAll type=physical

You need to add the $USER1$ macro before calling the command, otherwise you're just calling 'check_nrpe'. Change it to this -

Code: Select all

command_line $USER1$/check_nrpe -H $HOSTADDRESS$ -p 5666 -c checkMEM -a MaxWarn=$ARG1$ MaxCrit=$ARG2$ ShowAll type=physical

Then restart nagios, and try again.

[blaha]

Hi, thank you, it works!
But I have question. Why is status CRITICAL when my Homer.cfg file contains command "!90!95":

define service{
use generic-service
host_name Homer
service_description Memory Usage
check_command CheckMEM!90!95
}

Where can I change command values?
Thank you.
Jan

[Box293]

Did you restart nagios after updating the config and force an immediate check of the service?

[blaha]

Hi, I restarted nagios but I do not know how to "force an immediate check of the service".

[Box293]

Click on the service so you are on the details of the service.
Under "Service Commands" click "Re-schedule the next check of this service"
Click Commit
Click Done
When the screen refreshes you'll see the "Last Check Time", confirm that is updating.

If your service is still incorrect, what is the output of this command:

Code: Select all

ps -ef | grep nagios.cfg

[blaha]

Hi, every same problem, more information in picture.

[rkennedy]

It could be how the GUI is processing the information. It seems to be working alright on my end -

Code: Select all

/usr/local/nagios/libexec/check_nrpe -H 192.168.5.47 -c checkmem -a MaxWarn=90 MaxCrit=95 ShowAll type=physical
OK: physical: Total: 31.907GB - Used: 8.915GB (27%) - Free: 22.993GB (72%)|'physical'=8.91473GB;28.71656;30.31193;0;31.90729 'physical %'=27%;89;94;0;100

Try running the same command, over the CLI and let us know the full input / output.

Code: Select all

/usr/local/nagios/libexec/check_nrpe -H ip.of.homer -c checkmem -a MaxWarn=90 MaxCrit=95 ShowAll type=physical

(replace the /usr/local/nagios/libexec/ path as needed if your environment is different, and also the ip.of.homer part to the correct IP)

I'd like to see if this is returning the same result as teh GUI.