I posted a message here some days ago (subject : squid 3.2.1 on solaris). Got no
answer. It seems a similar problem.
Migrating from 3.1.19 to 3.2.1.
squid continuously die with : FATAL: Received Segment Violation...dying.
Setting debug option to configuration file, I get :
2012/09/04 12:06:11.412 kid1| storeCreate: Selected dir 0 for -1@-1=0/2/1/1
FATAL: Received Segment Violation...dying.
I reinitialized the cache_dir partition, but this changes nothing.
I have another machine, same hardware same OS but no cache, which works fine.
Sunil K.P. wrote:
Not sure what exactly the problem.
Got this error again.
2012/09/10 20:36:22 kid1| FATAL: dying from an unhandled exception:
c
Rgds,
Sunil
-----Original Message-----
From: Eliezer Croitoru [mailto:eliezer@xxxxxxxxxxxx]
Sent: Monday, September 10, 2012 2:16 PM
To: squid-users@xxxxxxxxxxxxxxx
Cc: squid-users@xxxxxxxxxxxxxxx
Subject: Re: Impressions of 3.2.1
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?
--
Eliezer Croitoru
https://www1.ngtech.co.il
IT consulting for Nonprofit organizations eliezer <at> ngtech.co.il
--
Envoyé de ma machine à écrire.
---------------------------------------------------------------
Spam : Classement statistique de messages électroniques -
Une approche pragmatique
Chez Amazon.fr : http://amzn.to/LEscRu ou http://bit.ly/SpamJM
---------------------------------------------------------------
Jose Marcio MARTINS DA CRUZ http://www.j-chkmail.org
Ecole des Mines de Paris http://bit.ly/SpamJM
60, bd Saint Michel 75272 - PARIS CEDEX 06
mailto:Jose-Marcio.Martins@xxxxxxxxxxxxxxxxxx
