Errors on fresh DA install with mariadb

tristan

Verified User
Joined
Feb 11, 2005
Messages
610
Location
The Netherlands
As long as nothing else leaks...

But if stopping mysql wasn't the problem maybe CB should stop allowing to upgrade MySQL to MariaDB?
 

Richard G

Verified User
Joined
Jul 6, 2008
Messages
6,499
Location
Maastricht
Nah, that's not a good idea imho. People like to change and it should be possible to migrate to MariaDB.
 

tristan

Verified User
Joined
Feb 11, 2005
Messages
610
Location
The Netherlands
Sure but if it results in corrupted tables it might be better to only offer fresh MariaDB installs where you import your backed-up databases afterwards.
 

Richard G

Verified User
Joined
Jul 6, 2008
Messages
6,499
Location
Maastricht
For us that is true, but there are still people who want to stay with Mysql. And maybe change there mind later....
Or maybe create a more foolproof solution so there will not be corrupted tables anymore. Like you said earlier, dump all, install Mariadb, import all.
However I think it's already working this way so i don't know where the errors come from then.
 

tristan

Verified User
Joined
Feb 11, 2005
Messages
610
Location
The Netherlands
There are a couple different sections about the conversion to MariaDB in that General MariaDB and MySQL docs page:

1. How to upgrade MySQL / MariaDB with CustomBuild 2.0
This one is documents the drop-in replacement and upgrade path which doesn't do a dump all, remove everything and build a clean MariaDB but just tries a drop-in replacement with the same files MySQL was using just running mysql_upgrade afterwards. It specifically lists this upgrade path: MySQL 5.5 > MariaDB 5.5 > MariaDB 10.0 > MariaDB 10.1 > MariaDB 10.2 > MariaDB 10.3. Nowadays though MySQL 5.7 is installed by default so I did the MySQL 5.7 > MariaDB 10.2 as suggested in the table.

2. Converting from MySQL 5.5 to MariaDB 5.5
This seems to do something similar but is written for CentOS specifically, adding a step of removing the system supplied MySQL?

3. How to reinstall mysql
This only mentions how to do a clean install, nothing about restoring the databases in there.

So all in all nothing that actually works for current fresh Debian installs at the moment, haven't tested this on anything else. That's why I think that documentation page should be updated to at least tell everybody a MySQL > MariaDB conversion is not going to work anymore unless you do a clean install of MariaDB.
 

Richard G

Verified User
Joined
Jul 6, 2008
Messages
6,499
Location
Maastricht
This one is documents the drop-in replacement and upgrade path which doesn't do a dump all,
Yes it does:
./build set mysql_backup yes
is stated in the description and..
If you have mysql_backup=yes set set in options.conf file then a full raw sql backup will be run prior to the upgrade.
However, it looks confusing, I would only use this to upgrade mysqsl -or- mariadb, not convert from mysql to mariadb.
I would certainly not use this procedure do to a conversion. If it indeed should not be used, then it would be wise if it would be mentioned specifically.

The title converting is at option 2.
adding a step of removing the system supplied MySQL?
No a lot more. Like also creating a better backup and taking care that mysql is stopped the correct way that DA won't start it automatically again. Also a backup of /var/lib/mysql is mentioned. I don't see that this would be only for Centos as also Debian/FreeBSD is mentioned.
This would be the correct conversion procedure.

3.) Yes the title says it all. Reinstall not convert.

to at least tell everybody a MySQL > MariaDB conversion is not going to work anymore unless you do a clean install of MariaDB.
Oke, but how does anybody running MySQL gets a part MariaDB? This can only appear if a conversion went wrong, and then you have a problem anyway. So I don't understand this one completely.
 

ikkeben

Verified User
Joined
May 22, 2014
Messages
1,104
Location
Netherlands Germany
Personally i find wrong conversions or updates.
There should be a more safe proces then only own backups

So kind of extra copy / backup and reverse possibility before doing this, then after testing and all is ok, the possible delete from those.

Such also build in install procedure where things go wrong.

You can test upfront but you can't test all from all as SERVER ADMIN, other software devs...
Backups and restore yes you can, and backups should be there.
But still more easy (semi- automatic ) procedures could help here, and is way more friendly.

OYEA updates if info's about some important precautions should be also easier to find here in support Forum, help. ( and howto's about solving such if doing wrong)
And in Custombuild under the I (info ?) where some are but not enough or am i wrong here?

To have a better Customer experience for DA ofcourse. ;)

Yes one is Server Admin, but there are Server Admin who need / want a CP to get things done for them as easy as possible, else wherefore is a CP?
Command line and such ok ofcourse, but why if you can solve in CP and build such in the CP, example for updates going wrong or conversions i think some more could be done or? ( extra safe backup parts and scripts to solve most common also the help / info with the basic changes and precautions for software update / conversion under that one CP is very handy and friendly)

Lets say for future build in some and more AI, and make whith that AI kind of as "MANAGED" DA ? :love:
 
Last edited:

tristan

Verified User
Joined
Feb 11, 2005
Messages
610
Location
The Netherlands
No a lot more. Like also creating a better backup and taking care that mysql is stopped the correct way that DA won't start it automatically again. Also a backup of /var/lib/mysql is mentioned. I don't see that this would be only for Centos as also Debian/FreeBSD is mentioned.
This would be the correct conversion procedure.
That section also mentions RPM so that's a bit difficult in Debian. Anyway if this is the only correct conversion procedure it should be made clear in the docs that the How to upgrade MySQL / MariaDB with CustomBuild 2.0 section isn't the correct conversion procedure as this isn't obvious at all now because they have that "Drop-in replacement and upgrade path is following:" stuff in that section as well.
 
Top