Re: [squid-users] segfault after signal 6

> Hello.
>
> Yesterday, I came across a segfault problem in my squid box. Looking at
> the /var/log/messages file I noticed this:
>
> Jan 12 20:01:38 trahersa-test squid[1719]: Squid Parent: child process
> 1722 exited due to signal 6
<snip long trace>

>
> I don't know what caused this. Could it be a hardware problem or
> something else regarding squid?

We need a trace of where the segFault occured and what squid was doing at
the time in order to find a fix.
Details on how to get this information are in the wiki:
http://wiki.squid-cache.org/SquidFaq/TroubleShooting#head-7067fc0034ce967e67911becaabb8c95a34d576d

>
> I am running:
>
> trahersa-test:~# /usr/local/squid/sbin/squid -v
> Squid Cache: Version 3.0.STABLE11
> configure options: '--prefix=/usr/local/squid'
> '--sysconfdir=/etc/squid' '--enable-delay-pools'
> '--enable-kill-parent-hack' '--disable-htcp'
> '--enable-default-err-language=Spanish' '--enable-linux-netfilter'
> '--disable-ident-lookups' '--disable-internal-dns'
> '--localstatedir=/var/log/squid' '--enable-stacktraces'
> '--with-default-user=proxy' '--with-large-files'
>

FYI: internal-dns is very stable in Squid-3 and should be used.
http://wiki.squid-cache.org/Features/Dnsserver

Amos
Received on Wed Jan 14 2009 - 20:55:55 MST