I, too, am getting customer complaints of error 500s.  With a customer on the phone and looking at the logs in real time, I saw the error 500 happening at just the same time that pound emitted an error.  And, pound is emitting errors every few minutes.  I've copied a recent sample below.  This makes pound seem buggy. From past posts, I seem to recall that some of these are just warnings that need no modification of the pound config at all.  If so, I'd like to turn these warning messages off.  But, for the rest, what should I do.  I've also copied my simple config file below.
 
Thanks,
Steve Amerige
Fat Bear Incorporated
 
System: Red Hat Linux 9.0 (also on Fedora Core 1 and Fedora Core 4 with the same problems)
Pound version: 2.0.4
 
pound.cfg
 
LogLevel            0
User                "safeuser"
Group               "safegroup"
 
ListenHTTP
    Address         64.242.84.187
    Port            80
End
 
ListenHTTPS
    Address         64.242.84.187
    Port            443
    Cert            "/usr/local/apache2/conf/ssl/fatbear.com/fatbear.com.pem"
End
 
Service
    BackEnd
        Address     64.242.84.187
        Port        8088
    End
End
 
 
/var/log/messages
 
Aug  1 07:53:11 fat1 pound: error copy server cont: Connection timed out
Aug  1 07:53:55 fat1 pound: error copy server cont: Connection reset by peer
Aug  1 07:53:55 fat1 pound: error flush headers to 86.209.26.127: Connection reset by peer
Aug  1 07:54:06 fat1 pound: error copy server cont: Connection timed out
Aug  1 07:54:22 fat1 pound: error copy server cont: Connection reset by peer
Aug  1 07:56:17 fat1 pound: error copy server cont: Connection timed out
Aug  1 07:58:38 fat1 pound: error copy server cont: Connection reset by peer
Aug  1 08:00:24 fat1 pound: error copy server cont: Connection reset by peer
Aug  1 08:03:29 fat1 pound: error copy server cont: Connection reset by peer
Aug  1 08:04:03 fat1 pound: error copy server cont: Connection reset by peer
Aug  1 08:05:15 fat1 pound: error copy server cont: Connection reset by peer
Aug  1 08:05:46 fat1 pound: error flush headers to 68.79.159.2: Connection reset by peer
Aug  1 08:05:48 fat1 pound: error copy server cont: Connection reset by peer
Aug  1 08:05:51 fat1 pound: error flush headers to 68.79.159.2: Connection reset by peer
Aug  1 08:05:51 fat1 pound: error flush headers to 68.79.159.2: Connection reset by peer
Aug  1 08:05:51 fat1 pound: error copy server cont: Connection reset by peer
Aug  1 08:06:45 fat1 pound: error flush headers to 68.79.159.2: Connection reset by peer
Aug  1 08:07:01 fat1 pound: error copy server cont: Connection reset by peer
Aug  1 08:07:49 fat1 pound: error copy server cont: Connection reset by peer
Aug  1 08:08:05 fat1 pound: error copy server cont: Connection timed out
Aug  1 08:08:06 fat1 pound: error flush headers to 68.79.159.2: Connection reset by peer
Aug  1 08:08:08 fat1 pound: error copy server cont: Connection reset by peer
Aug  1 08:08:49 fat1 pound: error copy server cont: Connection reset by peer
Aug  1 08:09:00 fat1 pound: error flush headers to 71.139.184.220: Connection reset by peer
Aug  1 08:09:17 fat1 pound: response error read from 64.242.84.187:8088: Connection timed out
Aug  1 08:09:52 fat1 pound: error copy server cont: Connection reset by peer
Aug  1 08:09:54 fat1 pound: error copy server cont: Connection reset by peer
Aug  1 08:10:34 fat1 pound: error copy server cont: Connection reset by peer
Aug  1 08:10:38 fat1 pound: error copy server cont: Connection timed out
Aug  1 08:12:57 fat1 pound: error copy server cont: Connection timed out
Aug  1 08:13:29 fat1 pound: error copy server cont: Connection reset by peer
Aug  1 08:13:32 fat1 pound: error copy server cont: Connection reset by peer
Aug  1 08:15:22 fat1 pound: error copy chunk cont: Connection reset by peer
Aug  1 08:15:25 fat1 pound: error flush headers to 128.218.39.136: Connection reset by peer
Aug  1 08:15:25 fat1 pound: error flush headers to 128.218.39.136: Connection reset by peer
Aug  1 08:15:30 fat1 pound: error copy chunk cont: Connection reset by peer
Aug  1 08:17:36 fat1 pound: error flush headers to 81.231.98.56: Connection reset by peer
Aug  1 08:18:18 fat1 pound: can't read header
Aug  1 08:18:32 fat1 pound: error copy chunk cont: Connection reset by peer
Aug  1 08:18:38 fat1 pound: error copy server cont: Connection reset by peer
Aug  1 08:18:59 fat1 pound: error flush headers to 212.219.238.55: Connection reset by peer
Aug  1 08:19:03 fat1 pound: error read from 220.179.77.169: Connection timed out
Aug  1 08:19:12 fat1 pound: error copy server cont: Connection reset by peer
Aug  1 08:19:13 fat1 pound: error flush headers to 81.231.98.56: Connection reset by peer
Aug  1 08:19:49 fat1 pound: error read from 68.254.149.123: Connection reset by peer
Aug  1 08:19:49 fat1 pound: error copy server cont: Connection reset by peer
Aug  1 08:19:49 fat1 pound: error flush headers to 68.254.149.123: Connection reset by peer
Aug  1 08:21:07 fat1 pound: error copy server cont: Connection reset by peer
Aug  1 08:23:18 fat1 pound: error copy server cont: Connection reset by peer
Aug  1 08:24:57 fat1 pound: error copy server cont: Connection reset by peer
Aug  1 08:25:05 fat1 pound: error copy server cont: Connection timed out
Aug  1 08:25:06 fat1 pound: error copy server cont: Connection reset by peer
Aug  1 08:25:09 fat1 pound: error flush headers to 24.143.15.102: Connection reset by peer
Aug  1 08:26:55 fat1 pound: error copy server cont: Connection timed out
Aug  1 08:28:58 fat1 pound: error copy server cont: Connection reset by peer
Aug  1 08:29:06 fat1 pound: error copy server cont: Connection reset by peer
Aug  1 08:29:27 fat1 pound: error copy server cont: Connection reset by peer
Aug  1 08:29:35 fat1 pound: error copy server cont: Connection timed out
Aug  1 08:29:47 fat1 pound: error copy server cont: Connection reset by peer
Aug  1 08:32:29 fat1 pound: error copy server cont: Connection timed out
----- Original Message -----
From: Ondra Kudlik
To: Pound
Sent: Tuesday, August 01, 2006 2:57 PM
Subject: [Pound Mailing List] Timeout problems

Hi,

two days ago we switched to Pound 2.0.9 from 1.8 and now we have
problem with timeouts.

We have apache behind pound and when some client have script which
take long time it returns error 500 and in logs there is

response error read from 127.0.0.1:10000: Connection timed out

I found TimeOut in documentation so I add it to BackEnd end yes, it
is better.. but how I can set ideal value for TimeOut? What if
script take 3 minutes to go or 5 minutes or 30 seconds? I'm not
really sure but I think that with Pound 1.8 there wasn't this
problem.

Can you give me some advice?

Thanks

--
 .''`. Ondra 'Kepi' Kudlik
: :' : Debian GNU/Linux User
`. `'
  `-   http://www.nosoftwarepatents.com/cz/m/intro/index.html


--
To unsubscribe send an email with subject 'unsubscribe' to pound@apsis.ch.
Please contact roseg@apsis.ch for questions.
http://www.apsis.ch/pound/pound_list/archive/2006/2006-08/1154428070000