RE: [squid-users] Impressions of 3.2.1

Have downgraded back to 3.1.20 on one server without any changes to the hardware.
Everything working fine till now.

Rgds,
Sunil

-----Original Message-----
From: Amos Jeffries [mailto:squid3_at_treenet.co.nz]
Sent: Monday, September 10, 2012 11:22 PM
To: squid-users_at_squid-cache.org
Subject: Re: [squid-users] Impressions of 3.2.1

On 11.09.2012 01:16, Eliezer Croitoru wrote:
> On 9/7/2012 11:29 AM, Daniel Beschorner wrote:
>> Thank you for the advice!
>> We don't use a disk cache, but anyway good to know.
>>
>> Daniel
>>
>> <031701cd8cc3$c626b7f0$527427d0$@hyperia.com>:
>>> Greetings,
>>>
>>> For migrating to 3.1 to 3.2 did you have to reinitialize the squid
>>> dir.
>>>
>>> Had tried to move from 3.1 to 3.2 a couple of times but was
>>> unsuccessful.
>>> There were frequent "FATAL: Received Segment Violation...dying."
>>> messages .
>>>
>>> Rgds,
>>> Sunil
>>
> weird because I have use 3.1.20 and 3.2.0.19-3.2.1 with the same
> cache_dir no getting any of these problems.
> what version of 3.1?

For 3.1.20 you will have already had to do the swap.state file rebuild.
It is required for migrating to any 3.1.19 or later Squid to create a swap.state file with checksums added. see bug 3441 for more details.

Reinitialize is not specifically required, but is the easy way to upgrade the cache without any downtime.

Amos
Received on Tue Sep 11 2012 - 09:20:46 MDT