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

From: Niki Gorchilov <niki_at_gorchilov.com>
Date: Wed, 5 Mar 2014 19:51:39 +0200

On Wed, Mar 5, 2014 at 6:59 PM, Niki Gorchilov <niki_at_gorchilov.com> wrote:
> 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'

One more error:
idnsGrokReply: Malformed DNS response

> 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:52:29 MST

This archive was generated by hypermail 2.2.0 : Fri Mar 07 2014 - 12:00:05 MST