Re: apache 2.2.8 uid 80: exited on signal 11 (was signal 4)

2008-03-14 Thread Wael Nasreddine
This One Time, at Band Camp, Kevin Kinsey <[EMAIL PROTECTED]> said, On Fri, Mar 
14, 2008 at 01:25:52PM -0500:
> Wael Nasreddine wrote:
>> This One Time, at Band Camp, Mel <[EMAIL PROTECTED]> 
>> 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 caught) 
>>> */
>>> If you're sure there are no CPU specific flags set during apache 
>>> compilation, you might want to get a core dump. Is apache the only 
>>> 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+="-march=pentium4"
>> WITHOUT_X11=yes
>> WITHOUT_JAVA=yes
>> # Use Perl with threads
>> WITH_THREADS=yes
>> # added by use.perl 2008-03-13 22:04:11
>> PERL_VER=5.8.8
>> PERL_VERSION=5.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


-- 
Wael Nasreddine
http://wael.nasreddine.com
PGP: 1024D/C8DD18A2 06F6 1622 4BC8 4CEB D724  DE12 5565 3945 C8DD 18A2

.: An infinite number of monkeys typing into GNU emacs,
   would never make a good program. (L. Torvalds 1995) :.


pgpMKKppEDe1g.pgp
Description: PGP signature


Re: apache 2.2.8 uid 80: exited on signal 11 (was signal 4)

2008-03-14 Thread Kevin Kinsey

Wael Nasreddine wrote:

This One Time, at Band Camp, Mel <[EMAIL PROTECTED]> 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 caught) */


If you're sure there are no CPU specific flags set during apache compilation, 
you might want to get a core dump. Is apache the only 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+="-march=pentium4"
WITHOUT_X11=yes
WITHOUT_JAVA=yes

# Use Perl with threads
WITH_THREADS=yes

# added by use.perl 2008-03-13 22:04:11
PERL_VER=5.8.8
PERL_VERSION=5.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.

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?

Kevin Kinsey
--
Marry in haste and everyone starts counting the months.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"