Had a similar problem a few years back. System worked fine for a number of months then started crashing whenever I recompiled the kernel. Turned out to be a defective secondary cache (yes it was a Pentium and yes it was a number of years ago). Showed up only under heavy cpu load. Try stressing the box. Good luck
On Wed, 20 Feb 2002, Sundara Pandian wrote: > Date: Wed, 20 Feb 2002 10:33:02 +0530 > From: Sundara Pandian <[EMAIL PROTECTED]> > To: SplitSlim <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > Subject: Re: Please, need help urgently > > Hi, > It would be time consuming to understand why the server crashed and then > repair the server, as u say it is a mission crtical one , the quickest way > to get it up and running would be to back up the database (copy the ur > database directory completely under the data directory) reinstall MySQL > cleanly and get the DB back in action again.Also make sure u've got a > 'release' build of MySQL, I got the following info from a site hope that > helps.. > > Signal 11 Description : > Signal 11, or officially know as "segmentation fault", means that the > program accessed a memory location that was not assigned. That's usually a > bug in the program. So if you're writing your own program, that's the most > likely cause. However, this FAQ will concentrate on the possibilities > besides that. > The cause can be software or (most likely) hardware for a Signal 11 crash. > Read on to find out more. (*) Of course nothing is Linux specific. If your > hardware is flaky, Linux, Windows 3.1, FreeBSD, Windows NT and NextStep will > all crash. If you are not reading this at http://www.BitWizard.nl/sig11/, > that's where you can find the most recent version. > > cheers, > Sundara Pandian, > Megasoft Ltd, > India. > > > ----- Original Message ----- > From: "SplitSlim" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, February 20, 2002 10:14 AM > Subject: Please, need help urgently > > > > I need some help, this is a mission critical server and it has > > CRASHED! > > Details:FreeBSD on INTEL, MySQL v3.23.36 (FreeBSD Port) > > The server had to be rebooted, and when it came back up, my MySQL > > server died. It's been working flawlessly for months (5 or 6), but > > all the sudden mysqld will not start. Here's whats in my log... > > _----------------------------------------_ > > 020219 22:52:00 mysqld restarted > > mysqld got signal 11; > > The manual section 'Debugging a MySQL server' tells you how to use a > > stack trace and/or the core file to produce a readable backtrace that > > may > > help in finding out why mysqld died. > > 020219 22:52:00 mysqld restarted > > mysqld got signal 11; > > The manual section 'Debugging a MySQL server' tells you how to use a > > stack trace and/or the core file to produce a readable backtrace that > > may > > help in finding out why mysqld died. > > 020219 22:52:01 mysqld restarted > > mysqld got signal 11; > > The manual section 'Debugging a MySQL server' tells you how to use a > > stack trace and/or the core file to produce a readable backtrace that > > may > > help in finding out why mysqld died. > > 020219 22:52:01 mysqld restarted > > mysqld got signal 11; > > The manual section 'Debugging a MySQL server' tells you how to use a > > stack trace and/or the core file to produce a readable backtrace that > > may > > help in finding out why mysqld died. > > _------------------------------------------_ > > This keeps repeating and repeating. Since it's a port I don't have > > debugging compiled into MySQL, so I can't stack trace. > > > > I've used isamchk, myisamchk, and mysqld --flush to try to clean > > everything up, but no luck. > > > > Please help, I need to get this thing back up tonight! If you need > > anymore info, I'll be on this group all night until I get this thing > > back up. > > > > Thanks in advance! > > NR > > > > > > > > --------------------------------------------------------------------- > > Before posting, please check: > > http://www.mysql.com/manual.php (the manual) > > http://lists.mysql.com/ (the list archive) > > > > To request this thread, e-mail <[EMAIL PROTECTED]> > > To unsubscribe, e-mail > <[EMAIL PROTECTED]> > > Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php > > > --------------------------------------------------------------------- > Before posting, please check: > http://www.mysql.com/manual.php (the manual) > http://lists.mysql.com/ (the list archive) > > To request this thread, e-mail <[EMAIL PROTECTED]> > To unsubscribe, e-mail <[EMAIL PROTECTED]> > Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php > Sincerely, William Mussatto, Senior Systems Engineer CyberStrategies, Inc ph. 909-920-9154 ext. 27 --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
