Re: [squid-users] WARNING: Ignoring cache entry due to a SIZE MISMATCH

2017-02-19 Thread Amos Jeffries
On 18/02/2017 3:18 a.m., Heiler Bemerguy wrote: > > Em 17/02/2017 09:44, Amos Jeffries escreveu: >> On 16/02/2017 10:40 a.m., Heiler Bemerguy wrote: >>> Is it normal, on every restart? >>> >> Well, this is a check that is only performed on restart. So in a way it >> is "normal" that it occurs on r

Re: [squid-users] WARNING: Ignoring cache entry due to a SIZE MISMATCH

2017-02-17 Thread Heiler Bemerguy
Em 17/02/2017 09:44, Amos Jeffries escreveu: On 16/02/2017 10:40 a.m., Heiler Bemerguy wrote: Is it normal, on every restart? Well, this is a check that is only performed on restart. So in a way it is "normal" that it occurs on restart. It should not happen at all though. AFAIK, it is a sign

Re: [squid-users] WARNING: Ignoring cache entry due to a SIZE MISMATCH

2017-02-17 Thread Amos Jeffries
On 16/02/2017 10:40 a.m., Heiler Bemerguy wrote: > > Is it normal, on every restart? > Well, this is a check that is only performed on restart. So in a way it is "normal" that it occurs on restart. It should not happen at all though. AFAIK, it is a sign of cache corruption... > maximum_object

[squid-users] WARNING: Ignoring cache entry due to a SIZE MISMATCH

2017-02-16 Thread Heiler Bemerguy
Is it normal, on every restart? maximum_object_size 2 GB cache_dir rock /cache 12 min-size=0 max-size=12288 slot-size=12288 max-swap-rate=250 swap-timeout=350 cache_dir rock /cache2 12 min-size=10240 max-size=65536 max-swap-rate=250 swap-timeout=360 2017/02/15 18:38:50 kid7| WARNING