[squid-users] 3.5.5 https problem
Amos Jeffries
squid3 at treenet.co.nz
Wed Jun 3 06:01:33 UTC 2015
On 3/06/2015 5:06 p.m., Dmitry Melekhov wrote:
> Hello!
>
> Just tried to install 3.5.5 on production proxy, users complained about
> slow https connections,
> I see errors in cache.log like
> 2015/06/03 09:00:34 kid1| local=192.168.42.130:32922
> remote=213.180.193.119:443 FD 964 flags=1: read/write failure: (32)
> Broken pipe
> 2015/06/03 09:00:46 kid1| local=192.168.42.130:52239
> remote=178.154.131.216:443 FD 1111 flags=1: read/write failure: (32)
> Broken pipe
> 2015/06/03 09:01:56 kid1| local=192.168.42.130:34841
> remote=213.180.193.119:443 FD 467 flags=1: read/write failure: (32)
> Broken pipe
>
> Switching back to 3.4.13 solved problem, but..
> Any ideas what can cause this ?
It is a socket being closed from the other end. The closure signal
arrives while Squid is trying to write to it.
Could be bug 3329 causing Squid confusion though.
NP: The patch for that bug is now in Squid-4 (trunk / HEAD / dev /
"pre-beta") and will be backported to 3.5 when its had some time to
settle, feedback from testing will speed that up if you can and wish to
assist.
Amos
More information about the squid-users
mailing list