[Nagiosplug-help] Problem with the restarting of nrpe deamon

carole gimenez gimenez at cict.fr
Mon Jan 10 09:11:19 CET 2005


My nrpe.cfg looks at this:

#############################################################################
# NRPE Config File
#
# Last Modified: 10-27-2004
#
# NOTES:
# This is a 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.
#############################################################################



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



# ALLOWED HOST ADDRESSES
# This is a comma-delimited list of IP address of hosts 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=127.0.0.1,195.220.61.9



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



# 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



# 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



# 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_disk1]=/usr/local/nagios/libexec/check_disk -w 20 -c 10 
-p /dev/hda1
#command[check_disk2]=/usr/local/nagios/libexec/check_disk -w 20 -c 10 
-p /dev/hdb1
#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

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

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_disk]=/usr/local/nagios/libexec/check_disk -e -w $ARG1$ -c 
$ARG2$ -X $ARG3$ -X $ARG4$ -X $ARG5$ -X $ARG6$
#command[check_procs]=/usr/local/nagios/libexec/check_procs -w $ARG1$ -c 
$ARG2$ -s $ARG3$
command[check_procs]=/usr/local/nagios/libexec/check_procs -w $ARG1$ -c 
$ARG2$
command[check_swap]=/usr/local/nagios/libexec/check_swap -a -w $ARG1$ -c 
$ARG2$


Jason Martin wrote:

>On Mon, Jan 10, 2005 at 11:11:47AM +0100, carole gimenez wrote:
>  
>
>>When this host reboot, the nrpe deamon restart well but only the
>>check_disk is OK. The others checks returns this message:
>>    
>>
>What does your nrpe.cfg look like?
>
>-Jason Martin
>  
>

-- 
**********************************
GIMENEZ Carole
Ingénieur Système
CICT - Université Paul Sabatier
118, route de Narbonne
31062 Toulouse Cedex
Tél.: 05.61.36.60.44
Fax: 05.61.52.14.58
Mail: gimenez at cict.fr
**********************************	





More information about the Help mailing list