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

[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_size 2 GB
> cache_dir rock /cache  120000 min-size=0 max-size=12288 slot-size=12288
> max-swap-rate=250 swap-timeout=350
> cache_dir rock /cache2 120000 min-size=10240 max-size=65536
> max-swap-rate=250 swap-timeout=360
> 

These caches cannot store objects larger than 64KB. So where do you
expect the 64KB thru 2GB objects to go?


> 2017/02/15 18:38:50 kid7| WARNING: Ignoring cache entry due to a SIZE
> MISMATCH 5852!=5853
> 2017/02/15 18:38:51 kid7| WARNING: Ignoring cache entry due to a SIZE
> MISMATCH 6223!=6222
> 2017/02/15 18:38:51 kid7| WARNING: Ignoring cache entry due to a SIZE
> MISMATCH 4198!=4202
...

That last line means the rock database contains an object of size 4198
bytes, with 4202 bytes of data in it.

 4202 > 4198. So 4 bytes of what? the next database slot? padding data?


You have any custom patches applied to this Squid? what version is it?

Amos