MySQL 5.6.21 has been released on September 23rd, 2014, fixing 24 security issues and various bugs affecting previous versions.
Please read the full Changelog fore more details.
The corresponding packages are now available for Debian 7 “Wheezy”, on both amd64 and i386 architectures.
Note : Some people reported having difficulties upgrading from 5.6.19 to 5.6.21. If this is your case, prefer using apt-get dist-upgrade (or equivalent) instead of apt-get upgrade.
40 replies on “MySQL 5.6.21 for Wheezy”
Your package seems to do not work, the mysql and libs stay to 5.6.19. We have changed nothing on the different servers.
similar here
The following packages will be upgraded:
libmysqlclient18 mysql-client mysql-common mysql-server
The following packages are RECOMMENDED but will NOT be installed:
mysql-common-5.6
4 packages upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
Same here too.
mysql-server-5.6 : Dépend: mysql-server-core-5.6 (= 5.6.19-1~dotdeb.1) mais 5.6.21-1~dotdeb.1 est installé
Same bug… mysql-server dépend de mysql-server-5.6 ; cependant :
Le paquet mysql-server-5.6 n’est pas encore configuré.
Guys, I’m still investigating what is your issue with these new packages (I did succeed upgrading my own machines before releasing 5.6.21). I’ll find a fix very soon and keep you posted.
Thanks, waiting for your new release.
Could you please help me by taking a look at /var/log/mysql/error.log or /var/log/syslog, tell me if something specific to MySQL went wrong during the upgrade?
Paste the result in a gist. Your help is greatly appreciated.
No error for me, the upgrade was successful. But, after the upgrade, the library stayed at version 5.6.19 and it was the same of the server (even if I restart MySQL for the server).
As far as I can see, at least for me, this is stricly a dependancy error.
It tells me I have some dependancies not satisfied:
mysql-server-5-6 depends on mysql-server-core-5.6 (= 5.6.19-1~dotdeb.1) But 5.6.21-1~dotdeb.1 is installed.
It won’t upgrade anything
Confirmed. Even if the upgrade process finishes with no errors, I still have 5.6.19. Phpmyadmin reads:
Server version: 5.6.19-1~dotdeb.1 – (Debian)
Database client version: libmysql – 5.6.19.
My apt-get log:
——-
Log started: 2014-10-29 12:33:14
(Reading database … 20696 files and directories currently installed.)
Preparing to replace mysql-common 5.6.19-1~dotdeb.1 (using …/mysql-common_5.6.21-1~dotdeb.1_all.deb) …
Unpacking replacement mysql-common …
Preparing to replace libmysqlclient18:i386 5.6.19-1~dotdeb.1 (using …/libmysqlclient18_5.6.21-1~dotdeb.1_i386.deb) …
Unpacking replacement libmysqlclient18:i386 …
Preparing to replace mysql-client 5.6.19-1~dotdeb.1 (using …/mysql-client_5.6.21-1~dotdeb.1_all.deb) …
Unpacking replacement mysql-client …
Preparing to replace mysql-client-core-5.6 5.6.19-1~dotdeb.1 (using …/mysql-client-core-5.6_5.6.21-1~dotdeb.1_i386.deb) …
Unpacking replacement mysql-client-core-5.6 …
Preparing to replace mysql-server 5.6.19-1~dotdeb.1 (using …/mysql-server_5.6.21-1~dotdeb.1_all.deb) …
Unpacking replacement mysql-server …
Processing triggers for man-db …
Setting up mysql-common (5.6.21-1~dotdeb.1) …
Installing new version of config file /etc/mysql/my.cnf …
Setting up libmysqlclient18:i386 (5.6.21-1~dotdeb.1) …
Setting up mysql-client (5.6.21-1~dotdeb.1) …
Setting up mysql-client-core-5.6 (5.6.21-1~dotdeb.1) …
Setting up mysql-server (5.6.21-1~dotdeb.1) …
Log ended: 2014-10-29 12:33:24
——
BTW: apt-get upgrade show that such packages were upgraded but others were keeped at current version (didn’t remeber exactly since I erased that part of the log)
following my previous comment, apt-get upgrade says:
The following packages have been kept back:
mysql-client-5.6 mysql-server-5.6 mysql-server-core-5.6
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
Could you guys please send me the result of dpkg -l '*mysql*' | grep '^.i' ?
ii libdbd-mysql-perl 4.021-1+b1 i386 Perl5 database interface to the MySQL database
ii libmysqlclient18:i386 5.6.21-1~dotdeb.1 i386 MySQL database client library
ii mysql-client 5.6.21-1~dotdeb.1 all MySQL database client (metapackage depending on the latest version)
ii mysql-client-5.6 5.6.19-1~dotdeb.1 i386 MySQL database client binaries
ii mysql-client-core-5.6 5.6.21-1~dotdeb.1 i386 MySQL database core client binaries
ii mysql-common 5.6.21-1~dotdeb.1 all MySQL database common files, e.g. /etc/mysql/my.cnf
ii mysql-server 5.6.21-1~dotdeb.1 all MySQL database server (metapackage depending on the latest version)
ii mysql-server-5.6 5.6.19-1~dotdeb.1 i386 MySQL database server binaries and system database setup
ii mysql-server-core-5.6 5.6.19-1~dotdeb.1 i386 MySQL database server binaries
ii php5-mysql 5.5.18-1~dotdeb.1 i386 MySQL module for php5
ii python-mysqldb 1.2.3-2 i386 Python interface to MySQL
I’ve just upgraded via aptitude upgrade. All works fine:
5.6.21-1~dotdeb.1-log
@skp : Thank you. As mentioned by Plazik, could you please check if aptitude upgrade does a better job?
ii libdbd-mysql-perl 4.021-1+b1 i386 Perl5 database interface to the MySQL database
ii libmysql++-dev 3.1.0-2+b1 i386 MySQL C++ library bindings (development)
ii libmysql++3 3.1.0-2+b1 i386 MySQL C++ library bindings (runtime)
ii libmysqlclient15-dev 5.0.51a-24+lenny5 i386 MySQL database development files
ii libmysqlclient15off 5.0.51a-24+lenny5 i386 MySQL database client library
ii libmysqlclient18:i386 5.6.19-1~dotdeb.1 i386 MySQL database client library
ii mysql-client-5.5 5.5.40-0+wheezy1 i386 MySQL database client binaries
ii mysql-client-5.6 5.6.19-1~dotdeb.1 i386 MySQL database client binaries
ii mysql-client-core-5.6 5.6.19-1~dotdeb.1 i386 MySQL database core client binaries
ii mysql-common 5.6.21-1~dotdeb.1 all MySQL database common files, e.g. /etc/mysql/my.cnf
ii mysql-server 5.6.21-1~dotdeb.1 all MySQL database server (metapackage depending on the latest version)
ii mysql-server-5.6 5.6.19-1~dotdeb.1 i386 MySQL database server binaries and system database setup
ii mysql-server-core-5.6 5.6.19-1~dotdeb.1 i386 MySQL database server binaries
ii php5-mysql 5.4.34-1~dotdeb.1 i386 MySQL module for php5
ii python-mysqldb 1.2.3-2 i386 Python interface to MySQL
“apt-get dist-upgrade” installs the three packages that are held back when doing “apt-get upgrade”.
Accourding to Ralph’s comment, apt-get dist-upgrade seems to solve the dependency problem. Do you guys confirm? If so, I’ll add a note on the blog post.
Seems to work for both: lib and server.
apt-get dist-upgrade seems to solve the “problem” (any explanation why ? 🙂 ). Below the results:
ii libdbd-mysql-perl 4.021-1+b1 i386 Perl5 database interface to the MySQL database
ii libmysqlclient18:i386 5.6.21-1~dotdeb.1 i386 MySQL database client library
ii mysql-client 5.6.21-1~dotdeb.1 all MySQL database client (metapackage depending on the latest version)
ii mysql-client-5.6 5.6.21-1~dotdeb.1 i386 MySQL database client binaries
ii mysql-client-core-5.6 5.6.21-1~dotdeb.1 i386 MySQL database core client binaries
ii mysql-common 5.6.21-1~dotdeb.1 all MySQL database common files, e.g. /etc/mysql/my.cnf
ii mysql-server 5.6.21-1~dotdeb.1 all MySQL database server (metapackage depending on the latest version)
ii mysql-server-5.6 5.6.21-1~dotdeb.1 i386 MySQL database server binaries and system database setup
ii mysql-server-core-5.6 5.6.21-1~dotdeb.1 i386 MySQL database server binaries
ii php5-mysql 5.5.18-1~dotdeb.1 i386 MySQL module for php5
ii python-mysqldb 1.2.3-2 i386 Python interface to MySQL
World for me (but stil the symlink problem for the data directory, fixed like I did during the last update)
Thanks for your work.
I just used “apt-get install mysql-server” after receiving the upgrade bug and it fixed the problem aswell (just had to reenter/reset the root password).
I tried apt-get dist-upgrade and am getting this result:
apt-get dist-upgrade -u
Reading package lists… Done
Building dependency tree
Reading state information… Done
Calculating upgrade… Done
The following NEW packages will be installed:
mysql-common-5.6
The following packages will be upgraded:
mysql-client mysql-server mysql-server-5.6 mysql-server-core-5.6
4 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
6 not fully installed or removed.
Need to get 0 B/22.0 MB of archives.
After this operation, 4610 kB disk space will be freed.
Do you want to continue [Y/n]?
Y =>
Unpacking replacement mysql-client-5.6 …
Processing triggers for man-db …
Use of uninitialized value in concatenation (.) or string at /usr/share/perl5/Debconf/DbDriver/File.pm line 44, chunk 3.
Use of uninitialized value in -e at /usr/share/perl5/Debconf/DbDriver/File.pm line 46, chunk 3.
Use of uninitialized value in pattern match (m//) at /usr/share/perl5/Debconf/DbDriver/File.pm line 47, chunk 3.
Use of uninitialized value $directory in -d at /usr/share/perl5/Debconf/DbDriver/File.pm line 48, chunk 3.
Use of uninitialized value $directory in concatenation (.) or string at /usr/share/perl5/Debconf/DbDriver/File.pm line 49, chunk 3.
debconf: DbDriver “config”: mkdir :No such file or directory
dpkg: error processing man-db (–unpack):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
man-db
E: Sub-process /usr/bin/dpkg returned an error code (1)
oot@server:~# dpkg -l ‘*mysql*’ | grep ‘^.i’
ii libdbd-mysql-perl 4.021-1+b1 amd64 Perl5 database interface to the MySQL database
ii mysql-client 5.6.19-1~dotdeb.1 all MySQL database client (metapackage depending on the latest version)
ii mysql-server 5.6.19-1~dotdeb.1 all MySQL database server (metapackage depending on the latest version)
ii mysql-server-5.6 5.6.19-1~dotdeb.1 amd64 MySQL database server binaries and system database setup
ii mysql-server-core-5.6 5.6.19-1~dotdeb.1 amd64 MySQL database server binaries
ii mysqltuner 1.2.0-1 all high-performance MySQL tuning script
ii php5-mysqlnd 5.4.34-1~dotdeb.1 amd64 MySQL module for php5 (Native Driver)
This wheezy mysql 5.6.21 upgrade worked fine for me using “aptitude full-upgrade”
Aptitude shows me no upgrade possibility to MySQL 5.6.21 at all.
I am using http://packages.dotdeb.org wheezy-php55 all
My statement was wrong. Caching effect ;).
@Ovidiu : something goes wrong while processing the man pages, maybe because of the debconf cache. Could you please check that the /var/cache/debconf/ directory exists on your system. If the problem still occurs, please try to run dpkg-reconfigure -phigh -a. It looks it solved similar problems.
to correctly update I had to
apt-get update
apt-get dist-upgrade
apt-get install mysql-server
(which was uninstalled by dist upgrade and prevented upgrade of packages mysql-server and mysql-server-core)
This on a fresh debian install.
That /var/cache/debconf folder didn’T exist, I created it and then apt-get dist-upgrade went smooth. Thanks for the help!
For me:
aptitude upgrade
works fine!
Upgrading worked fine for me with dist-upgrade
But now after upgrade my CPU utilization went through the roof. It maxed out at 100% so I had to increase the number of cores, now two cores at 70%.
I look at my Munin stats and it seems like at the same time the CPU went to 100% the number of mysql queries just increased dramtically.
This happend just a few hours after I upgraded mysql on my server. Any idea for why that is or how I could solve it?
Running top or ps aux show almost no use of the CPU what so ever.
On closer investigation it actually seems to have been a DOS-attack, not DDOS though.
I upgraded MySql from 5.5 to 5.6.21 using your repository on Ubuntu 12.04. Started it via Webmin, seems to be working fine. Those who can’t upgrade, try to run apt-get install for each held-back package (I had to run it 3 times in order to perform the upgrade). So far so good. Thank you for providing this package and keep up to good work.
I had fatal problems on two PCs with Debian Wheezy after clean upgrade over 5.6.19. The problems where somehow related to the slave thread but I am not sure. Both machines are running slave threads connected to two 5.6.21 masters Win64PCs with that run smoothly. One of the slaves entered infinite loop of restarting with “Got signal 11” message. The second after few days got “segmentation fault”. So I had to revert both to 5.6.19. The binary loging mode is “mixed”. Any idea about such kind of problems?
I also use BOA for drupal sites, and they have switched to mariaDB 10, and state that it offers significant improvements over mysql. Can you comment on this, and if so, have you considered packaging mariadb 10+ Guillaume? Thanks for your great work on mysql and php and redis, etc.
@Ed : I have package of MariaDB 10.0, but I need to refresh them and to test them extensively before releasing them. Thanks for your patience.
My statement was wrong too. After carefull upgrade ( stop of the masters before upgrading the slaves ) everything looks fine. Thanks for this release!
Thanks for update!
+1 for apt-get dist-upgrade
Just in case someone else had problems with replication after upgrade to 5.6.21.
See that link:
http://forums.mysql.com/read.php?26,621717,623367#msg-623367
ulimit ‘open files’ and MySQL ‘open_files_limit’ …
How to set permanently the limit of open files and MySQL open_files_limit but i set the limit in my.cnf and limits.conf but after restart server the limit is restored to default 1024.
Thanks you.