NRPE on monitoring host

[Thomas Guyot-Sionnest]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 16/02/08 03:35 PM, Henrik Schou wrote:
> Hi all			
> 
> Thank you for your answers.
> 
> You say that I can install the nrpe conf file for xinetd.
> 
> As you state you belive I have already done that. Yes, I belive I have.. In /etc/xinetd.d/nrpe I have entered the following:
> 
> # default: on
> # description: NRPE (Nagios Remote Plugin Executor)
> service nrpe
> {
>         flags           = REUSE
>         socket_type     = stream
>         wait            = no
>         user            = nagios
>         server          = /usr/local/nagios/bin/nrpe -c
>         server_args     = /etc/local/nagios/etc/nrpe.cfg -d --inetd
>         log_on_failure  += USERID
>         disable         = no
>         only_from       = 192.168.0.0/24
> }
> 
> If I understand all of the comments I have received correct, it seems that I run nrpe in 2 instances, which I can't. How would I do it the right way then? I'd say I would prefer to run it through xinetd..

As Sean made me realize you were actually trying to run the xinetd
config file... In fact all you have to do it probably reload or restart
xinetc. (make sure to kill all instances of the NRPE daemon)


Thomas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHuGhc6dZ+Kt5BchYRAiMnAJ9YjFdi8kxJP4KDInwaBI4GPIUWRgCg9nbb
AOzCO0LmnKK81r4njbR5+0c=
=BMJx
-----END PGP SIGNATURE-----

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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