Comments - Upgrade from 10.5.x to 10.6.x mysql_upgrade or mariadb-upgrade not working

2 years, 1 month ago Rob Rutledge

Here is the output after upgrade:

[code]

  1. mysql --version mysql Ver 15.1 Distrib 10.6.7-MariaDB, for Linux (x86_64) using readline 5.1
  1. mariadb-upgrade -p Enter password: Major version upgrade detected from 10.5.13-MariaDB to 10.6.7-MariaDB. Check required! Error: Server version (10.5.13-MariaDB) does not match with the version of the server (10.6.7-MariaDB) with which this program was built/distributed. You can use --skip-version-check to skip this check. FATAL ERROR: Upgrade failed
  2. mysql_upgrade -p Enter password: Major version upgrade detected from 10.5.13-MariaDB to 10.6.7-MariaDB. Check required! Error: Server version (10.5.13-MariaDB) does not match with the version of the server (10.6.7-MariaDB) with which this program was built/distributed. You can use --skip-version-check to skip this check. FATAL ERROR: Upgrade failed

[/code]

My main concern is that I would not be able to run mythtv if the mariadb upgrade was not successful. Mythtv does start now and I can play recorded shows, but I cannot set up new recordings -- I get a message that "could not start recording". The last time I tried to make this upgrade from 10.5.x to 10.6.x it became apparent that "Offset" is a reserved word now for MariaDB 10.6.x and I believe this word is used to set up the duration of the recordings. Will I be able to make this upgrade if mariadb-upgrade does not work and/or will mythtv have to make adjustments for using the word "Offset" in their queries?

 
2 years, 1 month ago Rob Rutledge

Let's try this again:

Here is the output after upgrade:

  1. mysql --version mysql Ver 15.1 Distrib 10.6.7-MariaDB, for Linux (x86_64) using readline 5.1
  2. mariadb-upgrade -p Enter password: Major version upgrade detected from 10.5.13-MariaDB to 10.6.7-MariaDB. Check required! Error: Server version (10.5.13-MariaDB) does not match with the version of the server (10.6.7-MariaDB) with which this program was built/distributed. You can use --skip-version-check to skip this check. FATAL ERROR: Upgrade failed
  3. mysql_upgrade -p Enter password: Major version upgrade detected from 10.5.13-MariaDB to 10.6.7-MariaDB. Check required! Error: Server version (10.5.13-MariaDB) does not match with the version of the server (10.6.7-MariaDB) with which this program was built/distributed. You can use --skip-version-check to skip this check. FATAL ERROR: Upgrade failed

My main concern is that I would not be able to run mythtv if the mariadb upgrade was not successful. Mythtv does start now and I can play recorded shows, but I cannot set up new recordings -- I get a message that "could not start recording". The last time I tried to make this upgrade from 10.5.x to 10.6.x it became apparent that "Offset" is a reserved word now for MariaDB 10.6.x and I believe this word is used to set up the duration of the recordings. Will I be able to make this upgrade if mariadb-upgrade does not work and/or will mythtv have to make adjustments for using the word "Offset" in their queries?

 
2 years, 1 month ago Rob Rutledge

I forgot to include the version of mariadb-upgrade previously. It is:

mariadb-upgrade Ver 2.0 Distrib 10.6.7-MariaDB, for Linux (x86_64)

I have another image for slackware that I have not upgraded to ver 10.6.7. It shows these versions:

mariadb-upgrade Ver 1.4 Distrib 10.5.13-MariaDB, for Linux (x86_64)

Now the strange thing is that I just rebooted the system with ver 10.6.7, ran mariadb-upgrade, and it completed successfully. In addition I was able to start the mythbackend for mythtv and it appears to be working fine with the mariadb ver 10.6.7. Was there a workaround for the fact that "Offset" is or was a reserved word in version 10.6.x? Thanks again.

 
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.