Check_http problem

[Srinivas Kotapally]

I fixed it!!  I had the firewall setup to drop outgoing http requests!

Thanks

Srini 

-----Original Message-----
From: Marc Powell [mailto:marc at ena.com] 
Sent: Tuesday, November 23, 2004 2:38 PM
To: Srinivas Kotapally; Nagios
Subject: RE: [Nagios-users] Check_http problem



> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users- 
> admin at lists.sourceforge.net] On Behalf Of Srinivas Kotapally
> Sent: Tuesday, November 23, 2004 12:58 PM
> To: Nagios
> Subject: [Nagios-users] Check_http problem
> 
> Hi All
> 
> I have just installed nagios on my servers.  I am getting a "Socket 
> timeout after 10 seconds" when I set check_http for a few of my 
> servers.
> 
> Can anyone help?  The port 80 is open on the server (it is a public 
> website).

Does it work from the command line as the nagios user? Does it take longer
than 10 seconds to complete when run from the command line? What does the
command definition, service definition and host definition look like? OS on
the Nagios server? Nagios and plugin versions? What have you already done to
troubleshoot? We have little to no useful information to help you at this
point other than it's taking longer than 10 seconds to run. Based on that I
would suggest you might want to increase the plugin timeout value (-t
parameter to check_http). The service_check_timeout value in nagios.cfg
should be at or more than your highest plugin timeout value as well.

--
Marc





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