This basically means the connection was closed by the client before pound was able to send the info back. Did you try running your test by calling pound, instead of backend?

"Connection timed out" message is caused by a timeout on the read by pound from client. You can increase "Client" value in the pound.cfg

Dennis Jacobfeuerborn wrote:

Hi,
I'm running pound 2.2.5 on a debian machine I see sporadic errors in the logfile like this:

Feb 27 22:34:35 localhost pound: error flush headers to 82.83.69.159: Connection reset by peer
Feb 27 22:38:17 localhost pound: error copy chunk cont: Connection reset by peer
Feb 27 22:42:16 localhost pound: error flush headers to 213.139.142.142: Connection reset by peer
Feb 27 22:45:16 localhost pound: error copy server cont: Connection reset by peer
Feb 27 22:45:33 localhost pound: error read from 87.165.223.40: Connection reset by peer
Feb 27 22:48:45 localhost pound: error copy server cont: Connection reset by peer
Feb 27 22:51:55 localhost pound: error copy server cont: Connection reset by peer
Feb 27 22:53:28 localhost pound: error copy server cont: Connection reset by peer
Feb 27 22:53:43 localhost pound: error copy server cont: Connection reset by peer
Feb 27 22:54:26 localhost pound: error read from 84.56.116.218: Connection timed out

The real problem are the "connection reset by peer" errors as they result in an "internal server error" message on the client. The setup is fairly trivial with a simple HTTP listener that forwards request to a single backend server. I've written a little test script that runs on the pound server and repeatedly retrieves pages from the backend and that works flawlessly so it looks like this could be a bug in pound. What would be the best way to diagnose this problem further?

Regards,
Dennis