On 19/06/11 22:39, Jenny Lee wrote:
Hello Squid Team,
Thank you for much awaited 3.2.0.9 release. This one seem to have one major issue:
1) Peers are not honored. All connections going direct. I tried everything possible but of no use. Can someone verify?
There was a major change in the peer selection algorithm to make it work
with tcp_outgoing_address across multiple address families.
I'm adding some debug now so we can view the selections and see what is
going on a bit better.
The patch is here:
http://www.squid-cache.org/Versions/v3/3.HEAD/changesets/squid-3-11506.patch
Others:
2) assertion failed: mem.cc:190: "MemPools[type] == NULL"
3) What does this mean?
2011/06/19 14:16:14 kid1| Failure Ratio at 1.008
2011/06/19 14:16:14 kid1| Going into hit-only-mode for 5 minutes...
More DIRECT requests are failing due to TCP connect or DNS lookup errors
than are succeeding.
Probably a side effect of (1) above.
4) --disable-ipv6 still not honored. need to use "USE_IPV6 0" to disable.
Okay. Found this one. Sorry for being so dense earlier. I was looking at
the logic rather than the variable name :(
BTW: would you mind trialling with IPv6 enabled now? This version is
supposed to resolve all the edge cases previous releases had.
The only issues I'm expecting to be still relevant are:
* servers not responding to IPv6 TCP packets (ECN and PMTUD issues).
* DNS resolvers not responding to AAAA lookups.
5) forward.cc has "Forwarding client request..." line at debug 17,1 which seems to create a cache.log as big as the access.log!
Thank you. That should have been 17,2.
Just the debug tracer for when a request is about to be forwarded on
somewhere.
This is with a drop-in 3.2.0.8 config file at a cursory glance. I will go throught the options to see if anything changed and if these are my wrongdoings.
Jenny
Amos
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.12
Beta testers wanted for 3.2.0.8 and 3.1.12.2
