Date: Thu, 17 Jun 1999 13:01:38 -0400 (EDT) From: Troy Settle <st@i-Plus.net> To: Ilya Obshadko <ilya@zhurnal.ru> Cc: Juriy Goloveshkin <j@avias.com>, freebsd-stable@FreeBSD.ORG Subject: Re: Re[2]: mysql problems after upgrading to 3.2-stable Message-ID: <Pine.BSF.4.10.9906171259230.25271-100000@rio.i-plus.net> In-Reply-To: <Pine.BSF.4.05.9906171543090.5805-100000@xfire.polit.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 17 Jun 1999, Ilya Obshadko wrote: > On Thu, 17 Jun 1999, Juriy Goloveshkin wrote: > > > >> > I've cvsupped my source tree to 3.2-stable, rebuilt the system and after > > >> > that I encounter a lot of problems with mysql. The performance has become > > >> > lower, and there are repeaded segmentation faults. Rebuilding mysql > > >> > doesn't help. System is FreeBSD 3.2-STABLE SMP, Dual P-II-333. > > >> When did you perform the cvsup? There was some problems in the > > >> threads library right around 3.2-release that you may have grabbed.. > > IO> I've cvsupped 3.2-stable at June 9. Is it fixed already? > > At the present moment in both branches libc_r is spoiled. > > But I know about fixes, which were made by Dan Eischen. > > With them mysql again works normally. > > I don't know why these changes haven't yet commited.... > > Maybe there's a chance to get update before it will be committed? There's > a lot of performance troubles on our production server after upgrading to > 3.2-STABLE... :( > Oh crap... I totally forgot that I had problems with MySQL when going to 3.2-STABLE. The solution was to simply build mysql from the port. I didn't look too deeply into it, but mysql has been up and running for 3 weeks without problem now. Hope this helps someone in need. -- Troy Settle <st@i-Plus.net> iPlus Internet Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9906171259230.25271-100000>