From owner-freebsd-questions@FreeBSD.ORG Fri Apr 2 08:11:07 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 1991416A4CF for ; Fri, 2 Apr 2004 08:11:07 -0800 (PST) Received: from calis.blacksun.org (calis.blacksun.org [216.254.108.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7D4443D48 for ; Fri, 2 Apr 2004 08:11:06 -0800 (PST) (envelope-from don@calis.blacksun.org) Received: by calis.blacksun.org (Postfix, from userid 1001) id 7E58F17089; Fri, 2 Apr 2004 11:14:37 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by calis.blacksun.org (Postfix) with ESMTP id 7CF6A17088; Fri, 2 Apr 2004 11:14:37 -0500 (EST) Date: Fri, 2 Apr 2004 11:14:37 -0500 (EST) From: Don To: Mario Doria In-Reply-To: <200404012035.47873.madd@tecdigital.net> Message-ID: <20040402111222.V11568@calis.blacksun.org> References: <200404012035.47873.madd@tecdigital.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-questions@freebsd.org Subject: Re: Problem with mod_php4-4.3.5_7,1 (Signal 11) 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: Fri, 02 Apr 2004 16:11:07 -0000 > I'm hoping someone can help me, I've just upgraded a server to > mod_php4-4.3.5_7,1, running with abcache-0.14 and over > apache+mod_ssl-1.3.29+2.8.16_1. > > The problem is that it crashes with signal 11, I found this on the server's > dmesg output: > pid 1263 (httpd), uid 80: exited on signal 11 > pid 17611 (httpd), uid 80: exited on signal 11 > > On the error log I found this: > [Thu Apr 1 16:52:35 2004] [notice] child pid 17611 exit signal Segmentation > fault (11) > > This is after running for 24 hours. Has anybody else experienced something > similar? I had the same problem. The current version of PHP in the ports tree was crashing the current version of Apache with a sig 11. The slightly older packages were not affected and the problem seemed to exist whether I used Apache-13+mod_ssl or just plain Apache. I ended up using the packages because the problem wasn't critical. What needs to be done is to look at the core dump and figure out what is going on. -Don