Date: Wed, 16 Feb 2005 15:06:43 -0800 From: Sean Chittenden <sean@chittenden.org> To: Sean Chittenden <sean@gigave.com> Cc: threads@FreeBSD.org Subject: Re: Strange backtrace from amd64 + mysqld... Message-ID: <f4bcd580f482f0ef768ab95d7af66b88@chittenden.org> In-Reply-To: <20050211001252.GY1060@sean.gigave.com> References: <20050211001252.GY1060@sean.gigave.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Howdy. I'm running into a strange issue with MySQL 4.1.9 wherein its > eating itself every 24hrs. I grabbed a back trace, but haven't > recompiled MySQL with debugging given the strangeness of the backtrace > (can't tell if this is gdb or if the call stack is massively corrupt > due to some error). Given I've watched this repeat itself a few times > now and it seems to be dying in a pthread call, I'm posting here. > MySQL is the only process having problems, but it's also the most > heavily threaded and is getting pounded pretty hard. Without going > back to MySQL (esp given the backtrace), I want to verify that this > isn't a pthreads issue. Can someone comment on whether or not they've > seen this before? Out of desperation, I recompiled MySQL with system scoped threads instead of process scoped threads and MySQL has been running as well as MySQL runs. Seems as though there's some locking issue that gets exposed with process scoped threads vs. system scoped threads. Regardless, for those dropping in, MySQL should be used with system scoped threads if you're experiencing any abnormal MySQL instability (I'm also not sure if this is an amd64 specific issue or not). -sc -- Sean Chittenden
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f4bcd580f482f0ef768ab95d7af66b88>