############################################################################# # 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/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 # Django : 2015-01-27 # default: #server_address=127.0.0.1 server_address=10.0.0.67 # 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=nrpe # 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=nrpe # 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 # Django : 2015-01-27 # default: allowed_hosts=127.0.0.1 allowed_hosts=10.0.0.127 # 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 # 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= # COMMAND DEFINITIONS # Command definitions that this daemon will run. Definitions # are in the following format: # # command[]= # # When the daemon receives a request to return the results of # it will execute the command specified by the 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... # Django : 2015-01-27 # allgemeiner Host-Teil command[check_tcp_5666]=/usr/lib64/nagios/plugins/check_tcp -H 10.0.0.67 -p 5666 command[check_users]=/usr/lib64/nagios/plugins/check_users -w 5 -c 10 command[check_load]=/usr/lib64/nagios/plugins/check_load -w 15,10,5 -c 30,25,20 command[check_fs_boot]=/usr/lib64/nagios/plugins/check_disk -w 20% -c 10% -p /boot command[check_fs_root]=/usr/lib64/nagios/plugins/check_disk -w 20% -c 10% -p / command[check_fs_varlog]=/usr/lib64/nagios/plugins/check_disk -w 20% -c 10% -p /var/log command[check_fs_ramdisk_sudo]=/usr/bin/sudo /usr/lib64/nagios/plugins/check_disk -w 20% -c 10% -p /var/spool/amavisd/tmp command[check_swap]=/usr/lib64/nagios/plugins/check_swap -w 50% -c 25% command[check_updates]=/usr/lib64/nagios/plugins/check_updates -w 1 -c 5 command[check_zombie_procs]=/usr/lib64/nagios/plugins/check_procs -w 5 -c 10 -s Z command[check_total_procs]=/usr/lib64/nagios/plugins/check_procs -w 175 -c 225 command[check_running_iptables]=/usr/lib64/nagios/plugins/check_iptables_status -T INPUT -r 95 command[check_if_traffic_eth0]=/usr/bin/sudo /usr/lib64/nagios/plugins/check_if_traffic -v 3 -U nagios -P KI/3Db+MIgeqaF0DSg3iyXNBbVY -H 127.0.0.1 -B -b 100 -u m -i eth0 command[check_crond]=/usr/lib64/nagios/plugins/check_running -p 'crond' # Mailserver spezifische Test command[check_running_postfix]=/usr/lib64/nagios/plugins/check_running -p 'postfix' command[check_running_amavisd]=/usr/lib64/nagios/plugins/check_running -p 'amavisd' command[check_running_clamd]=/usr/lib64/nagios/plugins/check_running -p 'clamd' command[check_clamav]=/usr/lib64/nagios/plugins/check_clamav -w 3 -c 4 command[check_tcp_25]=/usr/lib64/nagios/plugins/check_tcp -H 127.0.0.1 -p 25 command[check_tcp_783]=/usr/lib64/nagios/plugins/check_tcp -H 127.0.0.1 -p 783 command[check_tcp_8899]=/usr/lib64/nagios/plugins/check_tcp -H 10.0.0.67 -p 8899 command[check_tcp_9998]=/usr/lib64/nagios/plugins/check_tcp -H 127.0.0.1 -p 9998 command[check_tcp_10024]=/usr/lib64/nagios/plugins/check_tcp -H 10.0.0.67 -p 10024 command[check_sending_mail_10024]=/usr/lib64/nagios/plugins/check_smtp -H 127.0.0.1 -C -p 10024 -4 -F vml000020.dmz.nausch.org 'helo vml000020.dmz.nausch.org' -R '250 OK' -C 'mail from: weather@vml000020.dmz.nausch.org' -R '250 OK' -C 'rcpt to:' -R '250 OK' command[check_sending_mail_10025]=/usr/lib64/nagios/plugins/check_smtp -H 10.0.0.87 -C -p 10025 -4 -F vml000020.dmz.nausch.org 'helo vml000020.dmz.nausch.org' -R '250 OK' -C 'mail from: weather@vml000020.dmz.nausch.org' -R '250 OK' -C 'rcpt to:' -R '250 OK' # 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/lib64/nagios/plugins/check_users -w $ARG1$ -c $ARG2$ #command[check_load]=/usr/lib64/nagios/plugins/check_load -w $ARG1$ -c $ARG2$ #command[check_disk]=/usr/lib64/nagios/plugins/check_disk -w $ARG1$ -c $ARG2$ -p $ARG3$ #command[check_procs]=/usr/lib64/nagios/plugins/check_procs -w $ARG1$ -c $ARG2$ -s $ARG3$ # 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=/etc/nrpe.d/