There is a bug open for this in bugzilla http://www.squid-cache.org/bugs/show_bug.cgi?id=972 and a test patch against 2.5 stable5 that appears to fix the problem. I was experiencing the same problem several times a day across lots of servers. I have applied the patch and so far so good no crashes.
Steve -----Original Message----- From: alex [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 19, 2004 7:05 AM To: squid-users Subject: [SPAM] - Re: [squid-users] FATAL: Received Segment Violation...dying. (SOLVED) - Bayesian Filter detected spam I get same error. Squid is 2.5.STABLE5 Compile options: --enable-gnuregex --enable-snmp --enable-linux-netfilter --enable-internal-dns --with-pthreads --enable-wccpv2 --disable-icmp --disable-wccp --disable-arp-acl --disable-ssl --disable-ident-lookups --disable-unlinkd (transparent proxy using wccpv2, linux-netfilter, etc.). Here is what I get: 2004/05/19 15:22:16| httpSendRequestEntryDone: Likely proxy abuse detected 'x.x.x.x' -> 'http://activex.microsoft.com/objects/ocget.dll' FATAL: Received Segment Violation...dying. After this squid restarts. What can it be? Raymond A. Meijer wrote: >On Fri 23 April 2004 22:31, Henrik Nordstrom wrote: > > > >>I saw earlier in this thread that -O6 was used. Using any -O level above >>-O2 is generally not advisable as there very often lurks compiler bugs at >>those higher levels, and it is in addition not expected higher -O levels >>will give any better performance of Squid. Over the years there has been >>quite many reports about segmentation faults from people using too >>aggressive compiler optimizations, and it has most often been fixed by >>using a normal optimization level. >> >> > >I think that my problems were caused by the "--enable-dlmalloc" configure >option (I had tried "-O2" before). > >Last Friday I recompiled Squid this way: > >export CFLAGS="-s -DNUMTHREADS=24" > >ulimit -n 4096 > >./configure --prefix=/opt/squid-2.5.STABLE5 --enable-linux-netfilter >--enable-async-io=24 --enable-underscores '--enable-removal-policies=lru >heap' > >make -j3 all > >make install > >and it's been working perfectly ever since. > >Thanks everybody for your suggestions! > > >Ray > > >
