Re: [squid-users] Vary object loop?

tor 2010-07-29 klockan 11:03 +0200 skrev Ralf Hildebrandt:
> >From my Logs today:
>
> 2010/07/29 10:59:25| could not parse headers from on disk structure!
> 2010/07/29 10:59:25| varyEvaluateMatch: Oops. Not a Vary object on second attempt, 'http://service.gmx.net/de/FCKeditor/fckeditor.js' 'accept-encoding="gzip,%20deflate"'
> 2010/07/29 10:59:25| clientProcessHit: Vary object loop!
> 2010/07/29 11:00:56| could not parse headers from on disk structure!
> 2010/07/29 11:00:56| varyEvaluateMatch: Oops. Not a Vary object on second attempt, 'http://static.ak.fbcdn.net/rsrc.php/zC9LW/hash/58740o8y.css' 'accept-encoding="gzip,deflate"'
> 2010/07/29 11:00:56| clientProcessHit: Vary object loop!
> 2010/07/29 11:01:08| could not parse headers from on disk structure!
> 2010/07/29 11:01:08| varyEvaluateMatch: Oops. Not a Vary object on second attempt, 'http://service.gmx.net/de/FCKeditor/fckeditor.js' 'accept-encoding="gzip,%20deflate"'
> 2010/07/29 11:01:08| clientProcessHit: Vary object loop!
> 2010/07/29 11:01:17| could not parse headers from on disk structure!
> 2010/07/29 11:01:17| varyEvaluateMatch: Oops. Not a Vary object on second attempt, 'http://download.interscience.wiley.com/freeflow/css/wis.standards.css' 'accept-encoding="gzip,deflate"'
> 2010/07/29 11:01:17| clientProcessHit: Vary object loop!
> 2010/07/29 11:01:24| could not parse headers from on disk structure!
> 2010/07/29 11:01:55| could not parse headers from on disk structure!
>
> a) "could not parse headers from on disk structure!"
> I don't get this, since I WIPED (!) the cache just prior to that.
> So why can't squid3.1 parse it's own data?

The only case I know of if the object meta header gets excessively
large, but that should only happen on very long URLs which do not seem
to be the case here.

> b) varyEvaluateMatch: Oops. Not a Vary object on second attempt?
> What's that?

It means that what Squid found when trying to resolve the correct Vary
response was not a Vary response. In your case above it seems to be a
sideeffect of the "could not parse" error which makes sense.

When an object uses Vary the store lookup is done in two steps. First a
meta object which tells the Squid cache which Vary header the response
varies on, then based on that a second lookup for the actual object. The
message says that the response Squid found when doign that second lookup
did not match what it expected.

Regards
Henrik
Received on Mon Aug 02 2010 - 19:52:48 MDT