Hi All,

We are experiencing three different problems with Pound. They have all been
mentioned on this list before, but I wanted to share our experience and
research, and hopefully get some feedback. The problems are:

1. No content being returned from pound (not even headers.)
2. Error 500s for no apparent reason.
3. Garbled content (what appears to be two responses - one from some other
user/connection and your own response. This is the same problem Dennis Allison
is having.)

Looking in the logs we see the following:

When we get no response from the server, the following error occurs (where
x.x.x.x is the client IP and pound3 is the name of the pound server):

Sep 27 08:15:10 pound3 pound: error read from x.x.x.x: Input/output error

When we get the error 500 for no reason (static content) the following gets
logged (where 10.0.1.104 is one of our backends and pound3 is the name of the
pound server):

Sep 27 09:40:00 pound3 pound: response error read from 10.0.1.104:80: Success

We so far have not been able to track down any specific error message with
respect to the jumbled response.

This is a Mandrake 10.0 server (2.6.3 Kernel NPTL) running the latest
pound-current, at least it was the latest last Friday. This particular Pound
server gets between 12 and 15 hits per second and the errors seem to become
more frequent the more hits it gets.

I am going to start looking at the source to see if I can find anything. Any
insight or suggestion would be appreciated.

Thanks,

John D.

Hi again,

I have been doing more testing and I wanted to share the results. This test is
a shell script useing cUrl to conntect to the server (there is NO SSL in this
test). It gets the same static text file as quickly as it can and compairs what
it got to what it should have gotten. If cUrl gets something unexpected then
the script exits and prints the date. I then use this date to look in the Pound
log file to find the error. The script does NOT run for more then 10 minutes
before getting an error. In the results below x.x.x.x is the client IP; pound3
is the name of the pound server; and 10.0.1.??? is a backend.

-------------------------------------------------------
curl: (52) Empty reply from server
BAD!!! Mon Sep 27 10:23:11 PDT 2004
Sep 27 10:23:11 pound3 pound: error flush headers to x.x.x.x: Connection reset
by peer

curl: (52) Empty reply from server
BAD!!! Mon Sep 27 10:38:42 PDT 2004
Sep 27 10:38:42 pound3 pound: error flush headers to x.x.x.x: Connection reset
by peer

curl: (52) Empty reply from server
BAD!!! Mon Sep 27 10:40:27 PDT 2004
Sep 27 10:40:27 pound3 pound: response error read from 10.0.1.102:80: Success

Error 500
BAD!!! Mon Sep 27 10:45:10 PDT 2004
Sep 27 10:45:10 pound3 pound: response error read from 10.0.1.102:80: Bad file
descriptor

curl: (52) Empty reply from server
BAD!!! Mon Sep 27 11:13:27 PDT 2004
Sep 27 11:13:27 pound3 pound: error flush headers to x.x.x.x: Connection reset
by peer

curl: (52) Empty reply from server
BAD!!! Mon Sep 27 11:20:29 PDT 2004
Sep 27 11:20:29 pound3 pound: error flush headers to x.x.x.x: Connection reset
by peer

Error 500
User reported error Sep 27 11:28
Sep 27 11:28:16 pound3 pound: error copy chunk cont: Connection reset by peer

curl: (52) Empty reply from server
BAD!!! Mon Sep 27 11:29:49 PDT 2004
Sep 27 11:29:49 pound3 pound: bad request "HTTP/1.1 400 Bad Request" from
x.x.x.x

curl: (52) Empty reply from server
BAD!!! Mon Sep 27 11:37:23 PDT 2004
Sep 27 11:37:23 pound3 pound: error flush headers to x.x.x.x: Connection reset
by peer

curl: (52) Empty reply from server
BAD!!! Mon Sep 27 11:43:33 PDT 2004
Sep 27 11:43:33 pound3 pound: error flush headers to x.x.x.x: Connection reset
by peer

curl: (52) Empty reply from server
BAD!!! Mon Sep 27 11:54:44 PDT 2004
Sep 27 11:54:44 pound3 pound: error flush headers to x.x.x.x: Connection reset
by peer
------------------------------------------------------

Off hand, I would say there is a problem. We weren't having any problems before
we moved these server behind Pound.

John D.

********** Original Email *********
** To:   pound(at)apsis.ch
** From: "John D" <jwdavid(at)ibizvision.com>
** Date: Mon, 27 Sep 2004 10:14:05
**********

Hi All,

We are experiencing three different problems with Pound. They have all been
mentioned on this list before, but I wanted to share our experience and
research, and hopefully get some feedback. The problems are:

1. No content being returned from pound (not even headers.)
2. Error 500s for no apparent reason.
3. Garbled content (what appears to be two responses - one from some other
user/connection and your own response. This is the same problem Dennis Allison
is having.)

Looking in the logs we see the following:

When we get no response from the server, the following error occurs (where
x.x.x.x is the client IP and pound3 is the name of the pound server):

Sep 27 08:15:10 pound3 pound: error read from x.x.x.x: Input/output error

When we get the error 500 for no reason (static content) the following gets
logged (where 10.0.1.104 is one of our backends and pound3 is the name of the
pound server):

Sep 27 09:40:00 pound3 pound: response error read from 10.0.1.104:80: Success

We so far have not been able to track down any specific error message with
respect to the jumbled response.

This is a Mandrake 10.0 server (2.6.3 Kernel NPTL) running the latest
pound-current, at least it was the latest last Friday. This particular Pound
server gets between 12 and 15 hits per second and the errors seem to become
more frequent the more hits it gets.

I am going to start looking at the source to see if I can find anything. Any
insight or suggestion would be appreciated.

Thanks,

John D.

Yea, these are the problems we're all having it seems.

For the record, I've tried downgrading to as low as 1.4, and the issue is
persistent. 
(e500's, content returned is from another session, etc.)

... John
[...]

Hi all,

I just wanted to update everyone on our findings. We have found a work around
to the problems!

After looking at the Pound source, the problem doesn't appear to have anything
to do with Pound's interaction with the Client. That got me thinking, maybe
there is something wrong with the way Pound re-uses backend connections (when
the backend supports HTTP 1.1). So we disabled HTTP 1.1 on the BackEnds (in
Apache we set KeepAlive to Off).

We are now seeing NO 500 errors, blank pages OR garbled content. So for us,
this works around the issue in Pound.

So, if you are seeing these problems give this a try. If it helps, let the list
know as this may assist Robert in isolating the problem.

John D.

********** Original Email *********
** To:   pound(at)apsis.ch
** From: "John D" <jwdavid(at)ibizvision.com>
** Date: Mon, 27 Sep 2004 12:06:38
**********

Hi again,

I have been doing more testing and I wanted to share the results. This test is
a shell script useing cUrl to conntect to the server (there is NO SSL in this
test). It gets the same static text file as quickly as it can and compairs what
it got to what it should have gotten. If cUrl gets something unexpected then
the script exits and prints the date. I then use this date to look in the Pound
log file to find the error. The script does NOT run for more then 10 minutes
before getting an error. In the results below x.x.x.x is the client IP; pound3
is the name of the pound server; and 10.0.1.??? is a backend.

-------------------------------------------------------
curl: (52) Empty reply from server
BAD!!! Mon Sep 27 10:23:11 PDT 2004
Sep 27 10:23:11 pound3 pound: error flush headers to x.x.x.x: Connection reset
by peer

curl: (52) Empty reply from server
BAD!!! Mon Sep 27 10:38:42 PDT 2004
Sep 27 10:38:42 pound3 pound: error flush headers to x.x.x.x: Connection reset
by peer

curl: (52) Empty reply from server
BAD!!! Mon Sep 27 10:40:27 PDT 2004
Sep 27 10:40:27 pound3 pound: response error read from 10.0.1.102:80: Success

Error 500
BAD!!! Mon Sep 27 10:45:10 PDT 2004
Sep 27 10:45:10 pound3 pound: response error read from 10.0.1.102:80: Bad file
descriptor

curl: (52) Empty reply from server
BAD!!! Mon Sep 27 11:13:27 PDT 2004
Sep 27 11:13:27 pound3 pound: error flush headers to x.x.x.x: Connection reset
by peer

curl: (52) Empty reply from server
BAD!!! Mon Sep 27 11:20:29 PDT 2004
Sep 27 11:20:29 pound3 pound: error flush headers to x.x.x.x: Connection reset
by peer

Error 500
User reported error Sep 27 11:28
Sep 27 11:28:16 pound3 pound: error copy chunk cont: Connection reset by peer

curl: (52) Empty reply from server
BAD!!! Mon Sep 27 11:29:49 PDT 2004
Sep 27 11:29:49 pound3 pound: bad request "HTTP/1.1 400 Bad Request" from
x.x.x.x

curl: (52) Empty reply from server
BAD!!! Mon Sep 27 11:37:23 PDT 2004
Sep 27 11:37:23 pound3 pound: error flush headers to x.x.x.x: Connection reset
by peer

curl: (52) Empty reply from server
BAD!!! Mon Sep 27 11:43:33 PDT 2004
Sep 27 11:43:33 pound3 pound: error flush headers to x.x.x.x: Connection reset
by peer

curl: (52) Empty reply from server
BAD!!! Mon Sep 27 11:54:44 PDT 2004
Sep 27 11:54:44 pound3 pound: error flush headers to x.x.x.x: Connection reset
by peer
------------------------------------------------------

Off hand, I would say there is a problem. We weren't having any problems before
we moved these server behind Pound.

John D.

********** Original Email *********
** To:   pound(at)apsis.ch
** From: "John D" <jwdavid(at)ibizvision.com>
** Date: Mon, 27 Sep 2004 10:14:05
**********

Hi All,

We are experiencing three different problems with Pound. They have all been
mentioned on this list before, but I wanted to share our experience and
research, and hopefully get some feedback. The problems are:

1. No content being returned from pound (not even headers.)
2. Error 500s for no apparent reason.
3. Garbled content (what appears to be two responses - one from some other
user/connection and your own response. This is the same problem Dennis Allison
is having.)

Looking in the logs we see the following:

When we get no response from the server, the following error occurs (where
x.x.x.x is the client IP and pound3 is the name of the pound server):

Sep 27 08:15:10 pound3 pound: error read from x.x.x.x: Input/output error

When we get the error 500 for no reason (static content) the following gets
logged (where 10.0.1.104 is one of our backends and pound3 is the name of the
pound server):

Sep 27 09:40:00 pound3 pound: response error read from 10.0.1.104:80: Success

We so far have not been able to track down any specific error message with
respect to the jumbled response.

This is a Mandrake 10.0 server (2.6.3 Kernel NPTL) running the latest
pound-current, at least it was the latest last Friday. This particular Pound
server gets between 12 and 15 hits per second and the errors seem to become
more frequent the more hits it gets.

I am going to start looking at the source to see if I can find anything. Any
insight or suggestion would be appreciated.

Thanks,

John D.