Date: Tue, 1 Aug 2006 09:20:45 +0930 From: Greg 'groggy' Lehey <grog@FreeBSD.org> To: Erik Kristensen <erik@erikkristensen.com> Cc: freebsd-questions@freebsd.org Subject: Re: MySQL Signal 10 on FreeBSD 6.0-RELEASE-P6 Message-ID: <20060731235045.GE48182@wantadilla.lemis.com> In-Reply-To: <87530d2a0b64cbc84fbfd1a19eecbc0d@66.18.46.88> References: <87530d2a0b64cbc84fbfd1a19eecbc0d@66.18.46.88>
next in thread | previous in thread | raw e-mail | index | archive | help
--B0nZA57HJSoPbsHY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Monday, 31 July 2006 at 11:35:04 -0400, Erik Kristensen wrote: > > I have an interesting issue with FreeBSD 6.0 and MySQL 5.0. Part of > my problem has been discussed serveral times in the past on other > mailing lists and it seems there has been fixes for older versions of > MySQL. =46rom what you say here, there's no reason to believe that your problem has been mentioned at all. > The MySQL server is currently receiving a SIGNAL 10 about once an > hour, which is causing many problems with the innodb databases that > we have running on this server. Signal 10 is SIGBUS (bus error), an error detected by the hardware. The most frequent causes are bugs in the hardware and bugs in the software. The only way to find out what causes the problem is to investigate further. Never make the assumption that any two SIGBUS problems are related. Still, SIGBUS is interesting, because just about every such error in FreeBSD is reported as a SIGSEGV (signal 11). > I am running FreeBSD 6.0-RELEASE-p6 and MySQL 5.0.22. > > In all the lists I have read regarding FreeBSD, MySQL and signal 10, > it all seems to happen with version 6.0 and the 4.1.x series of > MySQL. I can't confirm that at all. I've been chasing a number of very specific problems for some time, and as far as I can tell, there are very few cases where the server crashes. One case that I'm investigating is BUG#12251 (http://bugs.mysql.com/bug.php?id=3D12251). If any of this looks familiar to you, please let me know. > Any help in this area would be greatly appreciate as this is our > production server having issues. We are a small company with limited > resources. A start would be the documented method to track down crashes: http://dev.mysql.com/doc/refman/5.0/en/debugging-server.html gives details. In particular, the contents of the error log will give you some idea, though probably you'll need a debugger to get a usable backtrace. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers. --B0nZA57HJSoPbsHY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEzpdVIubykFB6QiMRAl0iAJ9NPIqxNJNBpiODRGXZ5FLdiTIpagCff6br 1Ql6S7N4Mbau/qoPEN9uanE= =hcXb -----END PGP SIGNATURE----- --B0nZA57HJSoPbsHY--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060731235045.GE48182>