Thanks Simon and Robert for the feedback (suspicion about Chrome and that it's 
not fatal).

I'm a bit confused though, if a client makes a specific request (e.g. save 
data) 
and it fails why would that just be annoying?  I assume if Chrome is warming up 
connections would not call a specific URI.  Is this timeout waiting for the 
client to respond, or?

Steve


________________________________
From: Robert Segall <[email protected]>
To: [email protected]
Sent: Thu, March 17, 2011 10:46:47 AM
Subject: Re: [Pound Mailing List] e500 errors within a generally well running 
environment

On Mon, 2011-03-14 at 12:07 -0700, North Rock wrote:
> We have a fairly busy web service, we do notice steady reports of e500 
> errors. 

>  They might relate to some trouble reports we get occasionally.  Is there any 
> advice on how to trouble-shoot this further?  Is there any chance pound will 
> think the web server is dead and deny requests for a few seconds until it 
> sees 

> requests are processing there?
> 
> Mar 14 17:52:21 {server} pound: (7fb20c069910) e500 error copy client cont to 
> 172.23.100.39:8348/POST {uri} HTTP/1.1: Connection timed out (10.010 sec)
> Mar 14 18:16:57 {server} pound: (7fb1ff4d3910) e500 error copy client cont to 
> 127.0.0.1:8348/POST {uri} HTTP/1.1: Connection timed out (10.010 sec)
> Mar 14 18:18:07 {server} pound: (7fb1fd822910) e500 error copy client cont to 
> 127.0.0.1:8348/POST {uri} HTTP/1.1: Connection timed out (10.005 sec)
> Mar 14 18:36:19 {server} pound: (7fb1fdebc910) e500 error copy client cont to 
> 127.0.0.1:8348/POST {uri} HTTP/1.1: Connection timed out (10.006 sec)
> 
> Thank you.

It's annoying, but harmless. If it really bothers you try increasing the
client time-out.
-- 
Robert Segall
Apsis GmbH
Postfach, Uetikon am See, CH-8707
Tel: +41-32-512 30 19


--
To unsubscribe send an email with subject unsubscribe to [email protected].
Please contact [email protected] for questions.



      

--
To unsubscribe send an email with subject unsubscribe to [email protected].
Please contact [email protected] for questions.

Reply via email to