[Nagiosplug-help] NRPE dies immediately

[Justin Shore]

As root

netstat -apn | grep :5666

That will tell you what process is already listening on tcp/5666.

Justin

> -----Original Message-----
> From: nagiosplug-help-admin at lists.sourceforge.net [mailto:nagiosplug-help-
> admin at lists.sourceforge.net] On Behalf Of nagios.list
> Sent: Thursday, September 15, 2005 3:23 PM
> To: Garrett Honeycutt
> Cc: nagiosplug-help at lists.sourceforge.net
> Subject: Re: [Nagiosplug-help] NRPE dies immediately
> 
> On Thu, 2005-09-15 at 15:00 -0500, Garrett Honeycutt wrote:
> > On Thu, 2005-09-15 at 14:47 -0500, nagios.list wrote:
> > > I have NRPE installed on many servers working fine.  I have installed
> > > it, and the plugins on two servers where it simply dies.
> > >
> > > looking in /var/log/messages I see
> > >
> > > nrpe: nrpe startup succeeded
> > > nrpe[14872]: Network server bind failure (98: Address already in use)
> > >
> > >
> > > I'm not sure what to make of this error.  NRPE and the installed
> plugins
> > > are current, and everything have been setup the same as the working
> > > servers.  Of the two not working, one is red hat 9.0 & the other is
> red
> > > hat 7.3.
> > >
> > > could anyone put me on track as to how to fix this? or at least more
> > > info on this error.
> > >
> > >
> > > Wayne
> > >
> >
> >
> > Are you running nrpe from inetd or xinetd? Stop inetd or xinetd and
> > issue a 'killall nrpe' and make sure there are no nrpe processes, then
> > restart inetd/xinetd. Posting your nrpe.cfg would not hurt either. Let
> > me know what you find.
> >
> > Cheers,
> > -g
> >
> Did as you said with same result
> put the nrpe.cfg to push debuging to the log file and got this
> 
> nrpe[22495]: INFO: SSL/TLS initialized. All network traffic will be
> encrypted.
> nrpe: nrpe startup succeeded
> nrpe[22496]: Network server bind failure (98: Address already in use)
> 
> not much help
> Running it from xinetd
> 
> # 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       = 216.23.216.20 192.168.1.115
> 
> }
> 
> 
> 
> nrpg.cfg
> 
> # 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=216.23.216.20,192.168.1.115
> 
> 
> 
> # 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=1
> 
> 
> 
> # DEBUGGING OPTION
> # This option determines whether or not debugging messages are logged to
> the
> # syslog facility.
> # Values: 0=debugging off, 1=debugging on
> 
> debug=1
> 
> 
> 
> # 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/hda6
> command[check_disk2]=/usr/lib/nagios/plugins/check_disk -w 20 -c 10
> -p /dev/hda1
> 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$
> 
> 
> 
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App Server.
> Download it for free - -and be entered to win a 42" plasma tv or your very
> own Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
> _______________________________________________
> Nagiosplug-help mailing list
> Nagiosplug-help at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagiosplug-help
> ::: Please include plugins version (-v) and OS when reporting any issue.
> ::: Messages without supporting info will risk being sent to /dev/null
> 
> --
> No virus found in this incoming message.
> Checked by AVG Anti-Virus.
> Version: 7.0.344 / Virus Database: 267.10.25/102 - Release Date: 9/14/2005
> 

-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.10.25/102 - Release Date: 9/14/2005