[Mageia-dev] mariadb

Maarten Vanraes alien at rmail.be
Sun Dec 18 01:12:21 CET 2011


Op zondag 18 december 2011 01:06:19 schreef Maarten Vanraes:
> Op zondag 18 december 2011 00:36:36 schreef David W. Hodgins:
> > On Sat, 17 Dec 2011 11:10:29 -0500, Maarten Vanraes <alien at rmail.be> 
wrote:
> > > I mentioned that this library should be versioned, and that it's not at
> > > this time, he agreed, and said that since it's ABI compatible with
> > > mysqlclient, that he should not use 0 major, but the 18 major (same as
> > > mysqlclient)
> > > 
> > > the code is still 100% exactly the same, it just went from unversioned
> > > in upstream to versioned.
> > > 
> > > since we had versioned manually mysqld to major 0, i provided the
> > > compatibility symlinks for it.
> > 
> > I've now figured out why my cauldron install is locking up.
> > 
> > I managed to get htop running before it locked.  It showed swap usage
> > climbing.  I got it to sort by vmsize.  It showed mysqldb using over
> > 2.5GB MV, and 1.5GB ram, on my 2GB ram system.
> > 
> > Regards, Dave Hodgins
> 
> that is a lot of memory, do you have any mysqld logs? and also, for the
> record, you have mariadb installed?
> 
> can you check if you have the latest, if there is still a part of mysql
> installed?
> 
> what kind of databases do you have, and which ones were created by mariadb?
> what kind of load do you have? what app is querying mariadb? do you have a
> slow-queries mysql log file?
> 
> how big are the recent mysql-binlogs?
> 
> perhaps you can make a bug report, this would be easier to follow up on.

oh and were any mysql libraries still loaded? ie: programs linked to mysql, 
after upgrade?


More information about the Mageia-dev mailing list