On 11/1/07, Peter Uthoff <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I have a problem where my Apache procs are dying almost exactly every
> ten
> minutes as you can from the messages and web logs below:
>
> Oct 25 10:34:44  kernel: pid 66337 (httpd), uid 80: exited on signal 4
> Oct
> 25 10:35:33  kernel: pid 66357 (httpd), uid 80: exited on signal 4 Oct
> 25
> 10:45:11  kernel: pid 66395 (httpd), uid 80: exited on signal 4 Oct 25
> 10:55:21  kernel: pid 66340 (httpd), uid 80: exited on signal 4
>
> Looking at the Apache logs, I find the following:
>
> [Thu Oct 25 10:25:01 2007] [notice] child pid 66379 exit signal Illegal
> instruction (4)
> [Thu Oct 25 10:34:44 2007] [notice] child pid 66337 exit signal Illegal
> instruction (4)
> [Thu Oct 25 10:35:33 2007] [notice] child pid 66357 exit signal Illegal
> instruction (4)
> [Thu Oct 25 10:45:11 2007] [notice] child pid 66395 exit signal Illegal
> instruction (4)
>
> I tried upping the logs all the way to debug today and it really wasn't
> very helpful:
>
> [Wed Oct 31 15:59:19 2007] [debug] prefork.c(991): AcceptMutex: flock
> (default: flock)
> [Wed Oct 31 16:05:39 2007] [notice] child pid 73668 exit signal Illegal
> instruction (4)
> [Wed Oct 31 16:12:01 2007] [info] server seems busy, (you may need to
> increase StartServers, or Min/MaxSpareServers), spawning 8 children,
> there
> are 4 idle, and 17 total children
> [Wed Oct 31 16:15:04 2007] [notice] child pid 73779 exit signal Illegal
> instruction (4)
> [Wed Oct 31 16:15:28 2007] [notice] child pid 73717 exit signal Illegal
> instruction (4)
> [Wed Oct 31 16:18:37 2007] [notice] child pid 95939 exit signal Illegal
> instruction (4)
>
> I don't believe the 'busy' message is accurate. I think it's a result of
> the procs dying constantly as I just don't get that much traffic. I also
> have no idea what is causing the illegal instructions because none of
> the logs point out any specific detail to help me track it down.
>
> I'm running the following:
>
> FreeBSD 6.2-RELEASE-p8 FreeBSD 6.2-RELEASE-p8 #3: Thu Oct 25 20:04:14
> CDT
> 2007  :/usr/obj/usr/src/sys/GENERIC  i386
>
> apache-2.2.6_2      Version 2.2 of Apache web server with prefork MPM.
>
> php5-5.2.4_1        PHP Scripting Language
>
> mysql-client-5.0.45_1 Multithreaded SQL database (client)
> mysql-server-5.0.45_1 Multithreaded SQL database (server)
> p5-DBD-mysql50-4.005 MySQL 5.0 driver for the Perl5 Database Interface
> (DBI)
> php5-mysql-5.2.4_1  The mysql shared extension for php
> php5-mysqli-5.2.4_1 The mysqli shared extension for php
>
> I'm using vhosts to host 4 different websites with different domains.
> The
> sad part is that these all show no errors in their logs even with them
> turned up to debug level. I've been looking at this off and on trying to
> solve it as time allowed since mid-September. I'm completely stumped and
> would appreciate any helpful suggestions where else I can look.
>
> Thank you!
>
> This email was sent to you by Reuters, the global news and information
> company.
> To find out more about Reuters visit www.about.reuters.com
>
> Any views expressed in this message are those of the individual sender,
> except where the sender specifically states them to be the views of
> Reuters Limited.
>
> Reuters Limited is part of the Reuters Group of companies, of which
> Reuters Group PLC is the ultimate parent company.
> Reuters Group PLC - Registered office address: The Reuters Building, South
> Colonnade, Canary Wharf, London E14 5EP, United Kingdom
> Registered No: 3296375
> Registered in England and Wales
>
>
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
> [EMAIL PROTECTED]"
>



First thing that comes to mind is to download knoppix and use either
"memtest" or "memtest86" as the cheatcode. I forget which.
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to