Date: Mon, 24 Oct 2005 09:39:26 -0500 From: eculp@bafirst.com To: vd@datamax.bg Cc: ports@freebsd.org Subject: Re: Squid +pid 48635 (squid), uid 100: exited on signal 6 (core dumped) Message-ID: <20051024093926.b1wkywbxcgccs0wc@mail.bafirst.com> In-Reply-To: <20051024141529.GA81860@qlovarnika.bg.datamax> References: <20051024071554.hws9x2ia74gokckc@mail.encontacto.net> <20051024141529.GA81860@qlovarnika.bg.datamax>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Vasil Dimov <vd@datamax.bg>: > On Mon, Oct 24, 2005 at 07:15:54AM -0500, Edwin L. Culp wrote: >> 4 Current servers running current and squid-2.5.11_3 that had no >> problems maybe a month ago are now dumping core and logging the >> following: >> >> +pid 48635 (squid), uid 100: exited on signal 6 (core dumped) >> >> I have no idea where to begin looking. From the squid list and saw >> where it could be caused by persistent connections on some platforms so >> I turned them off and there was no change. >> >> All the machines are running up to date ports, with kernel and userland >> no more that a week old and there are both Intel and amd processors. >> One box has multiple processors so it doesn't seem to be a hardware >> issue due to the diversity. Any help or suggestions for what I might >> try will be very much appreciated. >> >> ed > > You should firstly locate the core file and get a backtrace with gdb. > Compiling as much as possible stuff with -g (and without -O) and > preventing strip(1) in the install step will help you to get more > useful backtrace. > You are right, Vasil. I will start on that. I had hoped that someone else was seeing the problem and had solved it with configuration or recompile with changed flags, etc. One can always hope and dream ;-) Thanks, ed
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051024093926.b1wkywbxcgccs0wc>