[Fwd: CHECK_NRPE: Error receiving data from daemon help needed]
Jan Scholten
Jan.Scholten at iconz.net
Sun Nov 28 22:46:10 CET 2004
roadbox wrote:
Do you think that you need to post your text every 8 hours? Aren't we
allowed to have a weekend? That's rude and i thought of just deleting
your mails and add you to the spamlist.
What steps did you take for debugging nrpe? Did you install a package or
from the source (missed libssl-devel?)
Did you enter the line in /etc/services?
Turn on debugging in the nrpe.cfg
If you execute check_nrpe -H jmooo
What output do you get, what is in the logfiles?
Which Versions did you install?
Your Configs seems to be fine (i don't know xinetd or the IPs of your
host, so ..)
Jan
> Hello Linux challenged here
> I've yet to successfully use the npre/check_nrpe tools, but I sure wont to
> I believe my problem is in the .cfg files...I 've enclosed them below...
>
> Could someone "correct them" and/or post a working example for me to
> adjust appropriate to my system
> ###by Mo===
> define service{
> name generic-service
> active_checks_enabled 1
> passive_checks_enabled 1
> parallelize_check 1
> obsess_over_service 1
> check_freshness 1
> notifications_enabled 1
> event_handler_enabled 1
> flap_detection_enabled 1
> process_perf_data 1
> retain_status_information 1
> retain_nonstatus_information 1
> register 0
> }
>
>
> ###service defination
> define service{
> use generic-service
> host_name jmooo
> service_description check_users
> is_volatile 0
> check_period 24x7
> max_check_attempts 3
> normal_check_interval 5
> retry_check_interval 1
> contact_groups staff
> notification_interval 120
> notification_period 24x7
> notification_options w,u,c,r
> check_command check_nrpe!check_users
> }
>
>
> ###service defination
> ###service defination
> define service{
> use generic-service
> host_name jmooo
> service_description check_disk1
> is_volatile 0
> check_period 24x7
> max_check_attempts 3
> normal_check_interval 5
> retry_check_interval 1
> contact_groups staff
> notification_interval 120
> notification_period 24x7
> notification_options w,u,c,r
> check_command check_nrpe!check_disk1
> }
> ############the nrpe addition to xinetd.d/ on the test client
> # default: off
> # description: NRPE (Nagios Remote Plugin Executor)
> service nrpe
> {
> flags = REUSE
> type = UNLISTED
> port = 5666
> socket_type = stream
> wait = no
> user = nagios
> group = nagios
> server = /usr/sbin/nrpe
> server_args = -c /etc/nagios/nrpe.cfg --inetd
> log_on_failure += USERID
> disable = no
> only_from = 192.168.3.2
> }
>
> #########################the client nrpe.cfg on the test client
> #############################################################################
>
> # Sample NRPE Config File
> # Written by: Ethan Galstad (nagios at nagios.org)
> #
> # Last Modified: 03-05-2003
> #
> # 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
>
>
>
> # 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
>
>
>
> # 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
>
>
>
> # 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
>
>
>
> # 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/lib/nagios/plugins/check_users -w 5 -c 10
> command[check_load]=/usr/lib/nagios/plugins/check_load -w 15,10,5 -c
> 30,25,20
> command[check_disk1]=/usr/lib/nagios/plugins/check_disk -w 20 -c 10 -p
> /dev/hda1
> command[check_disk2]=/usr/lib/nagios/plugins/check_disk -w 20 -c 10 -p
> /dev/hdb1
> command[check_zombie_procs]=/usr/lib/nagios/plugins/check_procs -w 5 -c
> 10 -s Z
> command[check_total_procs]=/usr/lib/nagios/plugins/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/lib/nagios/plugins/check_users -w $ARG1$ -c
> $ARG2$
> #command[check_load]=/usr/lib/nagios/plugins/check_load -w $ARG1$ -c $ARG2$
> #command[check_disk]=/usr/lib/nagios/plugins/check_disk -w $ARG1$ -c
> $ARG2$ -p $ARG3$
> #command[check_procs]=/usr/lib/nagios/plugins/check_procs -w $ARG1$ -c
> $ARG2$ -s $ARG3$
>
> ###############all my nagios files have user nagios group nagios
>
>
>
>
> ------------------------------------------------------------------------
>
> Subject:
> [Nagios-users] CHECK_NRPE: Error receiving data from daemon help needed
> From:
> roadbox <roadbox at midsouth.rr.com>
> Date:
> Sat, 27 Nov 2004 18:14:57 -0600
> To:
> nagios <nagios-users at lists.sourceforge.net>
>
> To:
> nagios <nagios-users at lists.sourceforge.net>
>
>
> Hello Linux challenged here
> I've yet to successfully use the npre/check_nrpe tools, but I sure wont to
> I believe my problem is in the .cfg files...I 've enclosed them below...
>
> Could someone "correct them" and/or post a working example for me to
> adjust appropriate to my system
> ###by Mo===
> define service{
> name generic-service
> active_checks_enabled 1
> passive_checks_enabled 1
> parallelize_check 1
> obsess_over_service 1
> check_freshness 1
> notifications_enabled 1
> event_handler_enabled 1
> flap_detection_enabled 1
> process_perf_data 1
> retain_status_information 1
> retain_nonstatus_information 1
> register 0
> }
>
>
> ###service defination
> define service{
> use generic-service
> host_name jmooo
> service_description check_users
> is_volatile 0
> check_period 24x7
> max_check_attempts 3
> normal_check_interval 5
> retry_check_interval 1
> contact_groups staff
> notification_interval 120
> notification_period 24x7
> notification_options w,u,c,r
> check_command check_nrpe!check_users
> }
>
>
> ###service defination
> ###service defination
> define service{
> use generic-service
> host_name jmooo
> service_description check_disk1
> is_volatile 0
> check_period 24x7
> max_check_attempts 3
> normal_check_interval 5
> retry_check_interval 1
> contact_groups staff
> notification_interval 120
> notification_period 24x7
> notification_options w,u,c,r
> check_command check_nrpe!check_disk1
> }
> ############the nrpe addition to xinetd.d/ on the test client
> # default: off
> # description: NRPE (Nagios Remote Plugin Executor)
> service nrpe
> {
> flags = REUSE
> type = UNLISTED
> port = 5666
> socket_type = stream
> wait = no
> user = nagios
> group = nagios
> server = /usr/sbin/nrpe
> server_args = -c /etc/nagios/nrpe.cfg --inetd
> log_on_failure += USERID
> disable = no
> only_from = 192.168.3.2
> }
>
> #########################the client nrpe.cfg on the test client
> #############################################################################
>
> # Sample NRPE Config File
> # Written by: Ethan Galstad (nagios at nagios.org)
> #
> # Last Modified: 03-05-2003
> #
> # 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
>
>
>
> # 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
>
>
>
> # 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
>
>
>
> # 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
>
>
>
> # 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/lib/nagios/plugins/check_users -w 5 -c 10
> command[check_load]=/usr/lib/nagios/plugins/check_load -w 15,10,5 -c
> 30,25,20
> command[check_disk1]=/usr/lib/nagios/plugins/check_disk -w 20 -c 10 -p
> /dev/hda1
> command[check_disk2]=/usr/lib/nagios/plugins/check_disk -w 20 -c 10 -p
> /dev/hdb1
> command[check_zombie_procs]=/usr/lib/nagios/plugins/check_procs -w 5 -c
> 10 -s Z
> command[check_total_procs]=/usr/lib/nagios/plugins/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/lib/nagios/plugins/check_users -w $ARG1$ -c
> $ARG2$
> #command[check_load]=/usr/lib/nagios/plugins/check_load -w $ARG1$ -c $ARG2$
> #command[check_disk]=/usr/lib/nagios/plugins/check_disk -w $ARG1$ -c
> $ARG2$ -p $ARG3$
> #command[check_procs]=/usr/lib/nagios/plugins/check_procs -w $ARG1$ -c
> $ARG2$ -s $ARG3$
>
> ###############all my nagios files have user nagios group nagios
>
>
>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
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