Hello,

I have just witnessed a Pound read error. The Chrome (8.0.552.215)
user was being redirected to a HTTPS page.

Client Error: Error 101 (net::ERR_CONNECTION_RESET): Unknown error.
Server Error: Dec  6 10:23:21 host pound: (b7a9eb90) error read from
x.x.x.x: Connection timed out

I see this error 76 times across eight servers. Pound is solely used
for HTTPS which backs onto a Varnish server.

Configuration:
ListenHTTPS
	Address 0.0.0.0
	Port	443
	Cert "/etc/ssl/private/cert.pem"

	AddHeader "X-Forwarded-Proto: https"
	HeadRemove "X-Forwarded-Proto"

	Service
		BackEnd
			Address 127.0.0.1
			Port 80
		End
	End
End

Pound 2.4.3 (RPMForge)
CentOS 5


I have just noticed the EPEL repository has Pound 2.4.4, which I've
installed on a testing server. Switching between then doesn't seem to
be an issue though will it resolve the above issue? Below is the 2.4.4
changelog:

Bug fixes:
    - save and restore errno value in cur_time() (thanks to Albert)
    - fixed problem in timer thread (thanks to Albert)
    - added shutdown for failed socket connection (thanks to Albert)
    - fixed problem with CC containing spaces in Makefile.in (thanks
to Elan Ruusamäe)
    - increased MAXBUF to default 4096
    - increased T_RSA default to 30 minutes
    - fixed a problem with Unix sockets back-ends (thanks to Ricardo Gameiro)

Thanks.

-- 
Simon Males

On Mon, Dec 6, 2010 at 11:22 AM, Simon Males <sime(at)sime.net.au> wrote:
> Hello,
>
> I have just witnessed a Pound read error. The Chrome (8.0.552.215)
> user was being redirected to a HTTPS page.
>
> Client Error: Error 101 (net::ERR_CONNECTION_RESET): Unknown error.
> Server Error: Dec  6 10:23:21 host pound: (b7a9eb90) error read from
> x.x.x.x: Connection timed out

I am testing Pound 2.4.4 and managed to get another error from Chrome.

Client : Error 324 (net::ERR_EMPTY_RESPONSE): Unknown error.
Server: Dec  8 10:11:26 host pound: (b7a16b90) error read from
x.x.x.x: Connection timed out

A second reload will render the page. It's almost like the pound isn't warm.

Though further digging has found more Chrome related errors.

Loading a static asset (e.g. an image) will successfully download in
Chrome, though 9-10 seconds later (like clockwork) this appears in
syslog:
Dec  8 12:25:54 host pound: (b79b0b90) error read from x.x.x.x:
Connection timed out

This was consistent on Mac and Linux clients. In tcpdump I can see
pound trying to communicate with the client again. The behavior here
was strictly Chrome specific.


-- 
Simon Males