MythTV Upgrade from v29 to v31 - MySQL FROZEN

[notidefix]

Recently upgraded Ubuntu from 18.04 to 20.04 and MythTV was upgraded in the process

First I noticed that MySQL was not installed at all, so I tried to install MySQL 8

During installation, MySQL indicated it was FROZEN, indicating that the existing MySQL MythTV database (MySQL 5.7) was not compatible with MySQL 8

why would MySQL 8 not be able to read the old MySQL database?

[bill6502]

MySQL v8 can read mythconverg.

Include the output of this please: dpkg -l mariadb-server mysql-server
and may as well see: systemctl status --full --no-pager mysql mysqld mariadb

Looking to see if MariaDB got installed.

FYI only, the 0.n prefix went away after 0.28.

[notidefix]

dpkg -l mariadb-server mysql-server
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-=================================
un mariadb-server <none> <none> (no description available)
un mysql-server <none> <none> (no description available)


systemctl status --full --no-pager mysql mysqld mariadb
● mysql.service - MySQL Community Server
Loaded: loaded (/lib/systemd/system/mysql.service; disabled; vendor preset: enabled)
Active: inactive (dead)
Unit mysqld.service could not be found.
Unit mariadb.service could not be found.

[notidefix]

looks like mariadb was installed....during the upgrade, I can only assume

uninstalled mysql 8
installed mariadb

could read mythconverg, but mythtv could not connect to database......mariadb also crashed after running for 10 minutes......so back to mysql 8

sqldump to backup mythconverg
deleted mythconverg
reinstalled mysql 8
recreated mythconverg from sql dump

at this point mythbackend would not start.....error log indicated database issues

so reinstalled mythtv, front and back......and I have my old recordings back

but now I cannot get a channel lock......I can scan channels.......but doesn't lock

[paulh]

When you say you 'upgraded Ubuntu from 18.04 to 20.04' you are talking about an in place upgrade not a fresh install is that correct?

I'd be surprised if Ubuntu just unilaterally decided to remove MySQL and replace it with MariaDB without any warnings?

[notidefix]

yes....an upgrade from an already installed 18.04

the reply to my 1st post had me looking for mariadb and I did notice that mariadb common was installed (even though I reinstalled mysql 8)

could an 18.04 update in the last few years changed to mariadb.....?

in any case, the problems I saw with my installation of mariadb were well documented by others, so I had no interest in using mariadb

[paulh]

I skimmed though the 20.04 release notes but didn't see anything about swapping MySQL for MariaDB. I know new installs prefer MariaDB over MySQL which is why I asked.

There is nothing wrong with current MariaDB, I use it myself, if you set it up correctly. After Oracle took over MySQL, and the uncertainty of the future of MySQL, most distros seem to be switching to MariaDB so long term that seems to be the way to go. Just saying

[notidefix]

which version of mariadb are you using?

[paulh]

I have one MariaDB server that hosts all my databases and appear to be 10.3.25 running on Ubuntu Server 20.04.1 LTS.

The clients mostly run on the latest Kubuntu or Xubuntu so are probably using slightly newer versions of the client. No where near on to check at the moment.