* Henrik Nordström <henrik_at_henriknordstrom.net>:
> > 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.
It seems to happen quite often here.
> 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.
So something is broken? How should I debug this further? I can add
more logging if you like.
-- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt@charite.de | http://www.charite.deReceived on Mon Aug 02 2010 - 19:54:29 MDT
This archive was generated by hypermail 2.2.0 : Tue Aug 03 2010 - 12:00:02 MDT