Well, sorry for the "thread steal"...
Amos Jeffries wrote:
On 11.09.2012 07:54, Jose-Marcio Martins da Cruz wrote:
I posted a message here some days ago (subject : squid 3.2.1 on
solaris). Got no answer. It seems a similar problem.
No. These are two different bugs.
Migrating from 3.1.19 to 3.2.1.
squid continuously die with : FATAL: Received Segment Violation...dying.
Some invalid pointer reference or such in the code. We need a debug backtrace to
identify where exactly this violation is occuring.
Well, I didn't succeeded to get a core dump.
Looking a little more at /var/adm/messages, I see that the signal received isn't
SIGSEGV (11) but SIGIOT (6). Maybe (not sure) this explains why I can't get a
core dump.
******************
Sep 11 14:51:52 cc-proxy-2 squid[20881]: [ID 604506 local4.notice] Squid Parent:
(squid-1) process 21011 exited due to signal 6 with status 0
Sep 11 14:51:55 cc-proxy-2 squid[20881]: [ID 632156 local4.notice] Squid Parent:
(squid-1) process 21022 started
******************
Is the file cache.log got with some value of debug_option OK for you ?
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.
--
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
