Help plz ASAP , NRPE- Check_ping

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.
Locked
eng_m_g
Posts: 19
Joined: Tue Mar 27, 2012 4:12 pm

Help plz ASAP , NRPE- Check_ping

Post by eng_m_g »

Dears,
The story is the following
I have master nagios called MHE

And I have remote nagios called(RH1)


And the remote server is connected to many servers , I just want to monitor these servers through ping on MHE
I have configured nrpe on both MHE &RH1
From master nagios I can make direct checks for services on the remote host like (chek_disk,check_swap…etc) through NRPE
but I can't make indirect checks for service ping for remote servers connected to remote host RH1
eng_m_g
Posts: 19
Joined: Tue Mar 27, 2012 4:12 pm

Re: Help plz ASAP , NRPE- Check_ping

Post by eng_m_g »

my NRPE.cfg

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



# 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



# 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_sda1]=/usr/local/nagios/libexec/check_disk -w 20% -c 10% -p /dev/mapper/VolGroup00-LogVol00
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 180 -c 300
command[check_ping]=/usr/local/nagios/libexec/check_ping -H 41.191.22.48 -w 3000.0,80% -c 5000.0,100% -p 5


# 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$
eng_m_g
Posts: 19
Joined: Tue Mar 27, 2012 4:12 pm

Re: Help plz ASAP , NRPE- Check_ping

Post by eng_m_g »

my confg file on master nagiso MHE for the remote host RH1

define host{
name RH1
use generic-host
check_period 24x7
check_interval 5
retry_interval 1
max_check_attempts 10
check_command check-host-alive
notification_period 24x7
notification_interval 30
notification_options d,r
contact_groups admins
register 0
}

##################################################################################################
define host{
use RH1
host_name RH1
address 41.191.22.48
}
###################################################################################################
define hostgroup{
hostgroup_name MediaCity
alias RH1
members RH1
}
###################################################################################################
define service{
use generic-service
host_name RH1
service_description CPU Load
check_command check_nrpe!check_load
}
define service{
use generic-service
host_name RH1
service_description Current Users
check_command check_nrpe!check_users
}
define service{
use generic-service
host_name RH1
service_description /dev/mapper/VolGroup00-LogVol00 Free Space
check_command check_nrpe!check_sda1
}
define service{
use generic-service
host_name RH1
service_description Total Processes
check_command check_nrpe!check_total_procs
}

###################################################################################################
# IPTV switch
###################################################################################################
define host{
use generic-switch
host_name Main Switch
alias Cisco Switch-3560
address 10.1.1.100
hostgroups MediaCity
}
##################################################
define service{
use generic-service
host_name Main Switch
service_description PING
check_command check_nrpe!check_ping!200.0,20%!600.0,60%
normal_check_interval 5
retry_check_interval 1
}

###################################################################################################
# IPTV Servers
###################################################################################################
define host{
use generic-switch ; Inherit default values from a template
host_name Portal Generator ; The name we're giving to this switch
alias DreamGallery ; A longer name associated with the switch
address 10.1.0.3 ; IP address of the switch
hostgroups MediaCity ; Host groups this switch is associated with
}

define host{
use generic-switch ; Inherit default values from a template
host_name Portal Server ; The name we're giving to this switch
alias DreamGallery ; A longer name associated with the switch
address 10.1.0.11 ; IP address of the switch
hostgroups MediaCity ; Host groups this switch is associated with
}

define host{
use generic-switch ; Inherit default values from a template
host_name DataBase ; The name we're giving to this switch
alias DreamGallery ; A longer name associated with the switch
address 10.1.0.13 ; IP address of the switch
hostgroups MediaCity ; Host groups this switch is associated with
}

define host{
use generic-switch ; Inherit default values from a template
host_name Controller1 ; The name we're giving to this switch
address 10.1.0.18 ; IP address of the switch
hostgroups MediaCity ; Host groups this switch is associated with
}

define host{
use generic-switch ; Inherit default values from a template
host_name Controller2 ; The name we're giving to this switch
address 10.1.0.19 ; IP address of the switch
hostgroups MediaCity ; Host groups this switch is associated with
}

define host{
use generic-switch ; Inherit default values from a template
host_name EdgeWare ; The name we're giving to this switch
alias VOD ; A longer name associated with the switch
address 10.1.0.15 ; IP address of the switch
hostgroups MediaCity ; Host groups this switch is associated with
}

define host{
use generic-switch ; Inherit default values from a template
host_name Boot Server ; The name we're giving to this switch
alias MBS ; A longer name associated with the switch
address 10.1.0.100 ; IP address of the switch
hostgroups MediaCity ; Host groups this switch is associated with
}
#############################################
define service{
use generic-service
host_name Portal Server
service_description PING
check_command check_nrpe!check_ping!200.0,20%!600.0,60%
normal_check_interval 5
retry_check_interval 1
}



define service{
use generic-service
host_name Portal Generator
service_description PING
check_command check_nrpe!check_ping!200.0,20%!600.0,60%
normal_check_interval 5
retry_check_interval 1
}

define service{
use generic-service
host_name Boot Server
service_description PING
check_command check_nrpe!check_ping!200.0,20%!600.0,60%
normal_check_interval 5
retry_check_interval 1
}

define service{
use generic-service
host_name Controller1
service_description PING
check_command check_nrpe!check_ping!200.0,20%!600.0,60%
normal_check_interval 5
retry_check_interval 1
}

define service{
use generic-service
host_name Controller2
service_description PING
check_command check_nrpe!check_ping!200.0,20%!600.0,60%
normal_check_interval 5
retry_check_interval 1
}

define service{
use generic-service
host_name DataBase
service_description PING
check_command check_nrpe!check_ping!200.0,20%!600.0,60%
normal_check_interval 5
retry_check_interval 1
}

define service{
use generic-service
host_name EdgeWare
service_description PING
check_command check_nrpe!check_ping!200.0,20%!600.0,60%
normal_check_interval 5
retry_check_interval 1
}

###############################################################################################


kindly help me ASAP coz I have to close this task before the end of this week
slansing
Posts: 7698
Joined: Mon Apr 23, 2012 4:28 pm
Location: Travelling through time and space...

Re: Help plz ASAP , NRPE- Check_ping

Post by slansing »

Hello,

Have you tried adding in the master XI server's IP to the Allowed Host Address section and then running the commands?

Code: Select all

# ALLOWED HOST ADDRESSES
...
allowed_hosts=<Master.IP.Goes.Here
eng_m_g
Posts: 19
Joined: Tue Mar 27, 2012 4:12 pm

Re: Help plz ASAP , NRPE- Check_ping

Post by eng_m_g »

first i'm running nagios core ,second do u mean the nrpe file? if yes this is my nrpe file
# default: on
# description: NRPE (Nagios Remote Plugin Executor)
service nrpe
{
flags = REUSE
socket_type = stream
port = 5666
wait = no
user = nagios
group = nagios
server = /usr/local/nagios/bin/nrpe
server_args = -c /usr/local/nagios/etc/nrpe.cfg --inetd
log_on_failure += USERID
disable = no
only_from = 127.0.0.1 41.191.22.49
}
User avatar
nscott
Posts: 1040
Joined: Wed May 11, 2011 8:54 am

Re: Help plz ASAP , NRPE- Check_ping

Post by nscott »

You're going to have to define a command on your remote NRDP server that is something like the following:

command[check_other_server_ping]=/usr/local/nagios/libexec/check_ping -H $ARG1$ -w 3000.0,80% -c 5000.0,100% -p 5

You'll also need to allow arguments with NRPE, so change the 'dont_blame_nrpe' option to 1.

Now, you'll need to make the host for the ping check, you could also do this with a service, but we'll just using the host for now: (the following configs will need to be done on the Nagios server side)

Code: Select all

define host{
use generic-host
check_command check_nrpe_extended!check_other_server_ping!<IP of nrpe server>
host_name MyHostname
alias MyAlias
address 10.1.0.100
hostgroups PingableFromNRPE
}
And the command definition:

Code: Select all

define command{
command_name check_nrpe_extended
command_line $USER1$/check_nrpe -H $ARG1$ -t 30 -c $HOSTADDRESS$
}
This might take some fiddling on your part, but that should get you pretty close
Nicholas Scott
Former Nagios employee
eng_m_g
Posts: 19
Joined: Tue Mar 27, 2012 4:12 pm

Re: Help plz ASAP , NRPE- Check_ping

Post by eng_m_g »

nscott wrote:You're going to have to define a command on your remote NRDP server that is something like the following:

command[check_other_server_ping]=/usr/local/nagios/libexec/check_ping -H $ARG1$ -w 3000.0,80% -c 5000.0,100% -p 5

You'll also need to allow arguments with NRPE, so change the 'dont_blame_nrpe' option to 1.

Now, you'll need to make the host for the ping check, you could also do this with a service, but we'll just using the host for now: (the following configs will need to be done on the Nagios server side)

Code: Select all

define host{
use generic-host
check_command check_nrpe_extended!check_other_server_ping!<IP of nrpe server>
host_name MyHostname
alias MyAlias
address 10.1.0.100
hostgroups PingableFromNRPE
}
And the command definition:

Code: Select all

define command{
command_name check_nrpe_extended
command_line $USER1$/check_nrpe -H $ARG1$ -t 30 -c $HOSTADDRESS$
}
This might take some fiddling on your part, but that should get you pretty close
Thank u very much for ur answer, but i don't know what do u mean by NRDP server, so could u please make the accurate confg for me to copy and paste it, i'll be appreciated
Locked