From owner-freebsd-questions@FreeBSD.ORG Thu Mar 17 17:45:18 2005 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 9DC0D16A4CE for ; Thu, 17 Mar 2005 17:45:18 +0000 (GMT) Received: from klmhosting.net (ip-64-124-231-116.sea1.gadoz.com [64.124.231.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CF2C43D2F for ; Thu, 17 Mar 2005 17:45:18 +0000 (GMT) (envelope-from kyle@xraided.net) Received: from [172.16.45.200] (account kyle [172.16.45.200] verified) by klmhosting.net (CommuniGate Pro SMTP 4.2.8) with ESMTP id 168487 for freebsd-questions@freebsd.org; Thu, 17 Mar 2005 09:43:43 -0800 Message-ID: <4239C1DB.8010304@xraided.net> Date: Thu, 17 Mar 2005 09:43:55 -0800 From: Kyle Mott User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <000901c52b14$076bc210$0a01a8c0@ops.cenergynetworks.com> <20050317173021.GD8226@gentoo-npk.bmp.ub> In-Reply-To: <20050317173021.GD8226@gentoo-npk.bmp.ub> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Apache 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: Thu, 17 Mar 2005 17:45:18 -0000 This just very recently started to happen (and I haven't upgraded Apache as of late either, or any other software for that matter). I keep getting this in my kernel.log on 2 different hosts: Mar 17 09:34:16 logsrv pid 38069 (httpd), uid 0: exited on signal 11 (core dumped) Mar 17 00:34:25 g1bs0n kernel: pid 9419 (httpd), uid 0: exited on signal 11 (core dumped) Both hosts are running 'apache+mod_ssl-1.3.33+2.8.22' plus 'php4-4.3.10', and a bunch of php modules that I don't want to list. i was able to get Apache running on g1bs0n by not starting ssl; however, Apache won't start on logsrv at all. Looking up man signal, SIGSEGV (11) is a segmentation violation. What can cause this on 2 different machines that haven't been updated in a while? I'm currently running a ports-cvsup, to verify that apache+mod_ssl either does or does not need to be updated. -Kyle Mott