Re: AW: Max cache size reached --> squid shuts down!!! help me

At Monday 03:50 PM 27/03/2000 +0200, Scholz, Stefan wrote:
>Hi there,
>
>check if you have a swap.state file and a sile swap.state.new.
>The second file occours when you have 2 squids running at the same
>time or due to misconfiguration. Remove the swap.state.new file

This is not the case. Squid seems to rebuild swap.state.new anytime when
it rebuilds the swap.state file. It is unrelated to the number of squids
running (new versions will only allow one to run yet this file still
appears for me).
Don't confuse multiple squids with the use of Async-io which gives the
false appearance that multiple copies of squid are actually running.

I commonly see this file if squid crashes out without cleaning up properly
and writing all the swap.state out to disk.

>, empty the swap state ( > swap.state ) and restart the squid.
>When the error still appears you must have a problem with the
>cache mem. We experienced that strange error, too, on one of
>our machines when using a machine with 2 Gig left on the harddisk.
>The Cache already needed 2 Gig. When there was less then 2 Gig left
>FREE on the device it stopped the process.

Shutting down squid, removing the swap.state file and restarting squid may
be useful in getting squid to form a "clean" index of what is on
disk. Squid should however be able to maintain a "clean" index of what is
on disk without this sort of intervention...

It might also be worth upgrading from squid-2.2STABLE2 to 2.2STABLE5 or
2.3STABLE2. 2.2STABLE2 is a bit old and has a few nasty bugs.

reuben

-------------------------------------------------------------
Reuben Farrelly West Ryde, NSW 2114, Australia
Received on Mon Mar 27 2000 - 07:28:24 MST