Jon DeLee wrote:
*This message was scanned for all current viruses and is certified clean* I upgraded 2 days ago from 2.7.STABLE5 to 2.7.STABLE6 due to complaints about hotmail hanging. I have 3 squid servers, and I updated all 3 at the same time. I use one as the primary in a transparent mode, and it is forced to make requests from the other two parents, which are on different connections to the internet. This gives me a way to load balance between two connections. Anyway, the weighting was working great until I upgraded. After I noticed the problem, I made sure that I was seeing ICP packets coming from the primary to both parents, and they were, and ICP packets are coming back from the parents. The primary would always use the closest parent, no matter the weight setting. I went back to 2.7.STABLE5 on the primary and the problem disappeared. I found a reference to bug 2241, which seems to address this issue, but the patch for neighbors.c appears to patch a different version than the 2.7.STABLE6 source that I built from. It does appear that 2241 has been incorporated into Squid 3. Is Squid 3 mature enough to simply migrate to with my setup? Or should I continue to try to patch 2.7S6? If so, how can I patch from a different source version? Thanks in advance, Jon
3.0.STABLE13 is stable enough for production use. You will likely find it a (estimate) 10%-15% speed drop from 2.7 though. Also there are experimental features from 2.7 not present in 3.0, so check the ones you need still exist before migrating over.
Attempting a manual patch if you have the expertise may be worth the effort as well. We still support 2.7 and those who can't migrate, so if you do and find it fixes the issue please submit for adding to 2.7.
Amos -- Please be using Current Stable Squid 2.7.STABLE6 or 3.0.STABLE13 Current Beta Squid 3.1.0.5
