nrpe timesout!
alexus
alexus at gmail.com
Wed Nov 7 06:27:15 CET 2007
i understand that, all of those are enabled as before i switched to
nagios3 and trying to reconfigure everything from scratch it seems to
be working fine in nagios2 (using same settings from nagios2 to
nagios3) with nrpe, so i've dealt with nrpe and it has been working in
the past
On Nov 2, 2007 4:31 AM, Hari Sekhon <hpsekhon at googlemail.com> wrote:
> alexus wrote:
> > i assume instead of check_http -a 10.10.10.34 you mean whatever is in
> > nrpe.cfg for check_http command, so i'm showing you whats in there and
> > i'm trying to execute that command and it works fine, but not through
> > nrpe...
> >
> > # grep check_http ~nagios/etc/nrpe.cfg
> > command[check_http]=/usr/local/nagios/libexec/check_http -I $ARG1$ -e 200
> > # /usr/local/nagios/libexec/check_http -I 10.10.10.34 -e 200
> > HTTP OK HTTP/1.1 200 OK - 299 bytes in 0.002 seconds
> > |time=0.002095s;;;0.000000 size=299B;;;0
> > #
> 2 things:
>
> 1. Are you running this as root? The # at the beginning of the line
> suggests so. Try running it as the user account that nrpe runs as.
>
> 2. You are passing args through nrpe, this is not good practice. It also
> will not work unless you have dont_blame_nrpe=1 in your nrpe.cfg on the
> remote host against which you are executing the nrpe call. I would
> recommend not passing args but instead defining more check_commands with
> the args already in them, this is more secure as it is more tightly
> controlled.
>
> -h
>
--
http://alexus.org/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.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