MySQL 5.1 and openSUSE :: Michal Hrušecký

MySQL 5.1 and openSUSE

Some of you may already notice, that in Build Service, there are already available rpms for new MySQL 5.1. Currently I think that in openSUSE 11.2 will be some 5.1 version of MySQL. So it may be interesting to tell our users what will change and how. Most of these changes are reflected in README.SuSE, but frankly - who reads READMEs?

Changes

Plugins

One of the new features in MySQL 5.1 is support for plugins. So some of the storage engines will be now shipped like that. Following plugins will be available:

archive
blackhole
federated
example

As you can see, InnoDB will be still compiled as internal part of MySQL. If you are upgrading from version 5.0.X or if this is your first installation of MySQL 5.1, all plugins will be enabled by default and you can disable them manually later (see manual). All these plugins are installed by main mysql rpm so you don't need to install anything special. And if you don't like them, you can disable them easily and completely

With this change you need to remove skip-federated option from your my.cnf file if you have changed it manually. This option was there by default in previous versions of MySQL. But if you are installing MySQL for the first time or if you didn't touch your configuration file, everything should be ok.

File locations

There are going to be some changes in files locations too. Most of them was made in default configuration file so if you are experiencing problems and you have made some manual adjustments to your /etc/my.cnf, try to merge this file with /etc/my.cnf.rpmnew.

First of them is that mysql socket file and pid file were moved by default from /var/lib/mysql to more reasonable location ( /var/run/mysql ). Second change is that mysql log file is again back in /var/log. These changes should make MySQL more LSB friendly and help people with their MySQL administration. All these changes can be reverted by changing MySQL configuration file so if you don't like it, you can move them anywhere you want

BerkeleyDB

Other important change is that MySQL no longer contains BerkeleyDB as storage engine. There is no fix for that and if you used it before, you have to migrate your data to different storage engine.

MySQL Upgrade Log

Last thing you may find useful is that if you missed messages displayed during automatic MySQL database upgrade, you can find them from now on in /var/log/mysql_upgrade.log.

Summary

Just summarization of what you can expect. You wouldn't be able to use BerkeleyDB any longer. And if you are experiencing any problems, it's probably because you changed your configuration manually so solution is to replace /etc/my.cnf by /etc/my.cnf.rpmnew

miska | Thursday 28 May 2009 12:46am | openSUSE, MySQL | 5 comments

#1 Re: MySQL 5.1 and openSUSE

David C. Rankin, <E-Mail> / Friday 05 June 2009 10:23am

Dear Michal,

I am an openSuSE user and one of the first to have all of my web pages and database apps crater after updating to 5.1 with the socket and pid path changes.

It kills every single mysql install regardless of whether there have been any prior changes to /etc/my.cnf. I have a bug report open on the issue with novell as we speak.

Further, your information above is incorrect. I had made NO changes to my /etc/my.cnf file and the path changes you suggest trashed my database apps on openSuSE 10.3 through 11.1 servers. The sheer amount of downtime will be staggering.

Being more LSB Friendly does NOT justify crashing 100,000's of production systems. MySQL doesn't care if it is a little more, (or less), LSB friendly, but I guarantee you that the company owner forking over the cash to fix the crashes caused by the unneeded path changes certainly do.

[ Reply (2) ]

#1.1 Re: Re: MySQL 5.1 and openSUSE

Michal Hrušecký, <E-Mail> / Friday 05 June 2009 1:14pm

As stated on mailing list, using bleeding edge packages on production systems is IMHO bad idea.

With distribution configuration file MySQL works but you had to update settings in your already existing and configured applications using socket. Recently I moved socket file back to it's original location (/var/lib/mysql) for all older distributions. So it is in /var/run only for Factory currently.

[ Reply (0) ]

#1.2 Re: Re: MySQL 5.1 and openSUSE

wow gold, <> / Thursday 13 August 2009 12:04pm

Other important change is that MySQL no longer contains BerkeleyDB as storage engine. There is no fix for that and if you used it before, you have to migrate your data to different storage engine.

[ Reply (0) ]

#2 Re: MySQL 5.1 and openSUSE

aion power leveling, <E-Mail> / Wednesday 11 November 2009 8:20am

As in the mailing list, with advanced technology in production system is fettered bad idea.
Configuration files and distribution function of the works, but you must set already exists in your update and thecomponents use socket. I recently moved to the original document socket place for such/mysql) all the old distribution. So if only for factories.

[ Reply (0) ]