This issue might have just been fixed a few days ago in Squid HEAD.
There was definitely a bucket assignment fix that went in, but it may
not be the problem you're seeing. I don't know, I haven't had occasion
to spend time on this problem as I've never run into it personally.
You should probably grab the latest daily snapshot of Squid 2.5, and try
it out.
http://www.squid-cache.org/Versions/v2/2.5/
BTW-These sorts of questions should be sent to the Squid-Users mailing
list. My time is very limited and I'm very likely to ignore emails sent
to me personally if they aren't from my clients. It is more valuable to
me to answer questions in a public forum where the results of the
discussion will be helpful to others, and it will be archived for future
reference.
Hassan Zaheer wrote:
> Hi Joe and Henrik
>
> I'm expereincing a problem, I hope you can help me with this
>
> I have three squid proxy atached to my 7200 router, WCCP works fine with
> two proxy servers but whenever I attach third server I get Packet
> Unassigned in router sh ip wccp output
>
> I read that it happens when some ache goes out of the cluster but when
> its atatched and hash is assigned there should be no packet unassigned
>
> Please tell me what should I cehck for, is there any limit to number of
> cache engines atatch to router through wccp or theres something wrong
> with squid
>
> Also I tried to increase file descriptors in squid using
> ulimit -HSn 8192
> but the cahemgr interface keeps showing 1024, whys that
>
> thanks
-- Joe Cooper <joe@swelltech.com> Web caching appliances and support. http://www.swelltech.comReceived on Thu Oct 31 2002 - 00:15:29 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:10:57 MST