Two issues with MySQL upgrade (mysql-5.6.21)

[zEitEr]

Hello,

That came to our attention, that:

1. File servers of Directadmin seem to be missing mysql-5.6.21-linux-x86_64.tar.gz:

--2014-11-28 08:20:26--  http://files2.directadmin.com/services/all/mysql/debian/64-bit/mysql-5.6.21-linux-x86_64.tar.gzResolving files2.directadmin.com (files2.directadmin.com)... 69.30.193.202
Connecting to files2.directadmin.com (files2.directadmin.com)|69.30.193.202|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2014-11-28 08:20:26 ERROR 404: Not Found.

2. Custombuild does not check either md5sum of the downloaded file or its size if to say about mysql:

gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now
./build: line 6930: cd: mysql: No such file or directory
chown: cannot access `/usr/local/mysql-5.6.21-linux-x86_64': No such file or directory
/etc/init.d/mysqld: line 27: cd: /usr/local/mysql: No such file or directory
Giving mysqld a few seconds to start up...
Restarting MySQL.

So what we have after failed upgrade of MySQL is that MySQL is completely down.

lrwxrwxrwx 1 mysql mysql 25 Nov 28 08:20 /usr/local/mysql -> mysql-5.6.21-linux-x86_64
-rw-r--r-- 1 root  staff  0 Nov 28 08:20 /usr/local/mysql-5.6.21-linux-x86_64.tar.gz

Thus please check correct mysql (5.6.x) version in versions.txt or make sure your servers have the file.
And before creating symlink please do a check to make sure a new directory exists (and/or file is not empty), and before restart of mysql please make sure symlink is OK.



Thank you.

 

[HighFly]

Correct! Same here.... MySQL completely failed.

How can i revert back to an earlier version?
Or (temporary) get files from an other filesX.directadmin.com server?

 

[zEitEr]

Try this:

rm -f /usr/local/mysql
ln -s /usr/local/mysql-5.6.12-linux-x86_64 /usr/local/mysql

and restart mysql.

 

[DirectAdmin Support]

MySQL never offered 5.6 tar.gz binaries for Debian. Bug in CB was that it didn't check for the empty file, where it should have done the compile.
I've added the fix to CustomBuild 2.0 to do the check:

                if [ ! -s "${MYSQLPACK}.tar.gz" ]; then
                        MYSQL_FORCE_COMPILE_OPT=yes
                fi

which basically falls back to doing the compile, as it should have in the first place.

John