NRPE Chcek_Memory on Linix

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: NRPE Chcek_Memory on Linix

Post by rkennedy »

What are the permissions on the file, on the Pi? ls -la /usr/local/nagios/libexec/check_mem.sh

Also, when you run it over the CLI from the Nagios machine, look at /var/log/messages on the Pi and it should provide more information about the erorr.
Former Nagios Employee
kwhogster
Posts: 644
Joined: Wed Oct 14, 2015 6:51 pm
Location: Wood Ridge NJ USA
Contact:

Re: NRPE Chcek_Memory on Linix

Post by kwhogster »

root@raspberrypi:/usr/local/nagios/libexec# ls -la /usr/local/nagios/libexec/check_mem.sh
-rwxr-xr-x 1 pi pi 3420 Aug 19 18:26 /usr/local/nagios/libexec/check_mem.sh
root@raspberrypi:/usr/local/nagios/libexec#


root@raspberrypi:/usr/local/nagios/libexec# cat /var/log/messages
Aug 21 06:25:16 raspberrypi rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="3486" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
Aug 22 06:25:15 raspberrypi rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="3486" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
Aug 23 06:25:15 raspberrypi rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="3486" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
Aug 24 06:25:15 raspberrypi rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="3486" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
root@raspberrypi:/usr/local/nagios/libexec#

???????

Thanks
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: NRPE Chcek_Memory on Linix

Post by rkennedy »

Now try running -

Code: Select all

su nagios
/usr/local/nagios/libexec/check_mem.sh -w 80 -c 90
Let us know the full output.
Former Nagios Employee
kwhogster
Posts: 644
Joined: Wed Oct 14, 2015 6:51 pm
Location: Wood Ridge NJ USA
Contact:

Re: NRPE Chcek_Memory on Linix

Post by kwhogster »

pi@raspberrypi ~ $ su nagios
Password:
nagios@raspberrypi /home/pi $ /usr/local/nagios/libexec/check_mem.sh -w 80 -c 90[MEMORY] Total: 434 MB - Used: 177 MB - 40% [SWAP] Total: 99 MB - Used: 0 MB - 0% | MTOTAL=455725056;;;; MUSED=185188352;;;; MCACHE=114307072;;;; MBUFFER=132415488;;;; STOTAL=104853504;;;; SUSED=45056;;;;


I even did this

exit
pi@raspberrypi ~ $ /usr/local/nagios/libexec/check_mem.sh -w 80 -c 90
[MEMORY] Total: 434 MB - Used: 175 MB - 40% [SWAP] Total: 99 MB - Used: 0 MB - 0% | MTOTAL=455725056;;;; MUSED=183242752;;;; MCACHE=114311168;;;; MBUFFER=132419584;;;; STOTAL=104853504;;;; SUSED=45056;;;;
User avatar
lmiltchev
Former Nagios Staff
Posts: 13587
Joined: Mon May 23, 2011 12:15 pm

Re: NRPE Chcek_Memory on Linix

Post by lmiltchev »

Can you post the entire "/etc/nagios/nrpe.cfg" file?
Be sure to check out our Knowledgebase for helpful articles and solutions!
kwhogster
Posts: 644
Joined: Wed Oct 14, 2015 6:51 pm
Location: Wood Ridge NJ USA
Contact:

Re: NRPE Chcek_Memory on Linix

Post by kwhogster »

Code: Select all

#############################################################################
# Sample NRPE Config File
# Written by: Ethan Galstad (nagios@nagios.org)
#
# 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/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,10.2.8.72



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



# 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



# 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/[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_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_mem]=/usr/local/nagios/libexec/check_mem.sh -w $ARG1$ -c $ARG2$

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

User avatar
Box293
Too Basu
Posts: 5126
Joined: Sun Feb 07, 2010 10:55 pm
Location: Deniliquin, Australia
Contact:

Re: NRPE Chcek_Memory on Linix

Post by Box293 »

Code: Select all

command[check_mem]=/usr/local/nagios/libexec/check_mem.sh -w $ARG1$ -c $ARG2$
At the command line on the Nagios host you are executing this:

Code: Select all

/usr/lib/nagios/plugins/check_nrpe -H 10.2.8.7 -t 30 -c check_mem -a '-w 80% -c 90%'
This:

Code: Select all

'-w 80% -c 90%'
is being received as $ARG1$ as it is enclosed in single quotes.
NRPE is then executing this:

Code: Select all

/usr/local/nagios/libexec/check_mem.sh -w -w 80% -c 90% -c
Even if you took the single quotes away, you would then be sending 4 arguments:
$ARG1$ = -w
$ARG2$ = 80%
$ARG3$ = -c
$ARG4$ = 90%

Which would cause NRPE to execute this:

Code: Select all

/usr/local/nagios/libexec/check_mem.sh -w -w -c 80%
It ignores $ARG3$ and $ARG4$ because the command does not have them defined.

You need to execute NRPE as follows:

Code: Select all

/usr/lib/nagios/plugins/check_nrpe -H 10.2.8.7 -t 30 -c check_mem -a '80%' '90%'
I've enclosed the values in single quotes as the % signs can cause issues. This will make NRPE to execute this:

Code: Select all

/usr/local/nagios/libexec/check_mem.sh -w 90% -c 90%

It should work at this point.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
kwhogster
Posts: 644
Joined: Wed Oct 14, 2015 6:51 pm
Location: Wood Ridge NJ USA
Contact:

Re: NRPE Chcek_Memory on Linix

Post by kwhogster »

From my Nagios Server I ran this

root@tgcs017:/usr/local/nagios/etc/objects# /usr/lib/nagios/plugins/check_nrpe -H 10.2.8.7 -t 30 -c check_mem -a '80%' '90%'
NRPE: Unable to read output
root@tgcs017:/usr/local/nagios/etc/objects# /usr/lib/nagios/plugins/check_nrpe -H 10.2.8.72 -t 30 -c check_mem -a '80%' '90%'
CHECK_NRPE: Received 0 bytes from daemon. Check the remote server logs for error messages.
root@tgcs017:/usr/local/nagios/etc/objects#


10.2.8.7 is SUSE Linux

10.2.8.72 is Raspbian on my Raspberry PI



On Nagios
No handler for command: 90%

define service {
host_name RaspberryPi
service_description Check Memory Used Physical
check_command check_nrpe!check_mem! -a -w '80%' -c '90%'
check_interval 1
servicegroups MemUsage
use generic-service
}
User avatar
Box293
Too Basu
Posts: 5126
Joined: Sun Feb 07, 2010 10:55 pm
Location: Deniliquin, Australia
Contact:

Re: NRPE Chcek_Memory on Linix

Post by Box293 »

kwhogster wrote:pi@raspberrypi ~ $ su nagios
Password:
nagios@raspberrypi /home/pi $ /usr/local/nagios/libexec/check_mem.sh -w 80 -c 90[MEMORY] Total: 434 MB - Used: 177 MB - 40% [SWAP] Total: 99 MB - Used: 0 MB - 0% | MTOTAL=455725056;;;; MUSED=185188352;;;; MCACHE=114307072;;;; MBUFFER=132415488;;;; STOTAL=104853504;;;; SUSED=45056;;;;


I even did this

exit
pi@raspberrypi ~ $ /usr/local/nagios/libexec/check_mem.sh -w 80 -c 90
[MEMORY] Total: 434 MB - Used: 175 MB - 40% [SWAP] Total: 99 MB - Used: 0 MB - 0% | MTOTAL=455725056;;;; MUSED=183242752;;;; MCACHE=114311168;;;; MBUFFER=132419584;;;; STOTAL=104853504;;;; SUSED=45056;;;;
For the Pi, try it without the % signs

Code: Select all

/usr/lib/nagios/plugins/check_nrpe -H 10.2.8.7 -t 30 -c check_mem -a 80 90
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
kwhogster
Posts: 644
Joined: Wed Oct 14, 2015 6:51 pm
Location: Wood Ridge NJ USA
Contact:

Re: NRPE Chcek_Memory on Linix

Post by kwhogster »

I tried both the Pi did not work

root@tgcs017:/usr/local/nagios/etc/objects# /usr/lib/nagios/plugins/check_nrpe -H 10.2.8.7 -t 30 -c check_mem -a 80 90
[MEMORY] Total: 576 MB - Used: 154 MB - 26% [SWAP] Total: 133 MB - Used: 5 MB - 4% | MTOTAL=604598272;;;; MUSED=159191040;;;; MCACHE=95244288;;;; MBUFFER=92229632;;;; STOTAL=140505088;;;; SUSED=5779456;;;;

root@tgcs017:/usr/local/nagios/etc/objects# /usr/lib/nagios/plugins/check_nrpe -H 10.2.8.72 -t 30 -c check_mem -a 80 90
CHECK_NRPE: Received 0 bytes from daemon. Check the remote server logs for error messages.

root@tgcs017:/usr/local/nagios/etc/objects#
Locked