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.

On Tue, Mar 15, 2011 at 6:07 AM, North Rock <northrock007(at)yahoo.com>
wrote:[...]

I think that's Chrome. I see the same thing.

http://www.apsis.ch/pound/pound_list/archive/2010/2010-12/1291594925000

I brought it up on another list, and the reasoning seems sound.

http://www.varnish-cache.org/lists/pipermail/varnish-misc/2011-March/005834.html
[...]

On Mon, 2011-03-14 at 12:07 -0700, North Rock wrote:[...]

It's annoying, but harmless. If it really bothers you try increasing the
client time-out.[...]

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

[...]