Date: Thu, 17 Mar 2005 10:28:58 -0800 From: Kyle Mott <kyle@xraided.net> To: freebsd-stable@freebsd.org Subject: Apache Signal 11 (5.3-RELEASE-p3/4) Message-ID: <4239CC6A.7050402@xraided.net> In-Reply-To: <4239B796.80303@errno.com> References: <6.2.1.2.0.20050315112131.054b56f8@64.7.153.2> <4237523B.7090005@errno.com> <ygek6o7inb5.wl%ume@mahoroba.org> <4238782A.7010606@errno.com> <ygeis3rbcu7.wl%ume@mahoroba.org> <4239B796.80303@errno.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I've already sent this question to freebsd-questions; forgive me if this is the wrong list. 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4239CC6A.7050402>