Re: Error message

From: Petri Helenius (pete_at_he.iki.fi)
Date: 12/03/04

  • Next message: Claus Guttesen: "Re: postgresql on FreeBSD 5.3 and high load"
    Date: Fri, 03 Dec 2004 23:52:24 +0200
    To: Alexander Leidinger <Alexander@Leidinger.net>
    
    

    Alexander Leidinger wrote:

    >On Mon, 29 Nov 2004 08:17:40 -0600
    >Mike Horwath <drechsau@Geeks.ORG> wrote:
    >
    >
    >
    >>On Mon, Nov 29, 2004 at 06:12:20PM +0530, Akhthar Parvez. K wrote:
    >>
    >>
    >>>Hi All,
    >>>
    >>>I am getting the following error message in /var/log/messages
    >>>
    >>>tail -f /var/log/messages
    >>>Nov 29 07:24:31 speedy /kernel: pid 83876 (httpd), uid 65534: exited on signal 4
    >>>Nov 29 07:24:31 speedy /kernel: pid 84126 (httpd), uid 65534: exited on signal 4
    >>>
    >>>
    >>[snipper]
    >>
    >>#define SIGILL 4 /* illegal instr. (not reset when caught) */
    >>
    >>
    >>
    >>>Anyhave has any idea why it's coming? I am not getting any error
    >>>messsages in apache error logs.
    >>>
    >>>
    >>Only time I have seen this kind of thing is bad hardware.
    >>
    >>
    >
    >It may also be the case that the wrong CPUTYPE is/was specified in
    >/etc/make.conf.
    >
    >
    Are you running old enough version of apache to be vulnerable to remote
    exploits but they're trying to feed you wrong shellcode?

    Pete

    _______________________________________________
    freebsd-performance@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-performance
    To unsubscribe, send any mail to "freebsd-performance-unsubscribe@freebsd.org"


  • Next message: Claus Guttesen: "Re: postgresql on FreeBSD 5.3 and high load"

    Relevant Pages

    • Re: Error message
      ... Alexander Leidinger wrote: ... >>Only time I have seen this kind of thing is bad hardware. ... >It may also be the case that the wrong CPUTYPE is/was specified in ... To unsubscribe, ...
      (freebsd-questions)
    • Re: MySQL on -current (possible gcc issue?)
      ... > which lack a defined CPUTYPE in make.conf (which translates over to a ... > different hardware and different configurations. ...
      (freebsd-current)
    • Re: Internal compiler error in reload_cse_simplify_operands
      ... I would be extremely disappointed if this were a hardware ... > set CFLAGS and/or CPUTYPE to some strange combination of ... I have no CFLAGS set and CPUTYPE is also not set. ... *** Error code 1 ...
      (freebsd-current)