Page 1 of 1

(No output returned from plugin) Check_ram on AIX

Posted: Tue Mar 13, 2012 3:06 am
by SECHE ENVIRONNEMENT
I have a problem with my Nagios XI 2011R1.9, which install on a CentOS 6.0 .
It can't check the ram of a server AIX 6.1, it take an error "No output returned from plugin". I think my request is bad but I don't understand where It comes.
My NRPE check are OK for all other test(User, disk_space,total_process).
We don't use SSL certificated, I show "-n" in my request.
command.cfg on server Nagios

Code: Select all

define command {
       command_name                             check_nrpe
       command_line                             $USER1$/check_nrpe -H $HOSTADDRESS$ -t 30 -c $ARG1$ -u $ARG2$
}

define command {
       command_name                             check_nrpeversion
       command_line                             $USER1$/check_nrpe -H $HOSTADDRESS$
}

define command {
       command_name                             check_nrpe_ram
       command_line                             $USER1$/check_nrpe -H $HOSTADDRESS$ -n -t 30 -c $ARG1$ -f $ARG2$
}
What doc do you need?
Thanks for your help

Re: (No output returned from plugin) Check_ram on AIX

Posted: Tue Mar 13, 2012 11:36 am
by scottwilkerson
I am going to assume you followed the following documentation
http://assets.nagios.com/downloads/nagi ... Nagios.pdf

In your service definition you would just want $ARG1$ to be check_aix_ram

there is no need to setup a separate command in XI.

Re: (No output returned from plugin) Check_ram on AIX

Posted: Wed Mar 14, 2012 3:17 am
by SECHE ENVIRONNEMENT
Hi, scottwilkerson
Sorry for late response. Thanks for the doc, but I have read and applied this doc for install and configure my AIX !
In your service definition you would just want $ARG1$ to be check_aix_ram
there is no need to setup a separate command in XI.
I just want make a test because i thought my request don't have enough $ARG$
Can I use the command NRPE : check_nrpe

Code: Select all

define command {
       command_name                             check_nrpe
       command_line                             $USER1$/check_nrpe -H $HOSTADDRESS$ -t 30 -c $ARG1$ -u $ARG2$
}
first request used check_nrpe_ram

Code: Select all

efine service {
        host_name                       seche15.sechehetres
        service_description             Current Used RAM
        use                             generic-service
        check_command                   check_nrpe_ram!check_aix_ram_f!-w 10 -c 5!!!!!!
        max_check_attempts              5
        check_interval                  5
        retry_interval                  1
        notification_interval           60
        first_notification_delay        0
        notifications_enabled           0
        contacts                        nagiosadmin
        _xiwizard                       nrpe
        register                        1
        }
Second request used check_nrpe

Code: Select all

define service {
        host_name                       seche15.sechehetres
        service_description             Ram used test
        use                             generic-service
        check_command                   check_nrpe!check_aix_ram_f!-n -f!!!!!!
        check_period                    24x7
        register                        1
        }
I hope to be clear enough

Re: (No output returned from plugin) Check_ram on AIX

Posted: Wed Mar 14, 2012 9:10 am
by SECHE ENVIRONNEMENT
I show you my config nrpe.cfg on my server AIX

Code: Select all

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=172.16.X.X



# 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=172.16.X.X

# 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



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



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

[u]command[check_aix_ram_f]=/usr/local/nagios/libexec/check_mem.pl 80 100[/u]
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
command[check_hda4]=/usr/local/nagios/libexec/check_disk -w 90 -c 95 -p /dev/hd4
command[check_hda2]=/usr/local/nagios/libexec/check_disk -w 90 -c 95 -p /dev/hd2
command[check_hda9var]=/usr/local/nagios/libexec/check_disk -w 90 -c 95 -p /dev/
hd9var
commaod[check_hda3]=/usr/local/nagios/libexec/check_disk -w 90 -c 95 -p /dev/hd3
command[check_hda1]=/usr/local/nagios/libexec/check_disk -w 90 -c 95 -p /dev/hd1
command[check_hda10opt]=/usr/local/nagios/libexec/check_disk -w 90 -c 95 -p /dev
/hd10opt
command[check_fslv00]=/usr/local/nagios/libexec/check_disk -w 90 -c 95 -p /dev/f
slv00
command[check_fslv01]=/usr/local/nagios/libexec/check_disk -w 90 -c 95 -p /dev/f
slv01
command[check_fslv02]=/usr/local/nagios/libexec/check_disk -w 90 -c 95 -p /dev/f
slv02
command[check_fslv03]=/usr/local/nagios/libexec/check_disk -w 90 -c 95 -p /dev/f
slv03
command[check_svglv]=/usr/local/nagios/libexec/check_disk -w 90 -c 95 -p /dev/sv
glv


#The following examples allow user-supplied arguments and can
#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$
the Ip of server address and allowed host are identical :o I think it's a problem

Re: (No output returned from plugin) Check_ram on AIX

Posted: Wed Mar 14, 2012 9:25 am
by scottwilkerson
SECHE ENVIRONNEMENT wrote:the Ip of server address and allowed host are identical :o I think it's a problem
The allowed host address should be the IP address of your Nagios Server. Once changed you will need to restart nrpe.
SECHE ENVIRONNEMENT wrote:I just want make a test because i thought my request don't have enough $ARG$
Can I use the command NRPE : check_nrpe

Code: Select all
define command {
command_name check_nrpe
command_line $USER1$/check_nrpe -H $HOSTADDRESS$ -t 30 -c $ARG1$ -u $ARG2$
}
You could use this, but it looks like it was changed from its defaults. Looking at your config, check_aix_ram_f doesn't accept args, and has values hard coded, so.

In your seche15.sechehetres config
set the check command to check_nrpe
set $ARG2$ to just 30 which is just a timeout (-u)