Re: [squid-users] could not parse headers from a disk structure!

Important question - Landy, what version of squid, and what OS, are
you running on?

Was it a precompiled Squid or a custom compliation? If custom, what
were the build options?

I've seen stuff like this repeatedly in the long tail chase of
3.0-StableX versions 2ish years ago, when things went sideways, but it
could also be a one time blip for you.

-george

On Sun, Oct 10, 2010 at 4:47 PM, Amos Jeffries <squid3_at_treenet.co.nz> wrote:
> On Sun, 10 Oct 2010 07:22:15 -0700 (PDT), Landy Landy
> <landysaccount_at_yahoo.com> wrote:
>> Ok.
>>
>> I'm still getting that message. Looks like there were a lot of corrupted
>> files.
>>
>> Thanks for replying.
>
> In the corruption case, as Kinkie said, Squid discards the file and
> replaces it with a new one. This causes the message to decline as things
> get fixed. It may last a week or more to completely go, but should have an
> exponential decline as cleanup progresses. Are they noticeably decreasing
> already?
>
> Another potential cause is an upgrade of Squid where a disk format bug was
> added or fixed between the two versions. Or 32-bit -> 64-bit upgrade to the
> build or hardware. This would churn through the whole previous cache
> instead of just a small selection of corrupted files.
>
> If the warnings are not decreasing with time you may need to enable the
> store.log and check the timestamps for creation/release for some of the
> reported files. Any which are created by the current process then fail to
> read back need closer inspection.
>
> Things to consider that will impact this are: since you last re-started
> Squid has there been an OS kernel update? a squid binary change? a libc
> update? an ntp binary update (timestamp sizes)? a filesystem change? crypto
> library update (MD5)?
>  Any one of those could stay hidden on the system until a restart of the
> box or Squid brings up the new software linkages.
>
> Amos
>
>>
>> --- On Sat, 10/9/10, Kinkie <gkinkie_at_gmail.com> wrote:
>>
>>> From: Kinkie <gkinkie_at_gmail.com>
>>> Subject: Re: [squid-users] could not parse headers from a disk
> structure!
>>> To: "Landy Landy" <landysaccount_at_yahoo.com>
>>> Cc: "Squid-Users" <squid-users_at_squid-cache.org>
>>> Date: Saturday, October 9, 2010, 1:45 PM
>>> You  are right, and you don't
>>> need to do anything. Those cache files
>>> will be discarded by Squid.
>>>
>>> On Friday, October 8, 2010, Landy Landy <landysaccount_at_yahoo.com>
>>> wrote:
>>> > Today, I noticed some sites were not loading and was
>>> getting "connection refused error". checked the cache.log
>>> and noticed squid was restarting due to
>>> >
>>> > 2010/10/08 15:41:01| WARNING: redirector #17 (FD 24)
>>> exited
>>> > 2010/10/08 15:41:01| WARNING: redirector #15 (FD 22)
>>> exited
>>> > 2010/10/08 15:41:01| WARNING: redirector #10 (FD 17)
>>> exited
>>> > 2010/10/08 15:41:01| WARNING: redirector #13 (FD 20)
>>> exited
>>> > 2010/10/08 15:41:01| WARNING: redirector #12 (FD 19)
>>> exited
>>> > 2010/10/08 15:41:01| WARNING: redirector #6 (FD 13)
>>> exited
>>> >
>>> > I shutdown squid and after 5 minutes restarted it
>>> again and now i get the following:
>>> >
>>> > 2010/10/08 15:44:30| WARNING: 1 swapin MD5 mismatches
>>> > 2010/10/08 15:44:30| could not parse headers from on
>>> disk structure!
>>> > 2010/10/08 15:44:42| could not parse headers from on
>>> disk structure!
>>> > 2010/10/08 15:44:42| could not parse headers from on
>>> disk structure!
>>> > 2010/10/08 15:45:10| could not parse headers from on
>>> disk structure!
>>> > 2010/10/08 15:45:13| could not parse headers from on
>>> disk structure!
>>> > 2010/10/08 15:45:16| could not parse headers from on
>>> disk structure!
>>> > 2010/10/08 15:45:25| could not parse headers from on
>>> disk structure!
>>> > 2010/10/08 15:45:26| could not parse headers from on
>>> disk structure!
>>> > 2010/10/08 15:45:29| could not parse headers from on
>>> disk structure!
>>> >
>>> > Don't know what causes it but, I'm suspecting some
>>> cache files are corrupted. I had a power outage yesterday
>>> and maybe it caused that.
>>> >
>>> > How can I fix that error?
>>> >
>>> > Thanks in advanced for your help.
>>> >
>>> >
>>> >
>>> >
>>>
>>> --
>>>     /kinkie
>>>
>

-- 
-george william herbert
george.herbert_at_gmail.com