I’m running Pound 2.3 with 3 Apache 2.0 backends, it’s working well overall
from a human user point of view (opening a page on my site is fast, I never
notice any error). However we are using the backend also as web application
servers, and there is another server application (done in Java) that makes HTTP
calls to Pound to persist information using Apache/PHP scripts. About once a
day, sometime several times a day, we get an HTTP 500 error code in the calling
server’s log files. I can see those types of messages in /var/log/messages:
Apr 30 11:36:40 srv2 pound: error copy server cont: Connection timed out
Apr 30 11:36:40 srv2 pound: error copy server cont: Connection timed out
Apr 30 11:46:57 srv2 pound: error copy server cont: Connection reset by peer
Apr 30 12:08:03 srv2 last message repeated 7 times
Apr 30 12:18:54 srv2 last message repeated 5 times
Apr 30 12:25:43 srv2 last message repeated 2 times
Apr 30 12:25:45 srv2 pound: error copy server cont: Connection reset by peer
Apr 30 12:27:33 srv2 pound: error copy chunk cont: Connection reset by peer
Apr 30 12:42:56 srv2 pound: error copy server cont: Connection reset by peer
Apr 30 13:17:22 srv2 pound: error copy server cont: Connection timed out
Apr 30 13:17:44 srv2 pound: error copy chunk cont: Connection reset by peer
Apr 30 13:20:03 srv2 pound: error copy chunk cont: Connection timed out
Apr 30 13:39:05 srv2 pound: error copy server cont: Connection timed out
Apr 30 13:39:06 srv2 last message repeated 6 times
Apr 30 15:53:25 srv2 pound: error copy server cont: Connection reset by peer
Apr 30 16:09:26 srv2 pound: error copy chunk cont: Connection reset by peer
Apr 30 16:14:01 srv2 pound: error copy chunk cont: Connection timed out
Apr 30 16:29:52 srv2 pound: error copy server cont: Connection reset by peer
Apr 30 16:30:30 srv2 last message repeated 2 times
I’m not sure if they are related to the HTTP 500 error. On Apache server side,
there are no errors logged. It seems that the error is somewhere at Pound
level. My question/suggestion is to find a way to do some “smart logging”,
where we log the whole HTTP request and result ONLY when some pre-configured
error occurs (ex: LogConditionalError 500) which will simplify identifying the
true reasons of such errors.
Lei
Internal Virus Database is out-of-date.
Checked by AVG Free Edition.
Version: 7.5.463 / Virus Database: 269.5.10/774 - Release Date: 23/04/2007
17:26
Internal Virus Database is out-of-date.
Checked by AVG Free Edition.
Version: 7.5.463 / Virus Database: 269.5.10/774 - Release Date: 23/04/2007
17:26
Internal Virus Database is out-of-date.
Checked by AVG Free Edition.
Version: 7.5.463 / Virus Database: 269.5.10/774 - Release Date: 23/04/2007
17:26
|
