From owner-freebsd-ports@FreeBSD.ORG Mon Oct 24 14:15:31 2005 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D15C416A41F for ; Mon, 24 Oct 2005 14:15:31 +0000 (GMT) (envelope-from vd@datamax.bg) Received: from jengal.datamax.bg (jengal.datamax.bg [82.103.104.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6926143D45 for ; Mon, 24 Oct 2005 14:15:31 +0000 (GMT) (envelope-from vd@datamax.bg) Received: from qlovarnika.bg.datamax (qlovarnika.bg.datamax [192.168.10.2]) by jengal.datamax.bg (Postfix) with SMTP id 49948B83B; Mon, 24 Oct 2005 17:15:30 +0300 (EEST) Received: (nullmailer pid 81897 invoked by uid 1002); Mon, 24 Oct 2005 14:15:30 -0000 Date: Mon, 24 Oct 2005 17:15:30 +0300 From: Vasil Dimov To: "Edwin L\. Culp" Message-ID: <20051024141529.GA81860@qlovarnika.bg.datamax> References: <20051024071554.hws9x2ia74gokckc@mail.encontacto.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051024071554.hws9x2ia74gokckc@mail.encontacto.net> X-OS: FreeBSD 6.0-RC1 User-Agent: Mutt/1.5.11 Cc: ports@freebsd.org Subject: Re: Squid +pid 48635 (squid), uid 100: exited on signal 6 (core dumped) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vd@datamax.bg List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2005 14:15:31 -0000 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.