[squid-users] Squid 5.2 Peer parent TCP connection to x.x.x.x/x failed

[David Touzeau]

Hello Community,

We use child Squid proxies that connect to boxes that act as parents.
In version 4.x this configuration does not pose any problem.
In version 5.2, since, we have a lot of errors like :

01h 47mn kid1| TCP connection to 10.32.0.18/3150 failed
01h 47mn kid1| TCP connection to 10.32.0.17/3150 failed
01h 47mn kid1| TCP connection to 10.32.0.17/3150 failed
01h 47mn kid1| TCP connection to 10.32.0.17/3150 failed
01h 47mn kid1| TCP connection to 10.32.0.17/3150 failed
01h 47mn kid1| TCP connection to 10.32.0.17/3150 failed
01h 47mn kid1| TCP connection to 10.32.0.17/3150 failed

However we are sure that the parent proxies are available.
To make sure this is the case, we installed a local HaProxy that scales 
with the parent proxies

The Squid uses the loopback as a parent.

The same problem occurs:
06:19:47 kid1| TCP connection to 127.0.0.1/2320 failed
06:15:13 kid1| TCP connection to 127.0.0.1/2320 failed
06:14:41 kid1| TCP connection to 127.0.0.1/2320 failed
06:14:38 kid1| TCP connection to 127.0.0.1/2320 failed
06:13:15 kid1| TCP connection to 127.0.0.1/2320 failed
06:11:23 kid1| TCP connection to 127.0.0.1/2320 failed

But in no case the local HaProxy service was down

This makes us understand that the parent squid process randomly stalls 
when in fact there is no reason for this to happen.
There is a software problem rather than a network problem

It is possible that the configuration is wrong but we have tried many 
possibilities.

Here is our last configuration

cache_peer 127.0.0.1 parent 2320 0 name=Peer11 no-query default 
connect-timeout=3 connect-fail-limit=5 no-tproxy

maybe we forgot something?

Regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20211101/d9561a8b/attachment.htm>