Error in AWS EC2 Uubuntu Monitoring

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
ivp2015
Posts: 142
Joined: Fri Feb 20, 2015 12:32 am

Re: Error in AWS EC2 Uubuntu Monitoring

Post by ivp2015 »

please find out the config file

root@ip-172-31-28-18:~# cat /etc/nagios/nrpe.cfg

Code: Select all

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



# 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, 182.74.168.35, 115.114.12.4
allowed_hosts=127.0.0.1, 115.114.12.4,182.74.168.35


# 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/[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
command[keystone]=/usr/lib64/nagios/plugins/check_procs -c 1: -w 3: -C keystone-all

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

command[check_disk]=/usr/local/nagios/libexec/check_disk $ARG1$ $ARG2$ $ARG3$
root@ip-172-31-28-18:~#



and also i have already share the nagios server UI adding host

Please let us know if anything required,

Thanks
Last edited by tgriep on Wed Apr 26, 2017 10:20 am, edited 1 time in total.
Reason: Added Code Wraps around large output.
User avatar
tgriep
Madmin
Posts: 9190
Joined: Thu Oct 30, 2014 9:02 am

Re: Error in AWS EC2 Uubuntu Monitoring

Post by tgriep »

Can you post this file so I can see if there is a duplicated check_disk command and that is causing the issue?

Code: Select all

include=/etc/nagios/nrpe_local.cfg
When you run the check, look in the /var/log/syslog file for the error that is generated by the NRPE Agent and post it here.
Be sure to check out our Knowledgebase for helpful articles and solutions!
ivp2015
Posts: 142
Joined: Fri Feb 20, 2015 12:32 am

Re: Error in AWS EC2 Uubuntu Monitoring

Post by ivp2015 »

Please find out the logs and file output

root@ip-172-31-28-18:~# cat /etc/nagios/nrpe_local.cfg
######################################
# Do any local nrpe configuration here
######################################
root@ip-172-31-28-18:~#


cat /var/log/syslog

Code: Select all

(/usr/lib/php5/maxlifetime))
May  1 10:45:01 ip-172-31-28-18 CRON[7899]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May  1 10:55:01 ip-172-31-28-18 CRON[9327]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May  1 11:05:01 ip-172-31-28-18 CRON[10266]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May  1 11:09:01 ip-172-31-28-18 CRON[10611]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
May  1 11:15:01 ip-172-31-28-18 CRON[11071]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May  1 11:17:01 ip-172-31-28-18 CRON[11245]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May  1 11:25:01 ip-172-31-28-18 CRON[11761]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May  1 11:35:01 ip-172-31-28-18 CRON[12470]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May  1 11:39:01 ip-172-31-28-18 CRON[12815]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
May  1 11:45:01 ip-172-31-28-18 CRON[13191]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May  1 11:55:01 ip-172-31-28-18 CRON[13941]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May  1 12:05:01 ip-172-31-28-18 CRON[14714]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May  1 12:09:01 ip-172-31-28-18 CRON[15061]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
May  1 12:15:01 ip-172-31-28-18 CRON[15629]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May  1 12:17:01 ip-172-31-28-18 CRON[15917]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May  1 12:25:01 ip-172-31-28-18 CRON[16550]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May  1 12:35:01 ip-172-31-28-18 CRON[17202]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May  1 12:39:01 ip-172-31-28-18 CRON[17547]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
May  1 12:45:01 ip-172-31-28-18 CRON[17979]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May  1 12:55:01 ip-172-31-28-18 CRON[18666]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May  1 13:05:01 ip-172-31-28-18 CRON[19379]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May  1 13:09:01 ip-172-31-28-18 CRON[19725]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
May  1 13:15:01 ip-172-31-28-18 CRON[20100]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May  1 13:17:01 ip-172-31-28-18 CRON[20296]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May  1 13:25:01 ip-172-31-28-18 CRON[20817]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May  1 13:35:01 ip-172-31-28-18 CRON[21585]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May  1 13:39:01 ip-172-31-28-18 CRON[21930]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
May  1 13:45:01 ip-172-31-28-18 CRON[22362]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May  1 13:55:01 ip-172-31-28-18 CRON[23049]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May  1 14:05:01 ip-172-31-28-18 CRON[23702]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May  1 14:09:01 ip-172-31-28-18 CRON[24048]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
May  1 14:15:01 ip-172-31-28-18 CRON[24480]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May  1 14:17:01 ip-172-31-28-18 CRON[24676]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May  1 14:25:01 ip-172-31-28-18 CRON[25192]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May  1 14:35:01 ip-172-31-28-18 CRON[25901]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May  1 14:39:01 ip-172-31-28-18 CRON[26246]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
May  1 14:45:01 ip-172-31-28-18 CRON[26621]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May  1 14:55:01 ip-172-31-28-18 CRON[27308]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May  1 15:05:01 ip-172-31-28-18 CRON[28018]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May  1 15:09:01 ip-172-31-28-18 CRON[28363]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
May  1 15:15:01 ip-172-31-28-18 CRON[29199]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May  1 15:17:01 ip-172-31-28-18 CRON[29397]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May  1 15:25:01 ip-172-31-28-18 CRON[30255]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
root@ip-172-31-28-18:~#
Last edited by tgriep on Mon May 01, 2017 11:52 am, edited 1 time in total.
Reason: Added Code Wraps around large output.
User avatar
tgriep
Madmin
Posts: 9190
Joined: Thu Oct 30, 2014 9:02 am

Re: Error in AWS EC2 Uubuntu Monitoring

Post by tgriep »

Can you edit your /etc/nagios/nrpe.cfg file and change the following line from

Code: Select all

command[check_disk]=/usr/local/nagios/libexec/check_disk $ARG1$ $ARG2$ $ARG3$
to

Code: Select all

command[check_disk]=/usr/lib/nagios/plugins/check_disk $ARG1$ $ARG2$ $ARG3$
Save the nrpe.cfg file and run the following as root on that server to restart the NREP Agent.

Code: Select all

service nrpe restart
Then if you still have the error, you will need to post exactly how the "/ Disk Usage" command is defined on the Nagios XI server so if it needs to be changed, we can help.
Be sure to check out our Knowledgebase for helpful articles and solutions!
ivp2015
Posts: 142
Joined: Fri Feb 20, 2015 12:32 am

Re: Error in AWS EC2 Uubuntu Monitoring

Post by ivp2015 »

after change disk check command its still not working please check the attachment,

Thanks
You do not have the required permissions to view the files attached to this post.
User avatar
tgriep
Madmin
Posts: 9190
Joined: Thu Oct 30, 2014 9:02 am

Re: Error in AWS EC2 Uubuntu Monitoring

Post by tgriep »

Please take a look at page 14 of the NRPE Troubleshooting guide for the solutions for the error you are receiving.
https://assets.nagios.com/downloads/nag ... utions.pdf
Be sure to check out our Knowledgebase for helpful articles and solutions!
ivp2015
Posts: 142
Joined: Fri Feb 20, 2015 12:32 am

Re: Error in AWS EC2 Uubuntu Monitoring

Post by ivp2015 »

Hi Team,

After changes in nrpe.cfg nrpe service not restarted bellow the error

ubuntu@ip-172-31-28-18:~$ service nrpe restart
stop: Unknown instance:
start: Rejected send message, 1 matched rules; type="method_call", sender=":1.26409" (uid=1000 pid=4805 comm="start nrpe ") interface="com.ubuntu.Upstart0_6.Job" member="Start" error name="(unset)" requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 comm="/sbin/init")
ubuntu@ip-172-31-28-18:~$



Thanks
User avatar
tgriep
Madmin
Posts: 9190
Joined: Thu Oct 30, 2014 9:02 am

Re: Error in AWS EC2 Uubuntu Monitoring

Post by tgriep »

It looks like you were logged in as the ubuntu user and you have to restart daemons while logged in as root or run if with sudo like the example below.

Code: Select all

sudo service nrpe restart
Try that and let us know if this works for you.
Be sure to check out our Knowledgebase for helpful articles and solutions!
ivp2015
Posts: 142
Joined: Fri Feb 20, 2015 12:32 am

Re: Error in AWS EC2 Uubuntu Monitoring

Post by ivp2015 »

yes its fine,

but still i am not able to monitor this host from nagios server,

Thanks
User avatar
tgriep
Madmin
Posts: 9190
Joined: Thu Oct 30, 2014 9:02 am

Re: Error in AWS EC2 Uubuntu Monitoring

Post by tgriep »

Is this a new NRPE install on a different host?
If so, how was the Agent installed?
I went back through the post and saw multiple IP addresses and hostnames from other servers and I want to make sure if it is a new or old install.

Can you post your nrpe.cfg file from your remote host?

Next, login as root to the remote server and run the following commands and post the output.

Code: Select all

netstat -anp |grep 5666
ps -ef --cols=300 | grep nrpe
find / -name nrpe.cfg
find / -name check_disk
find / -name check_mem
find / -name check_procs
Thanks
Be sure to check out our Knowledgebase for helpful articles and solutions!
Locked