Add a plugin AIX

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
migwi3@gmail.com
Posts: 8
Joined: Tue Aug 02, 2016 2:11 am

Add a plugin AIX

Post by migwi3@gmail.com »

Hello team,
I came accross a pluggin called check_AIX_processes.sh which i really want to use to monitor apecific aix processes. When i run it on command line, it works fine

e.g
bash-4.3# ./check_AIX_processes.sh -n MapperInMemoryHINASync_03-MapperInMemoryHINASync_03.tra
OK - System Process MapperInMemoryHINASync_03-MapperInMemoryHINASync_03.tra |processes= 1;;;00;
bash-4.3#

However, when i add it to the nagiosxi server using the link (https://assets.nagios.com/downloads/nag ... ios-XI.pdf) , i get the response that

/usr/local/nagios/libexec/check_nrpe -H 172.28.221.55 -t 30 -c check_AIX_processes.sh -n sendmail
CHECK_NRPE: Received 0 bytes from daemon. Check the remote server logs for error messages.

I do not know where the nagios logs go in aix server, but has encountered this?

I have made entries in nrpe.cfg on bothe servers as below and have enabled blame_nrpe=1

command[check_AIX_processes.sh]=/opt/nagios/libexec/check_AIX_processes.sh -n $ARG1$

Have i entered correctly? Your kind assistance will be highly appreciated.
regards
User avatar
tgriep
Madmin
Posts: 9177
Joined: Thu Oct 30, 2014 9:02 am

Re: Add a plugin AIX

Post by tgriep »

One possible cause of this is a setting in the nrpe.cfg file that has to be changes to allow the NRPE agent to use Arguments.
Edit the nrpe.cfg on your AIX server and change the following option to the example below.

Code: Select all

dont_blame_nrpe=1
Save the file and restart the NRPE agent for the settings to take effect.

This will enable the agent to receive arguments from the Nagios server.
If it still fails, login to the AIX server and run the following and post the output.

Code: Select all

su nagios
/opt/nagios/libexec/check_AIX_processes.sh -n sendmail
Also, upload the copy of the nrpe.cfg file from the AIX server.
Be sure to check out our Knowledgebase for helpful articles and solutions!
migwi3@gmail.com
Posts: 8
Joined: Tue Aug 02, 2016 2:11 am

Re: Add a plugin AIX

Post by migwi3@gmail.com »

Hello Thanks for responding ...I have already set it to 1 but i still get the error NRPE: Unable to read output

Below is my nrpe.cfg on the AIX server

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/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=172.29.227.136
 


# 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=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=/etc/nagios/nrpe/common.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]=/opt/nagios/libexec/check_users -w 5 -c 10
#command[check_load]=/opt/nagios/libexec/check_load -w 15,10,5 -c 30,25,20
#command[check_hda1]=/opt/nagios/libexec/check_disk -w 20% -c 10% -p /dev/hda1
#command[check_zombie_procs]=/opt/nagios/libexec/check_procs -w 5 -c 10 -s Z
#command[check_total_procs]=/opt/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]=/opt/nagios/libexec/check_users -w $ARG1$ -c $ARG2$
#command[check_load]=/opt/nagios/libexec/check_load -w $ARG1$ -c $ARG2$
#command[check_disk]=/opt/nagios/libexec/check_disk -w $ARG1$ -c $ARG2$ -p $ARG3$
#command[check_procs]=/opt/nagios/libexec/check_procs -w $ARG1$ -c $ARG2$ -s $ARG3$
command[check_AIX_processes.sh]=/opt/nagios/libexec/check_AIX_processes.sh -n $ARG1$
You do not have the required permissions to view the files attached to this post.
User avatar
tgriep
Madmin
Posts: 9177
Joined: Thu Oct 30, 2014 9:02 am

Re: Add a plugin AIX

Post by tgriep »

Can you login to the AIX server and run the plugin as the nagios user and post back the output?
To do that, run the following.

Code: Select all

su nagios
/opt/nagios/libexec/check_AIX_processes.sh -n sendmail
Be sure to check out our Knowledgebase for helpful articles and solutions!
migwi3@gmail.com
Posts: 8
Joined: Tue Aug 02, 2016 2:11 am

Re: Add a plugin AIX

Post by migwi3@gmail.com »

bash-4.3$ whoami
nagios
bash-4.3$
bash-4.3$
bash-4.3$
bash-4.3$
bash-4.3$
bash-4.3$ /opt/nagios/libexec/check_AIX_processes.sh -n sendmail
OK - System Process sendmail |processes= 1;;;00;
bash-4.3$
User avatar
tgriep
Madmin
Posts: 9177
Joined: Thu Oct 30, 2014 9:02 am

Re: Add a plugin AIX

Post by tgriep »

The plugin is setup on the AIX server to run as the Nagios user and that is good.
One thing, when you run the check_nrpe command and the command on the remote system needs an argument, you will have to use the -a option to pass the argument to the remote Agent.
Try running this command from the XI server and it should return the correct information from the AIX server.

Code: Select all

/usr/local/nagios/libexec/check_nrpe -H 172.28.221.55 -t 30 -c check_AIX_processes.sh -a sendmail
Be sure to check out our Knowledgebase for helpful articles and solutions!
migwi3@gmail.com
Posts: 8
Joined: Tue Aug 02, 2016 2:11 am

Re: Add a plugin AIX

Post by migwi3@gmail.com »

amazing ..how can i thank you?

[root@svdt1nagiosx01 jmwangi18]# su - nagios
Last login: Fri Jan 20 06:32:20 EST 2017 on pts/0
[nagios@svdt1nagiosx01 ~]$ /usr/local/nagios/libexec/check_nrpe -H 172.28.221.55 -t 30 -c check_AIX_processes.sh -a sendmail
OK - System Process sendmail |processes= 1;;;00;
[nagios@svdt1nagiosx01 ~]$



seems i was using the wrong option all along (-n)
[nagios@svdt1nagiosx01 ~]$ /usr/local/nagios/libexec/check_nrpe -H 172.28.221.55 -t 30 -c check_AIX_processes.sh -n sendmail
CHECK_NRPE: Received 0 bytes from daemon. Check the remote server logs for error messages.
[nagios@svdt1nagiosx01 ~]$


Immensely grateful. I am sorted now
User avatar
tgriep
Madmin
Posts: 9177
Joined: Thu Oct 30, 2014 9:02 am

Re: Add a plugin AIX

Post by tgriep »

Your very welcome.
I will close and mark this post as solved then. If you have any new questions, feel free to open a new post.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Locked