<html> <head> <style> .hmmessage P { margin:0px; padding:0px } body.hmmessage { font-size: 10pt; font-family:Verdana } </style> </head> <body class='hmmessage'> jumping in a bit late on this one... so it sounds like the check itself works on the local box... so if you run from the nagios server ./libexec/check_nrpe -H server -P 5666 -t 10 -c check_root and then... ./libexec/check_nrpe -H server -P 5666 -t 10 -c check_ora could your Nagios server also be connecting to the wrong server... ? I've had DNS issues drive me berserk before. -- Mat W. - <A href="http://www.techadre.com/">http://www.techadre.com</A> <HR id=stopSpelling> Date: Wed, 15 Jul 2009 16:14:27 +0300 From: juki.emma@gmail.com To: guidosh@gmail.com CC: nagios-users@lists.sourceforge.net Subject: Re: [Nagios-users] Monitoring disk usage Hi Guy, My findings in-line... <DIV class=EC_gmail_quote>2009/7/15 Guy Waugh <<A>guidosh@gmail.com</A>> <BLOCKQUOTE class=EC_gmail_quote style="PADDING-LEFT: 1ex"> <DIV class=EC_gmail_quote> <DIV>They should only be defined in one place. From those errors, it sounds like NRPE on the monitored host doesn't have those commands defined, which suggests that it's not reading your nrpe.cfg config file. I would check out NRPE on the monitored host... do any checks on that host work at all? </DIV></DIV></BLOCKQUOTE> <DIV> Yes, indeed the checks do work. These have been run on the monitored host. See below; bash$ /usr/local/nagios/libexec/check_disk -w 30% -c 20% -p /var/opt/BGw/Server1 DISK OK - free space: /var/opt/BGw/Server1 35606 MB (68% inode=97%);| /var/opt/BGw/Server1=16589MB;37990;43417;0;54272 bash$ /usr/local/nagios/libexec/check_disk -w 30% -c 20% -p /var/opt/BGw/Server1 DISK OK - free space: /var/opt/BGw/Server1 35614 MB (68% inode=97%);| /var/opt/BGw/Server1=16581MB;37990;43417;0;54272 </DIV> <BLOCKQUOTE class=EC_gmail_quote style="PADDING-LEFT: 1ex"> <DIV class=EC_gmail_quote> <DIV>Is the nrpe.cfg file in /usr/local/nagios/etc? Is either the NRPE daemon running or xinetd is handling the NRPE connections? Is the host listening on port 5666? Are the permissions on the nrpe.cfg file correct? What happens when you run an NRPE service check for that host manually, from the nagios server?</DIV></DIV></BLOCKQUOTE> <DIV> Yes, the nrpe.cfg file is in /usr/local/nagios/etc with permissions; bash$ ls -l /usr/local/nagios/etc/ total 32 -rw-r--r-- 1 nagios nagios 7871 Jul 15 14:21 nrpe.cfg The NRPE daemon is running on the pid... bash$ ps -ef | grep nrpe root 25866 14582 0 16:01:25 pts/4 0:00 grep nrpe nagios 1640 1 0 Jan 09 ? 49:38 /usr/local/nagios/bin/nrpe -c /usr/local/nagios/etc/nrpe.cfg -d nagios 9702 1 0 Jul 09 ? 1:27 /usr/local/nagios/bin/nrpe -c /usr/local/nagios/etc/nrpe.cfg -d And listening on.... bash$ netstat -a | grep nrpe emm4.nrpe *.* 0 0 49152 0 LISTEN *.nrpe *.* 0 0 49152 0 LISTEN localhost.nrpe *.* 0 0 49152 0 LISTEN On running a telnet (on port 5666) to the monitored host from the nagios monitoring server, I get; relay$ telnet 10.0.0.5 5666 Trying 10.0.0.5... Connected to 10.0.0.5. Escape character is '^]'. When I run an NRPE service check for the monitored host manually from the nagios server, I get; relay$ /usr/local/nagios/libexec/check_nrpe -H 10.0.0.5 -p 5666 -c check_disk /var/opt/mediation/ora DISK OK - free space: / 22848 MB (37% inode=23%);| /=37500MB;54862;57910;0;60958 1491 This shows that the check_nrpe command is retrieving the details for the root (/) partition and NOT those of the /var/opt/mediation/ora partition </DIV> <BLOCKQUOTE class=EC_gmail_quote style="PADDING-LEFT: 1ex"> <DIV class=EC_gmail_quote> <DIV> If none of that give you any joy, post the nrpe.cfg file to this list if you like, suitably obfuscated of course. </DIV></DIV></BLOCKQUOTE> <DIV> A copy of the nrpe.cfg file as follows; bash$ more nrpe.cfg ############################################################################# # Sample NRPE Config File # Written by: Ethan Galstad (<A>nagios@nagios.org</A>) # # 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 #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. # # 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=10.0.0.5 # 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/[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/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_hda1]=/usr/local/nagios/libexec/check_disk -w 20% -c 10% -p /dev/hda1 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 #emm4 specific commands# command[check_root]=/usr/local/nagios/libexec/check_disk -w 30% -c 20% -p / command[check_var]=/usr/local/nagios/libexec/check_disk -w 30% -c 20% -p /var command[check_server1]=/usr/local/nagios/libexec/check_disk -w 30% -c 20% -p /var/opt/BGw/Server1 command[check_ora]=/usr/local/nagios/libexec/check_disk -w 30% -c 20% -p /var/opt/mediation/ora command[check_swap]= /usr/local/nagios/libexec/check_swap -a -w 10% -c 5% command[check_procs]=/usr/local/nagios/libexec/check_procs -w 300 -c 400 command[check_ssh]=/usr/local/nagios/libexec/check_ssh -4 -t 10 -p 22 localhost command[check_ftp]=/usr/local/nagios/libexec/check_ftp -t 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$ It still puzzles me.... Regards, Juki </DIV></DIV> <hr />Lauren found her dream laptop. <a href='http://www.microsoft.com/windows/choosepc/?ocid=ftp_val_wl_290' target='_new'>Find the PC that�s right for you.</a></body> </html>