NRPE Problems

Shoaibi iknewitalready at gmail.com
Mon Aug 11 09:39:36 CEST 2008


Server Machine: Prompt is ">", FreeBSD6 with ipfw. Nagios v2.12, using
nrpe with -n as show afterwards. (192.168.40.1)
Client Machine: Prompt "sysadmin#", NRPE v2.12 without SSL running as
daemon (192.168.40.40)


==========
On Server:
==========

On server on the nagios front-end i am getting:
"CHECK_NRPE: Received 0 bytes from daemon. Check the remote server
logs for error messages. "

Alert Configuration file on monitoring server:

####### Alerts on SysAdmin Workstation
# service to check load
define service{
       use                        local-service
       host_name                  sysadmin
       service_description        Load on sysadmin
       notifications_enabled           0
       check_command              check_nrpe!check_load
}



# service to check users
define service{
       use                        local-service
       host_name                  sysadmin
       service_description        Users on sysadmin
       notifications_enabled           0
       check_command              check_nrpe!check_users
}


# service to check hard disk
define service{
       use                        local-service
       host_name                  sysadmin
       service_description        Root Partition on  sysadmin
       notifications_enabled           0
       check_command              check_nrpe!check_disk1
}

# service to check total processes
define service{
          use                 local-service
          host_name           sysadmin
          service_description Total Processes on sysadmin
          notifications_enabled           0
          check_command       check_nrpe!check_total_procs
          }

# service to check zombie processes
define service{
          use                 local-service
          host_name           sysadmin
          service_description Zombie Processes on sysadmin
          notifications_enabled           0
          check_command       check_nrpe!check_zombie_procs
          }


# service to check swap
define service{
          use                 local-service
          host_name           sysadmin
          service_description Swap on sysadmin
          notifications_enabled           0
          check_command       check_nrpe!check_swap
          }


=================================================
so you see that i am using check_nrpe, not check_tcp.
=================================================

=================================
Check command for check_nrpe on server
=================================

define command{
        command_name       check_nrpe
        command_line       $USER1$/check_nrpe -n -H $HOSTADDRESS$ -c
$ARG1$ -t 20
        }

================================================
Firewall on server:
===============================================
 sudo ipfw show | grep 5666
> sudo ipfw show | grep 40.40
02104      369      29160 allow tcp from 192.168.40.40 to me dst-port
22 in recv vr0





===========
On Client end
==========

=================
Some part of the log
=================
Aug 11 07:05:31 sysadmin nrpe[3115]: Could not read request from
client, bailing out...
Aug 11 07:05:31 sysadmin nrpe[3113]: Could not read request from
client, bailing out...
Aug 11 07:05:32 sysadmin nrpe[3117]: Could not read request from
client, bailing out...
Aug 11 07:06:03 sysadmin nrpe[3120]: Could not read request from
client, bailing out...
Aug 11 07:07:10 sysadmin nrpe[3127]: Could not read request from
client, bailing out...
Aug 11 07:07:35 sysadmin nrpe[3134]: Could not read request from
client, bailing out...


============
NRPE on client
============
sysadmin# ps aux | grep nrp | grep -v grep
nagios   2867  0.0  0.1  3104  1204  ??  Ss    6:42AM   0:00.01
/usr/local/sbin/nrpe -c /usr/local/etc/nrpe.cfg --daemon



=================
NRPE Config
=================
#############################################################################
# Sample NRPE Config File
# Written by: Ethan Galstad (nagios at nagios.org)
#
# Last Modified: 12-30-2002
#
# 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.
#############################################################################



# 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,192.168.40.1, 192.168.50.1,192.168.40.119



# 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



# 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



# 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!

command[check_users]=/usr/local/libexec/nagios/check_users -w 5 -c 10
command[check_load]=/usr/local/libexec/nagios/check_load -w 15,10,5 -c 30,25,20
command[check_disk1]=/usr/local/libexec/nagios/check_disk -w 20 -c 10
-p /dev/ad4s1a
command[check_disk2]=/usr/local/libexec/nagios/check_disk -w 20 -c 10
-p /dev/ad4s1e
command[check_zombie_procs]=/usr/local/libexec/nagios/check_procs -w 5
-c 10 -s Z
command[check_total_procs]=/usr/local/libexec/nagios/check_procs -w 150 -c 200
command[check_swap]=/usr/local/libexec/nagios/check_swap -w 20% -c 10%





Any other thing you require?

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Nagios-users mailing list
Nagios-users at 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





More information about the Users mailing list