From owner-freebsd-ports@FreeBSD.ORG Mon Oct 24 12:15:58 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 438E516A41F for ; Mon, 24 Oct 2005 12:15:58 +0000 (GMT) (envelope-from eculp@bafirst.com) Received: from bafirst.com (72-12-2-214.wan.networktel.net [72.12.2.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id BADDD43D53 for ; Mon, 24 Oct 2005 12:15:57 +0000 (GMT) (envelope-from eculp@bafirst.com) Received: from encontacto.net ([201.138.84.186]) by bafirst.com with esmtp; Mon, 24 Oct 2005 07:15:55 -0500 id 000958D5.435CD07C.0000EFB5 Received: from localhost (localhost [127.0.0.1]) (uid 80) by encontacto.net with local; Mon, 24 Oct 2005 07:15:54 -0500 id 000C3AFC.435CD07A.00002205 Received: from dsl-201-138-84-186.prod-infinitum.com.mx (dsl-201-138-84-186.prod-infinitum.com.mx [201.138.84.186]) by mail.encontacto.net (Horde MIME library) with HTTP; Mon, 24 Oct 2005 07:15:54 -0500 Message-ID: <20051024071554.hws9x2ia74gokckc@mail.encontacto.net> Date: Mon, 24 Oct 2005 07:15:54 -0500 From: "Edwin L. Culp" To: ports@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.1-cvs Cc: Subject: 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 List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2005 12:15:58 -0000 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