check_http succeeds on command line but fails in nagios

[Marc Powell]

Plugins should have a timeout option in order to terminate themselves if
they run to long and to prevent process build up. Nagios's timeout is
there in the event the plugin doesn't terminate itself.

Both are adjustable to your needs but the nagios timeout should be
greater than the longest plugin timeout you specify.

--
Marc

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Gary Danko
> Sent: Friday, September 16, 2005 4:36 PM
> To: nagios-users at lists.sourceforge.net
> Subject: Re: [Nagios-users] check_http succeeds on command line but
fails
> in nagios
> 
> Then what is the purpose of the "-t" switch in check_http?
> 
> On 9/16/05, Andrew Cruse <andrew at profitability.net> wrote:
> > nagios-users-admin at lists.sourceforge.net wrote:
> > > I have a simple PHP page that checks about 1,200 Windows
> > > shares across a network. The page takes about 80-90 seconds
> > > to run in a browser.
> >
> > Nagios typically only waits about 10 seconds for a plugin to return
> > information.  Any longer and it just times out.
> >
> > The workaround here would be to have a cron job that runs at
whatever
> > interval you're using in your check and grabs the output from that
page
> > and publishes it at another URL.  Then just run your check_http
command
> > against the second URL.



-------------------------------------------------------
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
_______________________________________________
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