[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cobalt-users] Squid consuming 100% of cpu rescs: newbie
- Subject: RE: [cobalt-users] Squid consuming 100% of cpu rescs: newbie
- From: "Andy Brown" <andy.brown@xxxxxxxxxxxxx>
- Date: Fri Sep 6 08:28:01 2002
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
<snip>
> My Cobalt Qube3 pro run squid for the proxy, but the problem
> is the squid
> consuming almost 100% of my cpu resourcess.
> Is it becouse the cobalt is not using the latest version of
> squid or i
> have to debuging the squid.conf to make it more lower the cpu
> state need.
</snip>
OK, the reason is because the version of squid on the Qube3 is Squid 2.3.STABLE3, which has a known bug where when the cache size reaches the set limit it doesn't correctly unlink (delete) the files, it jumps to 100% cpu and doesn't delete anything, so causing disk-space & CPU problems.
The only way i've found of correcting this (Never tried on Qube's though, only on normal Slakware Linux boxes) is to apply the diff issued which is squid-2.3.stable3-storeExpiredReferenceAge.patch
However, this must be done to the source before compilation, and i'm unsure if Cobalt has done anything unusual to the squid during compilation.
If anyone out there has a spare Qube3, they could try either getting the new squid from www.squid-cache.org and compiling see if the Qube still works, or try getting the old 2.3.stable3 and applying the patch to correct this.
Regards,
Andy
andy@xxxxxxxxxx
http://www.raqpak.com/ <-- Raq/Qube unofficial PKGs and support advice