All,
Good evening. I just installed CQRLog and MySQL, on a freshly installed Ubuntu Mate 20.04.1 installation, from the repo. When I launch CQRLog, I get the following MySQL error:
"Error during connection to database: TMYSQL57Connection: Server connect failed."
Here is the relevant output from my error log:
2020-12-12T22:27:10.550914Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.22-0ubuntu0.20.04.3) starting as process 7719
2020-12-12T22:27:10.552120Z 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-12-12T22:27:10.552130Z 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-12-12T22:27:10.626390Z 1 [ERROR] [MY-011011] [Server] Failed to find valid data directory.
2020-12-12T22:27:10.626760Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2020-12-12T22:27:10.626862Z 0 [ERROR] [MY-010119] [Server] Aborting
2020-12-12T22:27:10.627308Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.22-0ubuntu0.20.04.3) (Ubuntu).
2020-12-12T22:35:59.058286Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.22-0ubuntu0.20.04.3) starting as process 2258
2020-12-12T22:35:59.060769Z 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-12-12T22:35:59.060786Z 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-12-12T22:35:59.114379Z 1 [ERROR] [MY-011011] [Server] Failed to find valid data directory.
2020-12-12T22:35:59.114856Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2020-12-12T22:35:59.115046Z 0 [ERROR] [MY-010119] [Server] Aborting
2020-12-12T22:35:59.115828Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.22-0ubuntu0.20.04.3) (Ubuntu).
I'm still new to Linux and learning my way through this. Any assistance would be much appreciated.
Thanks and 73,
Ian, NV4C
Hi Ian,
there is a problem with MySQL 8.0. Remove it and install MariaDB, instead. I'm going to release a new version of CQRLOG soon with fixed package dependencies.
73 Petr, OK2CQR
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com
Thanks, Petr. Is there proper documentation for connecting CQRLog to MariaDB, on the web site? Or will the logger connect automatically? I'm not a database person, so good documentation will be most helpful.
73 de,
Ian, NV4C
HI Ian!
You should get MariaDB installed with console command
sudo apt-get install mariadb-client-10.3 mariadb-server-10.3 libmariadb3 libssl-dev libmariadb-dev-compat
It should remove MySQL. I do not know if it asks permission to do that first. I that case say yes.
See this message thread:
https://cqrlog.com/node/2984
--
Saku
OH1KH
Thanks, Saku! That worked perfectly. Everything is up and running.
73 de,
Ian, NV4C
Awesome....the console command you shared worked ! I am also back up and running. Thank you Saku !
73
Stephanie WX3K
Hello.
I ran into this same problem, or a similar one, I think.
Repartitioned and formatted disk, fresh install of latest Linux Mint MATE (20), all app installations are fine. Launched CQR and after asking if I wanted to save data locally (yes) it failed with the error message I'm so familiar with these days. Hah. Can't connect to MySQL.
I remembered this thread and did the install of maria suggested above, which went smoothly. I then rebooted. CQR then launched normally, showing the default Log 001. It asked me about downloading QSL managers and all that, which I did. I checked the QSO list window and others and all looked normal.
Then I shut CQR down and located the usual stuff in .config/cqrlog. I replaced the databases folder with the one I had saved from before and launched CQR again. It failed with another database error and generated a 2.6 megabyte error log, which I saved, and then came here to report my results. o.O
What did I do wrong? I would have included the final 20 lines of the error log but I saw nothing useful there.
/phil
Hello Phil!
Could it be so that the saved .config/cqrlog was created with different database engine, I.E. MySql.
If it is dropped to MariaDB based system it usually does not work.
Form MariaDB -> MariaDB it may work if versions are not very different and no big changes have not made in MariaDB newer version.
Form MariaDB -> MariaDB, when database engine version is same, this should work "out of the box" if there is no other (security) system that prevents it.
With MySql -> MariaDB this have to be done via mysqldump using the .config/cqrlog/database/sock socket link connection (sock is there while cqrlog is running). You will find threads about it from here using keyword "mysqldump".
Easiest way is full ADIF export transfer, but that does transfer additional data like settings and notes to callsigns etc. Just the basic qso data.
--
Saku
OH1KH
Thanks for replying, Saku. Hmm. I assumed that MariaDB is a drop-in replacement for MySQL. It claims to be but apparently isn't.
I have copies of the old databases but the platform they lived on is completely gone. Fortunately, I have ADIF backups as well, so I can use those and will have to manually restore the missing data.
Given all these problems, I have a modest proposal that I'll post on a new thread shortly.
/phil
Hello, OM's
my Problem is to connection an external MySQL Database by my Homepage Provider
The Server-Version: 5.7.22
what must i do for an easy first connect, and create the tables...
Gerhard
DG1BOR
73 de
dg1bor
Hi Gerhard!
Look this message https://cqrlog.com/comment/9015#comment-9015
--
Saku
OH1KH