Advertisement
Guest User

nrpe.cfg

a guest
May 27th, 2015
248
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
Bash 8.03 KB | None | 0 0
  1. #############################################################################
  2. # Sample NRPE Config File
  3. # Written by: Ethan Galstad (nagios@nagios.org)
  4. #
  5. # Last Modified: 11-23-2007
  6. #
  7. # NOTES:
  8. # This is a sample configuration file for the NRPE daemon.  It needs to be
  9. # located on the remote host that is running the NRPE daemon, not the host
  10. # from which the check_nrpe client is being executed.
  11. #############################################################################
  12.  
  13.  
  14. # LOG FACILITY
  15. # The syslog facility that should be used for logging purposes.
  16.  
  17. log_facility=daemon
  18.  
  19.  
  20.  
  21. # PID FILE
  22. # The name of the file in which the NRPE daemon should write it's process ID
  23. # number.  The file is only written if the NRPE daemon is started by the root
  24. # user and is running in standalone mode.
  25.  
  26. pid_file=/var/run/nrpe.pid
  27.  
  28.  
  29.  
  30. # PORT NUMBER
  31. # Port number we should wait for connections on.
  32. # NOTE: This must be a non-priviledged port (i.e. > 1024).
  33. # NOTE: This option is ignored if NRPE is running under either inetd or xinetd
  34.  
  35. server_port=5666
  36.  
  37.  
  38.  
  39. # SERVER ADDRESS
  40. # Address that nrpe should bind to in case there are more than one interface
  41. # and you do not want nrpe to bind on all interfaces.
  42. # NOTE: This option is ignored if NRPE is running under either inetd or xinetd
  43.  
  44. #server_address=127.0.0.1
  45.  
  46.  
  47.  
  48. # NRPE USER
  49. # This determines the effective user that the NRPE daemon should run as.  
  50. # You can either supply a username or a UID.
  51. #
  52. # NOTE: This option is ignored if NRPE is running under either inetd or xinetd
  53.  
  54. nrpe_user=nagios
  55.  
  56.  
  57.  
  58. # NRPE GROUP
  59. # This determines the effective group that the NRPE daemon should run as.  
  60. # You can either supply a group name or a GID.
  61. #
  62. # NOTE: This option is ignored if NRPE is running under either inetd or xinetd
  63.  
  64. nrpe_group=nagios
  65.  
  66.  
  67.  
  68. # ALLOWED HOST ADDRESSES
  69. # This is an optional comma-delimited list of IP address or hostnames
  70. # that are allowed to talk to the NRPE daemon. Network addresses with a bit mask
  71. # (i.e. 192.168.1.0/24) are also supported. Hostname wildcards are not currently
  72. # supported.
  73. #
  74. # Note: The daemon only does rudimentary checking of the client's IP
  75. # address.  I would highly recommend adding entries in your /etc/hosts.allow
  76. # file to allow only the specified host to connect to the port
  77. # you are running this daemon on.
  78. #
  79. # NOTE: This option is ignored if NRPE is running under either inetd or xinetd
  80.  
  81. allowed_hosts=127.0.0.1
  82.  
  83.  
  84.  
  85. # COMMAND ARGUMENT PROCESSING
  86. # This option determines whether or not the NRPE daemon will allow clients
  87. # to specify arguments to commands that are executed.  This option only works
  88. # if the daemon was configured with the --enable-command-args configure script
  89. # option.  
  90. #
  91. # *** ENABLING THIS OPTION IS A SECURITY RISK! ***
  92. # Read the SECURITY file for information on some of the security implications
  93. # of enabling this variable.
  94. #
  95. # Values: 0=do not allow arguments, 1=allow command arguments
  96.  
  97. dont_blame_nrpe=0
  98.  
  99.  
  100.  
  101. # BASH COMMAND SUBTITUTION
  102. # This option determines whether or not the NRPE daemon will allow clients
  103. # to specify arguments that contain bash command substitutions of the form
  104. # $(...).  This option only works if the daemon was configured with both
  105. # the --enable-command-args and --enable-bash-command-substitution configure
  106. # script options.
  107. #
  108. # *** ENABLING THIS OPTION IS A HIGH SECURITY RISK! ***
  109. # Read the SECURITY file for information on some of the security implications
  110. # of enabling this variable.
  111. #
  112. # Values: 0=do not allow bash command substitutions,
  113. #         1=allow bash command substitutions
  114.  
  115. allow_bash_command_substitution=0
  116.  
  117.  
  118.  
  119. # COMMAND PREFIX
  120. # This option allows you to prefix all commands with a user-defined string.
  121. # A space is automatically added between the specified prefix string and the
  122. # command line from the command definition.
  123. #
  124. # *** THIS EXAMPLE MAY POSE A POTENTIAL SECURITY RISK, SO USE WITH CAUTION! ***
  125. # Usage scenario:
  126. # Execute restricted commmands using sudo.  For this to work, you need to add
  127. # the nagios user to your /etc/sudoers.  An example entry for alllowing
  128. # execution of the plugins from might be:
  129. #
  130. # nagios          ALL=(ALL) NOPASSWD: /usr/lib/nagios/plugins/
  131. #
  132. # This lets the nagios user run all commands in that directory (and only them)
  133. # without asking for a password.  If you do this, make sure you don't give
  134. # random users write access to that directory or its contents!
  135.  
  136. # command_prefix=/usr/bin/sudo
  137.  
  138.  
  139.  
  140. # DEBUGGING OPTION
  141. # This option determines whether or not debugging messages are logged to the
  142. # syslog facility.
  143. # Values: 0=debugging off, 1=debugging on
  144.  
  145. debug=0
  146.  
  147.  
  148.  
  149. # COMMAND TIMEOUT
  150. # This specifies the maximum number of seconds that the NRPE daemon will
  151. # allow plugins to finish executing before killing them off.
  152.  
  153. command_timeout=60
  154.  
  155.  
  156.  
  157. # CONNECTION TIMEOUT
  158. # This specifies the maximum number of seconds that the NRPE daemon will
  159. # wait for a connection to be established before exiting. This is sometimes
  160. # seen where a network problem stops the SSL being established even though
  161. # all network sessions are connected. This causes the nrpe daemons to
  162. # accumulate, eating system resources. Do not set this too low.
  163.  
  164. connection_timeout=300
  165.  
  166.  
  167.  
  168. # WEEK RANDOM SEED OPTION
  169. # This directive allows you to use SSL even if your system does not have
  170. # a /dev/random or /dev/urandom (on purpose or because the necessary patches
  171. # were not applied). The random number generator will be seeded from a file
  172. # which is either a file pointed to by the environment valiable $RANDFILE
  173. # or $HOME/.rnd. If neither exists, the pseudo random number generator will
  174. # be initialized and a warning will be issued.
  175. # Values: 0=only seed from /dev/[u]random, 1=also seed from weak randomness
  176.  
  177. #allow_weak_random_seed=1
  178.  
  179.  
  180.  
  181. # INCLUDE CONFIG FILE
  182. # This directive allows you to include definitions from an external config file.
  183.  
  184. #include=<somefile.cfg>
  185.  
  186.  
  187.  
  188. # INCLUDE CONFIG DIRECTORY
  189. # This directive allows you to include definitions from config files (with a
  190. # .cfg extension) in one or more directories (with recursion).
  191.  
  192. #include_dir=<somedirectory>
  193. #include_dir=<someotherdirectory>
  194.  
  195.  
  196.  
  197. # COMMAND DEFINITIONS
  198. # Command definitions that this daemon will run.  Definitions
  199. # are in the following format:
  200. #
  201. # command[<command_name>]=<command_line>
  202. #
  203. # When the daemon receives a request to return the results of <command_name>
  204. # it will execute the command specified by the <command_line> argument.
  205. #
  206. # Unlike Nagios, the command line cannot contain macros - it must be
  207. # typed exactly as it should be executed.
  208. #
  209. # Note: Any plugins that are used in the command lines must reside
  210. # on the machine that this daemon is running on!  The examples below
  211. # assume that you have plugins installed in a /usr/local/nagios/libexec
  212. # directory.  Also note that you will have to modify the definitions below
  213. # to match the argument format the plugins expect.  Remember, these are
  214. # examples only!
  215.  
  216.  
  217. # The following examples use hardcoded command arguments...
  218.  
  219. command[check_users]=/usr/local/icinga/libexec/check_users -w 5 -c 10
  220. command[check_load]=/usr/local/icinga/libexec/check_load -w 15,10,5 -c 30,25,20
  221. command[check_hda1]=/usr/local/icinga/libexec/check_disk -w 20% -c 10% -p /dev/hda1
  222. command[check_zombie_procs]=/usr/local/icinga/libexec/check_procs -w 5 -c 10 -s Z
  223. command[check_total_procs]=/usr/local/icinga/libexec/check_procs -w 350 -c 400
  224.  
  225.  
  226. # The following examples allow user-supplied arguments and can
  227. # only be used if the NRPE daemon was compiled with support for
  228. # command arguments *AND* the dont_blame_nrpe directive in this
  229. # config file is set to '1'.  This poses a potential security risk, so
  230. # make sure you read the SECURITY file before doing this.
  231.  
  232. command[check_users]=/usr/lib64/nagios/plugins/check_users -w $ARG1$ -c $ARG2$
  233. command[check_load]=/usr/lib64/nagios/plugins/check_load -w $ARG1$ -c $ARG2$
  234. command[check_disk]=/usr/lib64/nagios/plugins/check_disk -w $ARG1$ -c $ARG2$ -p $ARG3$
  235. command[check_procs]=/usr/lib64/nagios/plugins/check_procs -w $ARG1$ -c $ARG2$ -s $ARG3$
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement