The settings that I have in nrpe.cfg file appear to be correct, but just in
case, I have included it in this e-mail.
If there are no other ideas, I'll have no choice but to fall back to version 1.x
of the client and server applications.
________________________________
From: David Gerbec [mailto:[EMAIL PROTECTED]
Sent: Fri 12/29/2006 9:58 AM
To: Kaplan, Andrew H.
Cc: Andy Shellam (Mailing Lists); Nagios Users mailinglist
Subject: Re: [Nagios-users] Service Check Timed Out Error
Hi!
Kaplan, Andrew H. pravi:
>> If i understand correctly, u ran the plugin su'ed to the nagios user and
>> the command completed successfully?
>
> That is correct.
>
>> If that's the case, then please check if the xinetd daemon is running
>> and what the setting for nagios-nrpe are for xinetd.
>
> As far as the client is concerned, nrpe is not being run via xinetd, it is
being
> run as a standalone daemon. This is command syntax that is used for
> running the daemon:
>
> /usr/local/nagios/bin/nrpe -c /usr/local/nagios/etc/nrpe.cfg -d
Have you checked the setting in the nrep.cfg file? Like server_port,
allowed_hosts, nrpe_user, nrpe_group?
I actaully have only one box, that's running NRPE as a standalone
daemon. U have to add the server IP in the allowed_hosts section (add
the server to /etc/hosts.allow as well).
And u need to restart the daemon on every change.
If u got all the above set up correcty, then i'm affraid i'm out of
ideas... :o(
Regards,
D.
>
> The user account running the daemon is nagios. This account has its own
> home directory, password, and uses the /bin/bash shell.
>
> As far as the server is concerned, nrpe is not present in xinetd, but does
have
> a startup script in the /etc/init.d directory. It is currently not turned on,
> but it can be if so needed.
>
>> What's your NRPE version on the server and the client machine?
>
> The version of NRPE on the server is 2.5.1, and this is the package that came
> bundled with the operating system which is Fedora Core 5.
> The version of NRPE on the client is also 2.5.1. The difference between that
on
> the server and client is that the client was compiled from source. Also, even
> though the client version is 2.5.1, according to the tar file that I
downloaded
> from the Nagios website, the version is supposedly 2.5.2.
>
>
> -----Original Message-----
> From: David Gerbec [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 29, 2006 9:30 AM
> To: Kaplan, Andrew H.
> Cc: Andy Shellam (Mailing Lists); Nagios Users mailinglist
> Subject: Re: [Nagios-users] Service Check Timed Out Error
>
>
> Hi!
>
> Kaplan, Andrew H. pravi:
>> I ran the chsh command to change the nologin shell for the nagios user to
>> /bin/bash, and also provided a password for the nagios account. After that,
>> I ran the check_nrpe command again from the command line, ie: manually, and
> was
>> able to get a response back from the nrpe client.
>
> If i understand correctly, u ran the plugin su'ed to the nagios user and
> the command completed successfully?
>
> If that's the case, then please check if the xinetd daemon is running
> and what the setting for nagios-nrpe are for xinetd.
>
> What's your NRPE version on the server and the client machine?
>
> I'm still sure, u got premission problems :o).
>
>
>
>
> Regards,
> D.
>
>> Listed below are posts that were requested from a previous e-mail:
>>
>> 1. The output of "check_nrpe -H <nrpe_client> -c <remote_command>" run
>> as the Nagios user:
>> DISK OK [50534480 kb (99%) free on cosmos2:/database
>>
>> 2. The Nagios command definition for your check_nrpe command:
>> # 'check_nrpe' command definition
>> define command{
>> command_name check_nrpe
>> command_line $USER1$/check_nrpe -H $HOSTADDRESS$ -t 60 -c $ARG1$
>>
>> 3. A Nagios service definition that uses the check_nrpe service on the
>> relevant host:
>> command[check_disk1]=/usr/local/nagios/libexec/check_disk -w 20% -c 10% -p
>> /cosmos2/database
>>
>>
>>
>>
>>
>> -----Original Message-----
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED] On Behalf Of Andy Shellam
>> (Mailing Lists)
>> Sent: Friday, December 29, 2006 8:58 AM
>> To: Kaplan, Andrew H.
>> Cc: Nagios Users mailinglist
>> Subject: Re: [Nagios-users] Service Check Timed Out Error
>>
>> Kaplan, Andrew H. wrote:
>>> I configured the ip tables on both the nagios server and the nrpe client to
>>> allow all inbound and outbound traffic. Additionally, I made sure the
>>> /etc/services file on both systems had port 5666 open to tcp and udp
traffic.
>
>>> I was able to telnet to port 5666 on the nrpe client, but I was still
getting
>> a
>>> connection refused for the same port on the server.
>>>
>> You won't be able to telnet back from the client to the server unless
>> you're also running nrpe on the server.
>> As long as you can telnet server to client on that port, you're fine.
>>
>> Also nrpe uses TCP only (I believe.)
>>> I verified also, that the network speed, ie: half vs. full duplex, was the
>> same
>>> for both systems. The speed here is 100 half duplex no autonegotiation.
>>>
>>> I repeatedly ran the check_nrpe command manually and did get output back
> every
>>> time. Why am I able to run the command manually, but not automatically?
>>>
>> Like David says, try su'ing to the Nagios user and running the command
>> manually.
>>
>> If all else fails, please post back the following:
>>
>>
>> 2. The Nagios command definition for your check_nrpe command
>> 3. A Nagios service definition that uses the check_nrpe service on the
>> relevant host
>>
>> Andy.
>>
>> -------------------------------------------------------------------------
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to share your
>> opinions on IT & business topics through brief surveys - and earn cash
>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>> _______________________________________________
>> Nagios-users mailing list
>> Nagios-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/nagios-users
>> ::: Please include Nagios version, plugin version (-v) and OS when reporting
> any
>> issue.
>> ::: Messages without supporting info will risk being sent to /dev/null
>>
>>
>>
>>
>> THE INFORMATION TRANSMITTED IN THIS ELECTRONIC COMMUNICATION IS INTENDED ONLY
> FOR THE PERSON OR ENTITY TO WHOM IT IS ADDRESSED AND MAY CONTAIN CONFIDENTIAL
> AND/OR PRIVILEGED MATERIAL. ANY REVIEW, RETRANSMISSION, DISSEMINATION OR
OTHER
> USE OF OR TAKING OF ANY ACTION IN RELIANCE UPON, THIS INFORMATION BY PERSONS
OR
> ENTITIES OTHER THAN THE INTENDED RECIPIENT IS PROHIBITED. IF YOU RECEIVED
THIS
> INFORMATION IN ERROR, PLEASE CONTACT THE SENDER AND THE PRIVACY OFFICER, AND
> PROPERLY DISPOSE OF THIS INFORMATION.
>>
>>
>> -------------------------------------------------------------------------
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to share your
>> opinions on IT & business topics through brief surveys - and earn cash
>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>> _______________________________________________
>> Nagios-users mailing list
>> Nagios-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/nagios-users
>> ::: Please include Nagios version, plugin version (-v) and OS when reporting
> any issue.
>> ::: Messages without supporting info will risk being sent to /dev/null
>
>
>
>
>
> THE INFORMATION TRANSMITTED IN THIS ELECTRONIC COMMUNICATION IS INTENDED ONLY
FOR THE PERSON OR ENTITY TO WHOM IT IS ADDRESSED AND MAY CONTAIN CONFIDENTIAL
AND/OR PRIVILEGED MATERIAL. ANY REVIEW, RETRANSMISSION, DISSEMINATION OR OTHER
USE OF OR TAKING OF ANY ACTION IN RELIANCE UPON, THIS INFORMATION BY PERSONS OR
ENTITIES OTHER THAN THE INTENDED RECIPIENT IS PROHIBITED. IF YOU RECEIVED THIS
INFORMATION IN ERROR, PLEASE CONTACT THE SENDER AND THE PRIVACY OFFICER, AND
PROPERLY DISPOSE OF THIS INFORMATION.
>
>
THE INFORMATION TRANSMITTED IN THIS ELECTRONIC COMMUNICATION IS INTENDED ONLY
FOR THE PERSON OR ENTITY TO WHOM IT IS ADDRESSED AND MAY CONTAIN CONFIDENTIAL
AND/OR PRIVILEGED MATERIAL. ANY REVIEW, RETRANSMISSION, DISSEMINATION OR OTHER
USE OF OR TAKING OF ANY ACTION IN RELIANCE UPON, THIS INFORMATION BY PERSONS OR
ENTITIES OTHER THAN THE INTENDED RECIPIENT IS PROHIBITED. IF YOU RECEIVED THIS
INFORMATION IN ERROR, PLEASE CONTACT THE SENDER AND THE PRIVACY OFFICER, AND
PROPERLY DISPOSE OF THIS INFORMATION.
#############################################################################
# Sample NRPE Config File
# Written by: Ethan Galstad ([EMAIL PROTECTED])
#
# Last Modified: 02-23-2006
#
# 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.
#############################################################################
# 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=132.183.12.169
# 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=127.0.0.1,132.183.12.228
# 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
# 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_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_procs]=/usr/local/nagios/libexec/check_procs -w $ARG1$ -c $ARG2$
-s $ARG3$
command[check_disk1]=/usr/local/nagios/libexec/check_disk -w 20% -c 10% -p
/cosmos2/database
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
