Issue with MariaDB and MySQL updates

S

Sempiterna

Verified User
Joined
Jun 21, 2014
Messages
21
Location
The Netherlands
1. On CentOS 7 with Custombuild 2, MariaDB gets installed. When I execute a minor version update of MariaDB using custombuild, it shows teh following:

package MariaDB-compat-5.5.41-1.el7.centos.x86_64 (which is newer than MariaDB-compat-5.5.41-1.el6.x86_64) is already installed
package MariaDB-common-5.5.41-1.el7.centos.x86_64 (which is newer than MariaDB-common-5.5.41-1.el6.x86_64) is already installed
package MariaDB-client-5.5.41-1.el7.centos.x86_64 (which is newer than MariaDB-client-5.5.41-1.el6.x86_64) is already installed
package MariaDB-server-5.5.41-1.el7.centos.x86_64 (which is newer than MariaDB-server-5.5.41-1.el6.x86_64) is already installed
package MariaDB-devel-5.5.41-1.el7.centos.x86_64 (which is newer than MariaDB-devel-5.5.41-1.el6.x86_64) is already installed
package MariaDB-shared-5.5.41-1.el7.centos.x86_64 (which is newer than MariaDB-shared-5.5.41-1.el6.x86_64) is already installed
mv: cannot stat '/etc/systemd/system/mysql.service': No such file or directory
Click to expand...

It seems MariaDB for CentOS 7 gets installed through CentOS 7 RPM's on new DirectAdmin installations, but subsequent updates come from CentOS 6 RPM's, which then also cause the systemd warning. Why install CentOS 6 RPM's when there are RPM's available for CentOS 7?

2. I'm used to rebuilding PHP after a MySQL upgrade to update the client API, but it seems that in Custombuild 2 (for both MariaDB and MySQL) the PHP rebuild has no effect. The API version stays at mysqlnd 5.0.11. Do we still need to rebuild PHP after MySQL gets upgraded to a newer major version?
 
It seems the RPMS are named wrong on files.directadmin.com
Code: 
http://files1.directadmin.com/services/all/mariadb/10.0/10.0.17/MariaDB-10.0.17-[B]centos7_0[/B]-x86_64-client.rpm
CustomBuild tries to use the correct path though
Code: 
http://files1.directadmin.com/services/all/mariadb/10.0/10.0.17/MariaDB-10.0.17-[B]centos7[/B]-x86_64-client.rpm
Also they seem to be 0 bytes for 10.0.17 and 5.5.42, probably because it retrieved the wrong file from mariadb.com as the filename changed with these versions.
 
Sempiterna said:
Is a PHP rebuild still required or advised after upgrading MySQL or MariaDB due to this change?
Click to expand...

No, you don't need to rebuild PHP anymore with CustomBuild 2.0 after MySQL/MariaDB updates/upgrades :)
 
Thanks for the report.
Looks like they changed the naming format from 5.x to 10.x.

I've fixed our downloader for 10.x and re-downloaded the correct files on files1.directadmin.com.
Allow 24 hours for rsync to other mirrors.

John
 
While the files are correct now on files1 to files5, on files 6 they are still 0 bytes and wrong filenames (http://files6.directadmin.com/services/all/mariadb/5.5/5.5.42/).

In addition I find the following oddities (or bugs?):

1. This may be a very recent change where in options.conf the mysql_inst option must either be: no, mysql or mariadb. On one of my CentOS 6 test servers, I tried to switch from mysql to mariadb by setting mysql_inst to "mariadb" and executing a ./build mysql. This is what happened:

Found /usr/local/directadmin/custombuild/mysql/MariaDB-10.0.17-centos5-x86_64-client.rpm
Found /usr/local/directadmin/custombuild/mysql/MariaDB-10.0.17-centos5-x86_64-devel.rpm
Found /usr/local/directadmin/custombuild/mysql/MariaDB-10.0.17-centos5-x86_64-server.rpm
Found /usr/local/directadmin/custombuild/mysql/MariaDB-10.0.17-centos5-x86_64-shared.rpm
Found /usr/local/directadmin/custombuild/mysql/MariaDB-10.0.17-centos5-x86_64-common.rpm
Found /usr/local/directadmin/custombuild/mysql/MariaDB-10.0.17-centos5-x86_64-compat.rpm
Stopping mysqld ...
Shutting down MySQL.. SUCCESS!
Upgrading MySQL 5.5 to MariaDB 10.0

Starting MariaDB was impossible. Maybe due to the fact that custombuild was installing CentOS 5 versions while i was running CentOS 6, or maybe that an upgrade from MySQL to MariaDB is simply not possible?

Also, the options.conf "mysql" version option no longer seems to work when mysql_inst is set to mariadb (i can enter any value i want without error). It is impossible to request an installation of MariaDB 5.5.

2. In my first question, MariaDB defaults to installing version 10. However, on my CentOS 7 testing server, which has MariaDB 5.5 installed, it is impossible to upgrade to version 10 because the mysql version option is no longer working. Is upgrading to version 10 implemented in custombuild?
 
Last edited:
Actually, after studying the bash code of 'build', I can answer my question nr 2 from my previous post. A new item was added called "mariadb" where either version 5.5 or 10.0 can be added. However, i did not notice it before, because the custombuild update added that one to the very bottom of the options.conf file :)
 
Sempiterna said:
1. This may be a very recent change where in options.conf the mysql_inst option must either be: no, mysql or mariadb. On one of my CentOS 6 test servers, I tried to switch from mysql to mariadb by setting mysql_inst to "mariadb" and executing a ./build mysql. This is what happened:

Found /usr/local/directadmin/custombuild/mysql/MariaDB-10.0.17-centos5-x86_64-client.rpm
Found /usr/local/directadmin/custombuild/mysql/MariaDB-10.0.17-centos5-x86_64-devel.rpm
Found /usr/local/directadmin/custombuild/mysql/MariaDB-10.0.17-centos5-x86_64-server.rpm
Found /usr/local/directadmin/custombuild/mysql/MariaDB-10.0.17-centos5-x86_64-shared.rpm
Found /usr/local/directadmin/custombuild/mysql/MariaDB-10.0.17-centos5-x86_64-common.rpm
Found /usr/local/directadmin/custombuild/mysql/MariaDB-10.0.17-centos5-x86_64-compat.rpm
Stopping mysqld ...
Shutting down MySQL.. SUCCESS!
Upgrading MySQL 5.5 to MariaDB 10.0

Starting MariaDB was impossible. Maybe due to the fact that custombuild was installing CentOS 5 versions while i was running CentOS 6, or maybe that an upgrade from MySQL to MariaDB is simply not possible?
Click to expand...

Please post the output of:
Code: 
/usr/local/directadmin/directadmin o

It must be a wrong OS set in the license. Please also check /var/lib/mysql/*err to see why MariaDB 10.0 is unable to start (likely custom /etc/my.cnf related).
 
Ah you're correct. It was indeed a wrong OS version that was set in the license. Thanks for pointing me to that direction :)

One small textual 'bug': During a './build mysql' of MariaDB 10.0 (no upgrade, just a minor update from 10.0.x to 10.0.17), the following is shown in the terminal:

"Upgrading MariaDB 10.0 to 5.5"

It's textual, because the build happens without errors, and the result is MariaDB 10.0.17.
 
Last edited:
Thank you for the repot. That should not happen anymore with CustomBuild 2.0 revision 1305.
 
You must log in or register to reply here.
Back
Top