Date: Tue, 1 May 2007 10:12:03 -0400 (EDT) From: "Mike Jakubik" <mikej@rogers.com> To: "Ken Chen" <ken73.chen@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: mysql frequently crash on 6.2 Message-ID: <53892.209.47.38.69.1178028723.squirrel@wettoast.dyndns.org> In-Reply-To: <d018a9bd0704302358h1cb35046i2c4498fcb8fec5d7@mail.gmail.com> References: <d018a9bd0704301811n47a34e7ax457f527f083e49e0@mail.gmail.com> <20070501020721.GA44472@icarus.home.lan> <d018a9bd0704302358h1cb35046i2c4498fcb8fec5d7@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, May 1, 2007 2:58 am, Ken Chen wrote: > 2007/5/1, Jeremy Chadwick <koitsu@freebsd.org>: >> >> >> I can confirm this problem. Normally sig11 is an indication that you >> have hardware-related problems, but in this particular case (at least in >> my experience), it can also be caused by some lack-of loader.conf >> tunables permitting mysqld to allocate the amount of memory you're >> claiming in my.cnf. > > > Jeremy, thank you for your information.But I has modified > /boot/loader.conf > already, you can check the 'limits' output in my last post. > > The mysql run well on my other machine with low-loading, but at the > high-loading box. mysql always get 'mysqld got signal 11'. I've had problems with 6.2 and mysql on a large server as well. High CPU usage and crashes. I switched the threading library to libthr and the problems went away.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53892.209.47.38.69.1178028723.squirrel>