MySQL error after upgrade to Mint 20

13 posts / 0 new
Last post
NZ0T
MySQL error after upgrade to Mint 20

I get error

"Error during connection to database:
TMySQL57 connection: Server connect failed"

Last lines of MySQL error:

2020-07-10T00:01:27.684583Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.20-0ubuntu0.20.04.1) starting as process 1804
2020-07-10T00:01:27.688382Z 0 [Warning] [MY-013242] [Server] --character-set-server: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.
2020-07-10T00:01:27.688401Z 0 [Warning] [MY-013244] [Server] --collation-server: 'utf8_general_ci' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.
2020-07-10T00:01:27.859967Z 1 [ERROR] [MY-011011] [Server] Failed to find valid data directory.
2020-07-10T00:01:27.860302Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2020-07-10T00:01:27.860459Z 0 [ERROR] [MY-010119] [Server] Aborting
2020-07-10T00:01:27.861354Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.20-0ubuntu0.20.04.1) (Ubuntu).
2020-07-10T00:37:27.515297Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.20-0ubuntu0.20.04.1) starting as process 3678
2020-07-10T00:37:27.519633Z 0 [Warning] [MY-013242] [Server] --character-set-server: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.
2020-07-10T00:37:27.519656Z 0 [Warning] [MY-013244] [Server] --collation-server: 'utf8_general_ci' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.
2020-07-10T00:37:27.711669Z 1 [ERROR] [MY-011011] [Server] Failed to find valid data directory.
2020-07-10T00:37:27.712216Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2020-07-10T00:37:27.712503Z 0 [ERROR] [MY-010119] [Server] Aborting
2020-07-10T00:37:27.714035Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.20-0ubuntu0.20.04.1) (Ubuntu).
2020-07-10T12:39:30.901545Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.20-0ubuntu0.20.04.1) starting as process 1944
2020-07-10T12:39:30.905297Z 0 [Warning] [MY-013242] [Server] --character-set-server: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.
2020-07-10T12:39:30.905316Z 0 [Warning] [MY-013244] [Server] --collation-server: 'utf8_general_ci' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.
2020-07-10T12:39:31.063321Z 1 [ERROR] [MY-011011] [Server] Failed to find valid data directory.
2020-07-10T12:39:31.063921Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2020-07-10T12:39:31.064212Z 0 [ERROR] [MY-010119] [Server] Aborting
2020-07-10T12:39:31.065748Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.20-0ubuntu0.20.04.1) (Ubuntu).

K9ACM
I also am getting a database

I also am getting a database error after upgrade to Mint 20.

My SQL error:

2020-07-10T20:05:40.150048Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.20-0ubuntu0.20.04.1) starting as process 74520
2020-07-10T20:05:40.150888Z 0 [Warning] [MY-013242] [Server] --character-set-server: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.
2020-07-10T20:05:40.150896Z 0 [Warning] [MY-013244] [Server] --collation-server: 'utf8_bin' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.
2020-07-10T20:05:40.177724Z 1 [ERROR] [MY-011011] [Server] Failed to find valid data directory.
2020-07-10T20:05:40.177878Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2020-07-10T20:05:40.177932Z 0 [ERROR] [MY-010119] [Server] Aborting
2020-07-10T20:05:40.178225Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.20-0ubuntu0.20.04.1) (Ubuntu).

NZ0T
Looks like the same error. I

Looks like the same error. I also found that the CQRLOG PPA does not work with Mint 20. I'll stick with Mint 19.3 on my shack computer until fixes occur.

K9ACM
Yes, same here with the PPA

Yes, same here with the PPA error. I hope a fix comes quickly.

PA1SBM
PA1SBM's picture
MySQL error after upgrade to Mint 20

I had the same error......

As i am fixing my automated installer script i ran into this as well.....
I had to fix a lot, so i am not 100% sure if this was the fix....
I think i renamed the cqrlog folder in /home/username/.config to cqrlog.old and started CQRlog again
Then it worked again... but you need to do all settings again

The main problem with the PPA is that it still installs mysql....
I am fixing my installer script now to first install mariadb which is suggested a lot on the interwebs.... :)
Let me know if this worked for you too.

greets,

Alex
PA1SBM

PA1SBM
PA1SBM's picture
MySQL error after upgrade to Mint 20

Other thing is that on my normal workstation i upgraded from 19.3 to 20 as well.... but i see several buggs... a bit too many....
If you need a stable system i suggest to stick with 19.3.... and wait till 20.1 or close to 20.1

On the other hand there are a few major improvements like the "explorer" is way faster. Including browsing the network.

G0OER
I've had the same problem

I've had the same problem here after a fresh install of Mint 20. I will either wait until 20.1 or try to fix later. Will keep the forum posted if I get a fix and can isolate how I did it.

NZ0T
Same here, I'm going to stay

Same here, I'm going to stay with 19.3 on my shack computer until 20 is working properly.

NZ0T
Same here, I'm going to stay

Same here, I'm going to stay with 19.3 on my shack computer until 20 is working properly.

ik5pws
Hi William,

Hi William,
has Alex wrote, I installed maria-db before cqrlog and it's seems to work,
at least I can reopen my logs.

I am continuing to work with dialup and TQSL, I'll let you know my global result

73 de Stefano

File: 

NZ0T
Hi Strfano,

Hi Strfano,

Was this a fresh install of cqrlog? I already had cqrlog installed before my upgrade from 19.3 to 20. maybe if I uninstalled maria-db and then reinstalled it? I'll try that.

73, Bill NZ0T

NZ0T
I installed mariadb server-10

I installed mariadb server-10.3 and that solved the problem. It deleted mysql during the install. I did have an issue with the install taking a long time but once done cqrlog is now working on my Mint 20 test computer. If I get brave I'll try the same fix on my shack computer.

73, Bill NZ0T

ik5pws
Hi Bill,

Hi Bill,
I tried to update from 19.3 to 20 but something went wrong an i got a system that seems not properly work.

So, due i used a SSD for root (/) and two HD in raid for /home, I decided to reinstall my os (formatting /).
After that, i reinstalled CQRLOG and i went stuck with that issue.

After solved db problem i got CQRLOG working again and I could again to work with my logs,
I also had imported my ARRL HF contest log of last week end and everything at this moment work well,
included export to LOTW (after I installed TQSL from binaries obvously).
73 de Stefano