[squid-users] cache.log errors and warnings: how fatal are they

Running a rock store experiment with SMP Squid 3.HEAD rev 13295 on 750
mbps of HTTP traffic.

There're few cache.log errors and warnings that aren't clear enough
for me. What triggers them, and how do they affect the corresponding
request that provoked them?

WARNING: Ignoring malformed cache entry
WARNING: swapfile header inconsistent with available data
WARNING: 10 swapin MD5 mismatches
Could not parse headers from on disk object
clientProcessHit: Vary object loop!
varyEvaluateMatch: Oops. Not a Vary object on second attempt,
'http://www.shaadi.com/' 'accept-encoding="gzip,deflate,sdch"'
clientIfRangeMatch: Weak ETags are not allowed in If-Range:
"68390-1391166396000" ? "68390-1391166396000"
fqdncacheParse: No PTR record for '77.87.212.52'

My main concern is if any one of the above actually breaks the
corresponding request?

Thank you in advance for the clarification.

Best,
Niki
Received on Wed Mar 05 2014 - 17:00:03 MST