Search squid archive

Re: could not parse headers from a disk structure!

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxx> 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


[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux