CRITICAL - Socket timeout after 10 seconds

[Giles Coochey]

On 02/02/2011 12:12, akp geek wrote:
> Now I have increased the timeout to 60 seconds. Now I am getting
>
> node name or service name not known
> HTTP CRITICAL - Unable to open TCP socket
>
> Thanks for the suggestions
>
> Regards
>
>
> On Tue, Feb 1, 2011 at 7:49 PM, steve f <a31modela at hotmail.com 
> <mailto:a31modela at hotmail.com>> wrote:
>
>      Most plugins time out after 10 seconds of not being able to
>     contact a service (FTP, HTTP, etc). If the plugins are timing out
>     after a short period of time, increase the timeout value for the
>     plugin using the appropriate command line argument for that
>     plugin. Try using a -t 12.
>
>     I think that only the plugin timeout default value is 10 seconds,
>     the other timeouts are higher.  Someone else smarter than me can
>     verify that.
>
>     Is this check_http failing every time now or only occasionally ? 
>     Try running the check to a different site and see if those fail as
>     well.
>
>     Is the server possibly busy at the same time??
>
>     Let us know what you find out.
>
>     Steve
>
>     ------------------------------------------------------------------------
>     Date: Tue, 1 Feb 2011 18:30:55 -0500
>     From: akpgeek at gmail.com <mailto:akpgeek at gmail.com>
>     To: nagios-users at lists.sourceforge.net
>     <mailto:nagios-users at lists.sourceforge.net>
>     Subject: [Nagios-users] CRITICAL - Socket timeout after 10 seconds
>
>
>     Hi all -
>
>                I have been using nagios for a while to check whether
>     some our web sites are  up and running
>
>     following is the line from the commands.cfg
>
>     *command_line $USER1$/check_http -w 5 -c 10  -H our_dns_name -u
>     /siteName -S -v*
>
>
>     It was working fine. Starting this afternoon, it started giving
>     Socket time out. Logs have no information. Can you please share
>     your experiences ?
>
>
>     Regards
>
>
Have you tried speaking with the administrators of the web servers? I 
remember once I was running some web-server analytic on one of my 
webservers and I found lots of spurious connections from a particular 
host... I assumed it was a lame DoS attack and simply put in a iptables 
command to block any incoming traffic from that IP. All the requests 
were silly and every 30 seconds or so.
Soon after I got a call from our NOC asking me if I could take a look at 
the webserver as it seemed to be down... of course, they never told me 
that they were monitoring it for uptime... nor did they actually check 
the webserver on a different client system...  I guessed the company I 
was working for was actually more interested in seeing whether I was 
meeting a SLA rather than properly communicating their monitoring systems...
But either way, if the web admin has blocked you then I imagine you'd 
get that error...

-- 
Best Regards,

Giles Coochey
NetSecSpec Ltd
NL T-Systems Mobile: +31 681 265 086
NL Mobile: +31 626 508 131
GIB Mobile: +350 5401 6693
Email/MSN/Live Messenger: giles at coochey.net
Skype: gilescoochey



-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5137 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://www.monitoring-lists.org/archive/users/attachments/20110202/a6e6e5ea/attachment.bin>
-------------- next part --------------
------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d
-------------- next part --------------
_______________________________________________
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