Migration from Centos 7 with Mariadb 10.5 to Ubuntu 20.04 with Mysql 8

WebSavvyGuy

• June 10, 2023 09:20

I have read that Ubuntu 20.04 comes installed with MYSQL 8 and Cpanel only supports that. My origin server is currently running Mariadb 10.5 (10.6 is the latest) and i plan to use the transfer tool to move each account to the new Ubuntu server with MYSQL 8. Will I have any issues with this? I am scared that MYSQL 8 will break things. Would love to hear any feedback. Thanks.

• 

  SimpleSonic

  • June 10, 2023 15:26

  You just need to refer to this:

  0
• 

  quietFinn

  • June 10, 2023 15:48

  Seems MariaDB is not supported if cPanel is installed in Ubuntu:

  0
• 

  WebSavvyGuy

  • June 10, 2023 15:49

  You just need to refer to this:

  0
• 

  quietFinn

  • June 10, 2023 15:56

  If you install AlmaLinux you must customize the installation as ResellerWiz told, by default MySQL is installed,

  0
• 

  mtindor

  • June 10, 2023 17:30

  I plan to use my hosts Cpanel/Ubuntu auto installer so i don't think i will have the option of choosing which version. Also, Cpanel does not support anything but Mysql 8 on Ubuntu so I do not want to lose that support. I am more looking for feedback for anyone who actually has done the switch and has had any impact. I am now leaning more towards installing AlmaLinux 8 just to avoid any further headaches.

  
  For what it's worth, I migrated two servers worth of Wordpress accounts and a few other PHP apps like older Joomla (about 250) from CloudLInux 6 ELS with MariaDB 10.3 - 10.5 to CloudLinux 8 with MySQL 8.0. What you should do is look at what sql_mode= on your MariaDB 10.5 server and then mimic that as best you can on the MySQL 8.0 server. MySQL 8.0 defaults with with sql_mode set to: ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION On each server run (as root): mysql mysql mysql> show variables like 'sql_mod%'; mysql> quit You'll see what the current sql_mode options are set to in the running MariaDB/MySQL servers. None of my MariaDB servers were running with STRICT_TRANS_TABLES or NO_ZERO_DATE or NO_ZERO_IN_DATE or ERROR_FOR_DIVISION_BY_ZERO So for some accounts I had issues with them after migrating them because the STRICT_TRANS_TABLES (and related options) were set on MySQL 8.0 but not on MariaDB 10.3 / 10.5. What I ended up doing on MySQL 8.0 was removing STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO I did that by adding the following to /etc/my.cnf and then doing a /scripts/restartsrv_mysql sql_mode=ONLY_FULL_GROUP_BY,NO_ENGINE_SUBSTITUTION You do things how you see fit. I'm just telling you what I did to avoid any issues with STRICT_TRANS_TABLES being enabled. If you have STRICT_TRANS_TABLES enabled on your MariaDB servers, then you will likely have zero issues. If you do not have STRICT_TRANS_TABLES enabled on your MariaDB servers, you probably want to set your sql_mode= in /etc/my.cnf on your MySQL 8.0 to look like mine before you start migrating accounts. mike

  0
• 

  vanessa

  • June 10, 2023 18:43

  I've moved a number of servers between MariaDB and MySQL 8 and haven't seen an issue. Do make note of the strict trans table issue in the previous message - that's the only gotcha I've seen so far.

  0

Please sign in to leave a comment.