[squid-users] Problems with squid 3.1 to 3.3 upgrade

Alex Rousskov rousskov at measurement-factory.com
Fri Aug 9 18:37:30 UTC 2019

On 8/9/19 1:37 PM, Tom Karches wrote:
> On Fri, Aug 9, 2019 at 11:38 AM Alex Rousskov wrote:

> Ok, here is the info from the real trace. First time with #dns_v4_first
> onĀ  commented out, 2nd time "dns_v4_ first on" is active. Difference is
> with no "dns_v4_first on" directive, I get a RR_CONNECT_FAIL 111. When
> active, I get a RR_CONNECT_FAIL 101. 

BTW, it may be easier for you to read --trace--ascii output.

Both are ERR_CONNECT_FAIL errors ("connection reset by peer" and
"connection refused"). Your Squid cannot connect to where it needs to
connect in order to establish a TCP tunnel. It could be a Squid
misconfiguration, a routing problem, insufficient capabilities, and many
other things.

I suggest checking cache.log for WARNINGs and ERRORs. After arriving at
a clean cache.log, I would use a packet capture (or similar) to see
where Squid is trying to connect (and which local address it is
connecting from). That information may be enough to figure out why Squid
cannot connect successfully.


More information about the squid-users mailing list