Michael Bowe wrote:
I have a site with several squid servers setup as shown here
http://wiki.squid-cache.org/Features/Tproxy4
All the Tproxy functionality is working fine.
Now I would like to enable cache-peer sibling proxy-only to avoid
duplication of objects between each server's hard drive.
The servers sit in a dedicated subnet/vlan (router has "ip wccp redirect
exclude in" on this subinterface ).
If I enable cache_peer, I see that the ICP part works fine, but should
server A try to fetch a HIT from server B, the connection fails because the
source-ip is set to the client rather than server A.
I end up with this type of thing in the cache.log
2009/09/19 17:53:09| Detected DEAD Sibling: cache03.<snipped>
2009/09/19 17:53:09| Detected REVIVED Sibling: cache03.<snipped>
2009/09/19 17:53:11| TCP connection to cache03.<snipped>/8080 failed
2009/09/19 17:53:11| Detected DEAD Sibling: cache03.<snipped>
2009/09/19 17:53:11| Detected REVIVED Sibling: cache03.<snipped>
2009/09/19 17:53:16| TCP connection to cache03.<snipped>/8080 failed
2009/09/19 17:53:16| Detected DEAD Sibling: cache03.<snipped>
2009/09/19 17:53:16| Detected REVIVED Sibling: cache03.<snipped>
I guess we need to be able to disable the Tproxy functionality when talking
to local cache_peers ?
I see that Adrian Chadd made a patch for Squid v2
http://code.google.com/p/lusca-cache/issues/detail?id=48
Lusca is not Squid v2. It's a private branch of code Adrian is working
on. Based on the old Squid code.
Seems he made one for lusca but did not mention it to the Squid
developers. Not surprising since Squid v2 does not support TPROXYv4
anyway, thats one of the bits he added to lusca since branching.
I was wondering if there were any plans for such a feature to be added to
Squid v3.1?
This is the first I've heard of the problem. Thank you for pointing it
out along with the fix.
http://www.squid-cache.org/Versions/v3/HEAD/changesets/squid-3-10004.patch
Amos
--
Please be using
Current Stable Squid 2.7.STABLE7 or 3.0.STABLE19
Current Beta Squid 3.1.0.13
