MySQL 5.6

Looking forward to this too.
MariaDB support too would be a great addition.
 
We're currently working hard on getting DA 1.43.0 released.
Custombuild 2.0 is also being worked on.

Most likely, sometime after things settle down a bit, right now we're quite busy.

I'll also add that you might be able to just update with the usual means, eg: update the rpms, and run the mysql_upgrade.

John
 
You can give MySQL 5.6 a try with CustomBuild 2.0 now.
 
Hello,

Looking at dev.mysql.com, it appears that they don't offer pre-compiled debian tar.gz files.. on .deb files, which our configuration isn't setup for.
This might be a multi-step fix to get CB to compile a tar.gz.

Assuming you're using custombuild 2.0, can you run the following:
Code: 
cd /usr/local/directadmin/custombuild
./build update
./build compile_mysql_binary
which is was just added as an advanced command line option in CB 2.0, on files1.directadmin.com. (not for general use.. just for this case)

Once compiled, let us know what the tar.gz file is named, as the glibc extensions seem to be different with 5.6, eg:
Code: 
ls -la mysql*.tar.gz
and then we can add that in to CB to compile automatically, just like FreeBSD does already.

John
 
Hi John.

I have try it on a debian 6 64.

./build compile_mysql_binary

Extracting mysql-5.6.10.tar.gz ...
Cannot find cmake, please install it.
apt-get install cmake

then i have installed cmake

apt-get install cmake

Reading package lists... Done
Building dependency tree
Reading state information... Done
cmake is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

then i try again.
./build compile_mysql_binary
and get again:
Extracting mysql-5.6.10.tar.gz ...
Cannot find cmake, please install it.
apt-get install cmake
 
hi,
Could you tell me how to upgrade to mysql 5.6.
In options.conf, i should edit version value from 5.5 to 5.6?
thanks
 
:(, I try update to 5.6 but failed.
Now I am trying back to 5.5, it also fail. Please help me.

[root@csrv01 custombuild]# service mysqld restart
MySQL server PID file could not be found! [FAILED]
Starting MySQL.The server quit without updating PID file (/[FAILED]mysql/csrv01.osd.vn.pid).

[root@csrv01 custombuild]# tail /var/log/mysqld.log
InnoDB: Error: log file /var/lib/mysql/ib_logfile0 is of different size 0 35651584 bytes
InnoDB: than specified in the .cnf file 0 109051904 bytes!
130420 4:09:08 [ERROR] Plugin 'InnoDB' init function returned error.
130420 4:09:08 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
130420 4:09:08 [ERROR] Unknown/unsupported storage engine: InnoDB
130420 4:09:08 [ERROR] Aborting

130420 4:09:08 [Note] /usr/sbin/mysqld: Shutdown complete

130420 04:09:08 mysqld_safe mysqld from pid file /var/lib/mysql/csrv01.osd.vn.pid ended
 
Pay attention to this:

Code: 
InnoDB: Error: log file /var/lib/mysql/ib_logfile0 is of different size 0 35651584 bytes
 InnoDB: than specified in the .cnf file 0 109051904 bytes!

That's it.
 
If you use Query Cache, be careful when you upgrade to MySQL 5.6. It is turned off by default in 5.6. After I first upgraded, I found that my WAIT TIME was way higher than usual and the load average went up at least 3x.
 
I am testing with CB 2.0 RC4

Do you experience InnoDb is much slower in MySQL 5.6 ?
(not sure it is only in 5.6, or happened in 5.5/5.1)

I tried to export and import a blank-new Horde 5 database (~6.3 MiB database, 110 InnoDB tables, 319 records in total),
it takes the following time to complete 3 trial import of InnoDB database (with different my.cnf setting) -

2m9.301s (with my own /etc/my.cnf)
2m7.681s (remarked query cache in /etc/my.cnf , and restarted mysql)
2m5.453s (remove /etc/my.cnf, i.e. everything default, and restarted mysql)

--

If I change the engine from InnoDb to MyISAM (i.e. modified the mysqldump file),
it takes 0m6.110s to complete those 110 MyISAM tables.
 
You must log in or register to reply here.
Back
Top