From owner-freebsd-apache@FreeBSD.ORG Mon Jan 3 10:31:55 2005 Return-Path: Delivered-To: freebsd-apache@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E700916A4CE for ; Mon, 3 Jan 2005 10:31:55 +0000 (GMT) Received: from utopia.in.force-elite.com (force-elite.com [216.255.199.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2878B43D3F for ; Mon, 3 Jan 2005 10:31:55 +0000 (GMT) (envelope-from chip@force-elite.com) X-AuthUser: chip@force-elite.com Received: from [10.0.0.113] (10.0.0.113:55687)Server] ; Mon, 03 Jan 2005 02:31:52 -0800 Message-ID: <41D91F18.7000202@force-elite.com> Date: Mon, 03 Jan 2005 02:31:52 -0800 From: Paul Querna User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Clement Laforet References: <20050103111551.6819aeb0.sheepkiller@cultdeadsheep.org> In-Reply-To: <20050103111551.6819aeb0.sheepkiller@cultdeadsheep.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-apache@FreeBSD.org Subject: Re: apache core dump X-BeenThere: freebsd-apache@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Support of apache-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jan 2005 10:31:56 -0000 Clement Laforet wrote: > On Sat, 1 Jan 2005 10:31:55 -0800 > "whitevamp" wrote: > > >>ok the otherday i had an issue with apache not binding to port 80 >> >>and i thought i got that taken care of, well maby i have but any way >>i knoticed that apache wasnt running any more so i when to start it >>and it whouldnt start so i looked in the error log didnt find >>anything wrong in there so i looked in messages and i found this >>Dec 31 19:00:04 vampextream kernel: pid 88555 (httpd), uid 80: exited on signal 11 >> >>so now its core dumping .. >>so my quistions are >>1. how do i go about debugging this? > > First of all you need to find what is causing the segfault: > - a modules (apache's one or third party one) > - apache itself > > You have to enable or disable every module (one by one) to find the > culpit. After that, rebuild apache and the culpit module (if any) with > debugging stuff. Thats pretty harsh, I generally just rebuild everything eith debugging info enabled. Much faster than trying to manually add/remove all those modules :) After that, you need to allow apache to write a dump. > sysctl kern.sugid_coredump=1 > and use CoreDumpDirectory to define a place to store dump files. > run gdb on the core to find where it fails. > > >>2. and what would be causeing this? > > Generally, mod_php ;) > Find the culpit first, and then you'll see. > > clem > > Note: if you use nss_ldap + php4, it can cause segfaults.