Hi,
Segment violation is definitely the bug. Would you mind reporting the
one to squid's bug tracker (bugs.squid-cache.org0?
TIA,
Pavel
On 08/18/2013 12:56 AM, Golden Shadow wrote:
Hi,
I think I got the answer to my question and thought it would be nice if I post
what I've concluded to the list, just in case somebody would have the same
question in the future.
I had the following two cache.log entries whenever the server is improperly
shutdown via power failure (Yes, it is odd but this is what happens in that
remote site!). squid keep spawning new worker but it dies after a short time.
kid1| WARNING: swapfile header inconsistent with available data
FATAL: Received Segment Violation...dying.
So to fix this, squid must first be shut down, and then swap.state files are
deleted, then once you start squid again, it will try to generate new and
consistent swap.state files. One very important thing to keep in mind is that
this process may take a very long time depending on your cache_dir size! Since
I had no other option, I had to risk the 2 TB cache contents and tried that,
but I ended up with squid taking a long time (roughly 30 hours) trying to
generate new swap.state files.
Best regards,
Firas
----- Original Message -----
From: Golden Shadow <[email protected]>
To: "[email protected]" <[email protected]>
Cc:
Sent: Friday, August 16, 2013 7:10 PM
Subject: [squid-users] swapfile header inconsistent with available data
Hi Squid-users!
Recently squid started to restart its working kid and I see the following log
entries in cache.log:
kid1| WARNING: swapfile header inconsistent with available data
FATAL: Received Segment Violation...dying.
Any advice to fix this? Can I just shutdown squid, remove swap.state and then
start squid again?
Best regards,
Firas
