Date: Fri, 14 Mar 2008 20:41:10 +0100 From: Wael Nasreddine <mla@nasreddine.com> To: freebsd-questions@freebsd.org Subject: Re: apache 2.2.8 uid 80: exited on signal 11 (was signal 4) Message-ID: <20080314194109.GI9831@phoenix.nasreddine.info> In-Reply-To: <47DAC330.3040506@daleco.biz> References: <264730.93904.qm@web33705.mail.mud.yahoo.com> <200803141832.41139.fbsd.questions@rachie.is-a-geek.net> <20080314175546.GH9831@phoenix.nasreddine.info> <47DAC330.3040506@daleco.biz>
next in thread | previous in thread | raw e-mail | index | archive | help
--a7XSrSxqzVsaECgU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable This One Time, at Band Camp, Kevin Kinsey <kdk@daleco.biz> said, On Fri, Ma= r 14, 2008 at 01:25:52PM -0500: > Wael Nasreddine wrote: >> This One Time, at Band Camp, Mel <fbsd.questions@rachie.is-a-geek.net>= =20 >> said, On Fri, Mar 14, 2008 at 06:32:40PM +0100: >>> On Friday 14 March 2008 16:32:30 Abdullah Ibn Hamad Al-Marri wrote: >>>> pid 88487 (httpd), uid 80: exited on signal 4 >>>> pid 98657 (httpd), uid 80: exited on signal 4 >>>> pid 52780 (httpd), uid 80: exited on signal 4 >>>> pid 58619 (httpd), uid 80: exited on signal 4 >>> #define SIGILL 4 /* illegal instr. (not reset when caugh= t)=20 >>> */ >>> If you're sure there are no CPU specific flags set during apache=20 >>> compilation, you might want to get a core dump. Is apache the only=20 >>> program creating SIGILL? >> I'm having a similar issue, ny dmesg is filled with >> -------- CUT >> pid 63364 (httpd), uid 80: exited on signal 11 >> -------- CUT >> my /etc/make.conf: >> -------- CUT >> CFLAGS+=3D"-march=3Dpentium4" >> WITHOUT_X11=3Dyes >> WITHOUT_JAVA=3Dyes >> # Use Perl with threads >> WITH_THREADS=3Dyes >> # added by use.perl 2008-03-13 22:04:11 >> PERL_VER=3D5.8.8 >> PERL_VERSION=3D5.8.8 >> -------- CUT >> what could be the problem... > > Well, first, signal 11 isn't signal 4, so the > problem isn't very *closely* related, but I'll > bite anyway. > Sorry for being off-topic I thought the solution would be almost the same or he could try whatever solution proposed to both of us, anyway sorry again :$ > That said, I've little idea what could be > causing your httpd to die with sig 11. In > my experience, signal 11s are generally caused > by incompatible modules (*.so) loading along > with httpd during Apache startup. PHP, in > particular, after a portupgrade. Any resemblance > to your situation? > Actuallly it's a fresh 7.0-RELEASE Installation, So I don't think a module might be broken unless it's a bug. > Kevin Kinsey --=20 Wael Nasreddine http://wael.nasreddine.com PGP: 1024D/C8DD18A2 06F6 1622 4BC8 4CEB D724 DE12 5565 3945 C8DD 18A2 =2E: An infinite number of monkeys typing into GNU emacs, would never make a good program. (L. Torvalds 1995) :. --a7XSrSxqzVsaECgU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.7 (GNU/Linux) iD8DBQFH2tTVVWU5RcjdGKIRAv6lAJ98V5FDfKrf1s6MTyQVKl/AAqtZ7ACfevL3 RzTeNoQLucvagijMxFKUY/A= =t4q8 -----END PGP SIGNATURE----- --a7XSrSxqzVsaECgU--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080314194109.GI9831>