From owner-freebsd-questions@FreeBSD.ORG Wed Feb 18 14:22:32 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B17016A4CF for ; Wed, 18 Feb 2004 14:22:32 -0800 (PST) Received: from skutsje.san.webweaving.org (skutsje.san.webweaving.org [209.132.96.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7797643D1F for ; Wed, 18 Feb 2004 14:22:32 -0800 (PST) (envelope-from dirkx@asemantics.com) Received: from [10.11.0.203] (fia193-115-100.dsl.hccnet.nl [80.100.115.193]) (authenticated bits=0)i1IMHTEJ011356 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Wed, 18 Feb 2004 14:17:32 -0800 (PST) (envelope-from dirkx@asemantics.com) In-Reply-To: <20040218163844.GA86823@q.internal.closedsrc.org> References: <20040218163844.GA86823@q.internal.closedsrc.org> Mime-Version: 1.0 (Apple Message framework v612) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Dirk-Willem van Gulik Date: Wed, 18 Feb 2004 23:22:21 +0100 To: Linh Pham X-Mailer: Apple Mail (2.612) cc: freebsd-questions@freebsd.org Subject: Re: Problems with Apache 1.3 segfaulting in 5.2.1-RC? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Feb 2004 22:22:32 -0000 On Feb 18, 2004, at 5:38 PM, Linh Pham wrote: > Has anyone ran into problems with Apache 1.3.x segfaulting (signal 11) > under FreeBSD 5.2.1-RC[12]? I had to recently re-install FreeBSD on my > home server and grabbed the latest src-all for RELENG_5_2, which ended > up being for 5.2.1-RC2. Afterwards, I compiled and installed Apache 1.3 > plus PHP5 and PostgreSQL and got it up and running without any > problems. > Easiest thing is to obtain a core dump; see the man page for 'ulimit', check '/etc/login.conf' and the apache directive for this. Otherwise - if it happens a LOT - you can run (from screen if needed) gdb /usr/local/sbin/httpd -X it will then run single process/thread mode; and if there is a segfault you'll inmediately see the culprit. This is generally too slow for a production server; but will easily handle hobby sites. Given your setup my guess is some PHP5 plugin (I had similar issues until I fixed/recompiled gd). Dw.