MySQL 5.5.30

February 5, 2013 · Guillaume Plessis

Packages of MySQL 5.5.30 are now available for Debian 6.0 “Squeeze” on both amd64 and i386 architectures. They fixes some InnoDB-, partition- and replication-related issues and some more bugs. And a new configuration directive, called innodb_print_all_deadlocks, has been backported from MySQL 5.6.

Please note that the Pinba engine has also been rebuilt to be used against this new version.

As usual, please read carefully the full Changelog before upgrading.

Kissifrot February 5, 2013
Are there plans for MySQL 5.6?
- Guillaume Plessis February 5, 2013
  @Kissifrot : from my experience, MySQL 5.6 as GA does not mean it’s ready for production. I think we’ll have to wait some more weeks/months before having a stable server.
  http://blog.mariadb.org/unbreakable-mysql/
  Waiting this, I’m really wondering about maintaining the Oracle branch of MySQL. I agree that :
  - it's the reference code
  - users trust it
  - switching to another name (MariaDB/Percona Server/whatever...) could be confusing.
  But Oracle policy about security fixes (see : http://www.oracle.com/us/support/assurance/fixing-policies/index.html) is really pissing me off. I also keep an eye on Debian's moves about MySQL/MariaDB.
  You’ll have news as soon as possible.
  - Tim February 5, 2013
    @Guillaume: I agree with your points, their security policy is very bad. Would it be a problem to support oracles branch and MariaDB? Or is this to complex/take to much time?
    - Guillaume Plessis February 5, 2013
      @Tim : it would require too much of my time, I guess. And it may be a bit confusing for the user.
      Debian talked about providing a mysql-common package that could be used whatever the Oracle/Percona/MariaDB flavour they would provide too. But I think that it would lead to too much compatibility problems. And there wasn’t any progress about it.
      http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565308 http://anonscm.debian.org/viewvc/pkg-mysql/mysql-5.6/
      - Tim February 5, 2013
        Yeah, I think the only way that users are not confused is to support it in another separate repo like your PHP 5.4. But I also understand that this require many of your time. So I hope Debian will find a solution, that is fine for all users. Personally I’d like to try MariaDB but only with offical support from Debian/Dotdeb.
Tomas Varil February 6, 2013
Hello there, I am running wheezy with your repositories currently PHP 5.3.21, today I upgraded to MySQL 5.5.30. I would like to upgrade to php 5.4.11 but I have noticed that php5-mysql (v5.4.11) package depends in libmysqlclient16, which is a package from squeeze but wheezy installs libmysqlclient18 by default.
During the upgrade proces of MySQL 5.5.30 I have noticed that it also installs never version of libmysqlclient18 from the dotdeb repositories. So is there any chance that php5-mysql (v5.4.11) package will work with this new libmysqlclient18? Which would finaly allow upgrade to PHP 5.4.X on wheezy without any issues?
- Guillaume Plessis February 6, 2013
  @Thomas Varil : nope, php5-mysql depends on the libmysqlclient that it has been built against : libmysqlclient16 in this case, for compatibility/stability concerns.
  If you want to avoid installing libmysqlclient16, you’ll prefer php5-mysqlnd instead of php5-mysql.
Frank February 6, 2013
During the updated to the latest mysql version from dotdeb I get the following errors.
Stopping MySQL database server: mysqld. insserv: warning: script ‘S99nagios’ missing LSB tags and overrides insserv: warning: script ’nagios’ missing LSB tags and overrides insserv: There is a loop at service rmnologin if started insserv: There is a loop between service rmnologin and mountnfs if started insserv: loop involving service mountnfs at depth 6 insserv: loop involving service networking at depth 5 insserv: There is a loop between service rmnologin and mountall if started insserv: loop involving service mountall at depth 4 insserv: loop involving service checkfs at depth 3 insserv: loop involving service quota at depth 8 insserv: There is a loop between service rmnologin and udev if started insserv: loop involving service udev at depth 1 insserv: There is a loop at service nagios if started insserv: There is a loop between service rmnologin and checkroot if started insserv: loop involving service checkroot at depth 2 insserv: loop involving service keyboard-setup at depth 1 insserv: Starting nagios depends on rmnologin and therefore on system facility $all' which can not be true! ... insserv: Max recursions depth 99 reached insserv: loop involving service courier-pop at depth 1 insserv: Starting nagios depends on rmnologin and therefore on system facility $all’ which can not be true! … insserv: Starting nagios depends on rmnologin and therefore on system facility $all' which can not be true! insserv: loop involving service urandom at depth 9 insserv: There is a loop between service rmnologin and hostname if started insserv: loop involving service hostname at depth 4 insserv: loop involving service bootlogd at depth 3 insserv: loop involving service hwclockfirst at depth 3 insserv: There is a loop between service rmnologin and ifupdown-clean if started insserv: loop involving service ifupdown-clean at depth 5 insserv: loop involving service mountkernfs at depth 1 insserv: Starting nagios depends on rmnologin and therefore on system facility $all’ which can not be true! … insserv: Starting nagios depends on rmnologin and therefore on system facility $all' which can not be true! insserv: loop involving service mountnfs-bootclean at depth 9 insserv: There is a loop between service rmnologin and mountoverflowtmp if started insserv: loop involving service mountoverflowtmp at depth 10 insserv: loop involving service mountall-bootclean at depth 9 insserv: Starting nagios depends on rmnologin and therefore on system facility $all’ which can not be true! … insserv: Starting nagios depends on rmnologin and therefore on system facility `$all’ which can not be true! insserv: There is a loop between service rmnologin and bootlogd if started insserv: exiting now without changing boot order! update-rc.d: error: insserv rejected the script header dpkg: error processing mysql-server-5.5 (–configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of mysql-server: mysql-server depends on mysql-server-5.5; however: Package mysql-server-5.5 is not configured yet. configured to not write apport reports configured to not write apport reports dpkg: error processing mysql-server (–configure): dependency problems - leaving unconfigured Setting up partimage (0.6.8-1+b1) … Errors were encountered while processing: mysql-server-5.5 mysql-server E: Sub-process /usr/bin/dpkg returned an error code (1)
- Frank February 6, 2013
  First think then wrote.
  It was my fault. Sorry for that.
  @Guillaume: You make a great job. Thank you for that.
Sander February 9, 2013
You’re doing an amazing job for many years already, Guillaume… but seriously, adding MariaDB to DotDeb would be the best thing since the invention of empty paper bags.
lyp February 18, 2013
/etc/mysql/my.cnf add lower_case_table_names=1
restart mysql
Invalid why？
- Guillaume Plessis February 18, 2013
  @lyp : it works on MySQL 5.5.30 packages from Dotdeb. Be sure to put this directive in the [mysqld] section.
  - lyp February 18, 2013
    O.M.G [Mysqld] section. I was doing.Failure
    - lyp February 18, 2013
      He is a read-only variables.In mysql5.5
Agga Memnon February 25, 2013
Please stop distributing vuln code! The mysql version distributed here is not good! Yes yes yes - KICK oracle code and add mariadb to this repo, please. it was clear that mysql will die the day oracle ate it, so now please face the consequences. There WILL be lot of pain while many users do not follow the details, but kicking mysql and switching to mariadb as fast as possible will give even more pain in future, so better do it quick now and hope ion 2014 we will all laugh about oracle.
If we stay with mysqldb we only support their stategy to destroy open source, so get rid of oracle code asap!
Alex March 12, 2013
After upgrade when i try to do:
server:/var/log# /etc/init.d/mysql start server:/var/log#
It doesn’t do anything. Can you please help? Using debian 6.
Alex March 12, 2013
Setting up mysql-server-core-5.5 (5.5.30-1~~dotdeb.0) … Setting up mysql-server-5.5 (5.5.30-1~~dotdeb.0) … Installing new version of config file /etc/mysql/debian-start … Installing new version of config file /etc/init.d/mysql … Installing new version of config file /etc/logrotate.d/mysql-server … Stopping MySQL database server: mysqld. Starting MySQL database server: mysqld . . . . . . . . . . . . . . failed! invoke-rc.d: initscript mysql, action “start” failed. dpkg: error processing mysql-server-5.5 (–configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of mysql-server: mysql-server depends on mysql-server-5.5; however: Package mysql-server-5.5 is not configured yet. dpkg: error processing mysql-server (–configure): dependency problems - leaving unconfigured configured to not write apport reports configured to not write apport reports Errors were encountered while processing: mysql-server-5.5 mysql-server E: Sub-process /usr/bin/dpkg returned an error code (1)
- Guillaume Plessis March 12, 2013
  @Alex : take a look at /var/log/syslog, it will explain why MySQL fails starting.
Kenn Ejima March 19, 2013
It’s been 40 days since the last update - any updates on the MySQL 5.6 plan? I’d really like to see it soon on dotdeb!
- Guillaume Plessis March 19, 2013
  @Kenn Ejima : the latest MySQL 5.5 version is 5.5.30 (do you really want to upgrade your database server more often?).
  About MySQL 5.6, see the comments above.
Andreas March 19, 2013
Maybe interesting for someone looking for 5.6: Percona plan to release their version 5.6 (based on MySQL 5.6) end of April (see comment at http://www.mysqlperformanceblog.com/2012/09/13/announcing-percona-server-5-6-6-60-1-alpha/ ).
At the moment Percona Server 5.6 is still Alpha (based on MySQL 5.6.10). http://www.mysqlperformanceblog.com/2013/03/14/announcing-percona-server-for-mysql-5-6-10-60-2/
Percona also maintains an apt repository: http://www.percona.com/doc/percona-server/5.5/installation/apt_repo.html (note: link is for 5.5). So most likely it will be quite easy to get 5.6 running on debian/ubuntu - at least in Percona flavour.
Steve May 2, 2013
Is 5.5.31 in the pipeline yet? I ask with absolutely respect and hope I don’t sound too demanding but I’ve noticed that normally you package upstream releases within a few days of release. Have come across a bug in 5.5.30 and think it’s fixed in 5.5.31 and would like to continue using your packages if possible.
- Guillaume Plessis May 2, 2013
  @Steve : I’ll work on MySQL 5.5.31 for Squeeze in the next few days. But I won’t maintain 5.5 for Wheezy (it’s available in 5.5.30 version, maintained by Debian). Just be aware of that that before upgrading your Squeeze.
  - Andreas May 13, 2013
    FYI wheezy is now on 5.5.31 http://www.debian.org/security/2013/dsa-2667
    Several issues have been discovered in the MySQL database server. The vulnerabilities are addressed by upgrading MySQL to a new upstream version, 5.5.31, which includes additional changes, such as performance improvements and corrections for data loss defects. For the stable distribution (wheezy), these problems have been fixed in version 5.5.31+dfsg-0+wheezy1.
    - Guillaume Plessis May 13, 2013
      @Andreas : I know that and this is my next move. But I spent a lot of time these days to support Wheezy and to release up-to-date packages of PHP 5.4.15/5.3.25 on Wheezy/Squeeze for amd64/i386. Thanks in advance for your patience and don’t hesitate to support Dotdeb.
      /donate/