SOLVED MySQL 5.7 to MySQL 8.0 Upgrade

[Rockforduk]

Hi Everyone,
I really want to upgrade MySQL 5.7 to MySQL 8.0 on my dedicated server, but i am worried about all the WordPress installations and plugin compatibility. What is the best way to do this please?

Thanks

Rockforduk

 

[andrew.n]

There are major changes introduced in MySQL 8.0 compared to 5.7 including the depreciation of the old SHA1 password encryption however as far as I know there is no WP plugin to the the compatibility check for you. WP if it's up to date it should be compatible though. When you are initiating the upgrade in WHM under MySQL upgrade the system will alert you for the major changes and show you if there is any account which uses the old password encryption method though.

 

[Rockforduk]

Thank you

There are major changes introduced in MySQL 8.0 compared to 5.7 including the depreciation of the old SHA1 password encryption however as far as I know there is no WP plugin to the the compatibility check for you. WP if it's up to date it should be compatible though. When you are initiating the upgrade in WHM under MySQL upgrade the system will alert you for the major changes and show you if there is any account which uses the old password encryption method though.

 

[Rockforduk]

Ok, so i have run the compatibility checker and have had a few of these warnings -

[mysqld]
default_authentication_plugin=mysql_native_password

However, the setting should be viewed as temporary, not as a long term or
permanent solution, because it causes new accounts created with the setting
in effect to forego the improved authentication security.
If you are using replication please take time to understand how the
authentication plugin changes may impact you.
More information:
MySQL :: MySQL 8.0 Reference Manual :: 2.11.4 Changes in MySQL 8.0
MySQL :: MySQL 8.0 Reference Manual :: 2.11.4 Changes in MySQL 8.0

Errors: 0
Warnings: 32700
Notices: 1

No fatal errors were found that would prevent an upgrade, but some potential issues were detected. Please ensure that the reported issues are not significant before upgrading.

Warnings

column has zero default value: 0000-00-00 00:00:00

column's default character set: utf8

Critical

MySQL enables "strict mode" by default as of version 5.7. Strict mode controls how MySQL handles invalid or missing values in data-change statements such as INSERT or UPDATE. Applications not built with strict mode enabled may cause undesired behavior; please verify applications using MySQL are compatible before upgrading. More information about strict mode is available here .

With the above warnings am i still good to go with upgrade?

Thanks

Rockforduk

 

[andrew.n]

You should be good to go, "strict_mode" could be easily disabled if necessary later on by editing /etc/my.cnf and adding this line:

sql_mode=""

then restart MySQL.

 

[Rockforduk]

Ok, just did my upgrade and have the following

Restarting mysql service.
Restart failed: timeout (196 seconds) reached! at /usr/local/cpanel/Cpanel/RestartSrv/Lock.pm line 37.
Mysql did not start up after upgrade; there may be a problem in /etc/my.cnf. at /usr/local/cpanel/Whostmgr/Mysql/Upgrade.pm line 802.
Obtained version information from system.
Proceeding with MySQL/MariaDB upgrade despite the following:
Normal: The selected MySQL version (8.0) is the same as the currently installed MySQL version (8.0). No upgrade will be performed at this time, though the normal upgrade steps will still be executed. This is only useful if a previous upgrade failed while partially completed.

 

[Rockforduk]

Ok, looks like it has all successfully upgraded. Thank you everyone

 

[andrew.n]

Happy to hear, enjoy