[squid-users] SQUID 3.1.20 TunnelStateData::Connection::error read/write failure: (32) Broken pipe

[LANGLOIS Nicolas]

Hi, im using squid On a debian server as simple proxy/cache and sometimes some clients get a connection error, i can't reproduce the problem and don' t really know where it can come from

Here is a Squid cache.log output :

2014/12/04 14:46:14| TunnelStateData::Connection::error: FD 232: read/write failure: (32) Broken pipe
2014/12/04 15:09:13| TunnelStateData::Connection::error: FD 285: read/write failure: (32) Broken pipe

Anyone has an idea or at least know what it mean ?


Nicolas

[Amos Jeffries]

Post by LANGLOIS Nicolas
Hi, im using squid On a debian server as simple proxy/cache and
sometimes some clients get a connection error, i can't reproduce
the problem and don' t really know where it can come from
read/write failure: (32) Broken pipe 2014/12/04 15:09:13|
(32) Broken pipe
Anyone has an idea or at least know what it mean ?

It means either the client or server attached to that tunnel
disconnected while there was still traffic flowing. Nothing Squid can
do about it.

PS. You should try to upgrade your Squid. Debian is currently shipping
3.3.8 (in Wheezy/stable) and 3.4.8 (in Jesse/testing) versions. The
latest will give you IP:port to further investigate if its not
resolved by the upgrade.

Amos