nstalling mariadb
I am running a new install of Ubuntu 22.04. Previously I had CQRlog running with mysql on Ubuntu 20.4. The new install has made all previous Ubuntu directories invisible or erased.
In any case, CQRlog itself has installed but cannot run because there is no SQL database to connect to. Your FAQ suggests using MariaDB. I have downloaded it, and began an install. The lines below show a failure due to trusted package singing keys not being released on ok2cqr directory in repository. The "curl" command is a copy-pasted command from the
mariadb.com/kb/en/installing-mariadb-deb-files/ webpage.
root@joe-Studio-XPS-7100:/opt# curl -sS https://downloads.mariadb.com/MariaDB/mariadb_repo_setup | sudo bash
# [info] Checking for script prerequisites.
# [info] MariaDB Server version 10.11 is valid
# [info] Repository file successfully written to /etc/apt/sources.list.d/mariadb.list
# [info] Adding trusted package signing keys...
# [info] Running apt-get update...
E: The repository 'https://ppa.launchpadcontent.net/ok2cqr/ppa/ubuntu jammy Release' does not have a Release file.
# [error] Failed to add trusted package signing keys
What do you suggest?
Thanks and 73's,
Joe N0NOW
Here are the last 20 lines of the mariadb error file listing from ~/.config/cqrlog/database/mysql.err.
2023-06-08T00:22:22.763272Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.33-0ubuntu0.22.04.2) starting as process 3126
2023-06-08T00:22:22.765254Z 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.
2023-06-08T00:22:22.765266Z 0 [Warning] [MY-013244] [Server] --collation-server: 'utf8mb3_bin' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.
2023-06-08T00:22:22.773559Z 1 [ERROR] [MY-011011] [Server] Failed to find valid data directory.
2023-06-08T00:22:22.773917Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2023-06-08T00:22:22.773966Z 0 [ERROR] [MY-010119] [Server] Aborting
2023-06-08T00:22:22.774528Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.33-0ubuntu0.22.04.2) (Ubuntu).
2023-06-08T00:22:25.683086Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.33-0ubuntu0.22.04.2) starting as process 3194
2023-06-08T00:22:25.685097Z 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.
2023-06-08T00:22:25.685108Z 0 [Warning] [MY-013244] [Server] --collation-server: 'utf8mb3_bin' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.
2023-06-08T00:22:25.691719Z 1 [ERROR] [MY-011011] [Server] Failed to find valid data directory.
2023-06-08T00:22:25.692092Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2023-06-08T00:22:25.692145Z 0 [ERROR] [MY-010119] [Server] Aborting
2023-06-08T00:22:25.692704Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.33-0ubuntu0.22.04.2) (Ubuntu).
2023-06-09T20:57:46.879670Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.33-0ubuntu0.22.04.2) starting as process 22886
2023-06-09T20:57:46.888883Z 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.
2023-06-09T20:57:46.888906Z 0 [Warning] [MY-013244] [Server] --collation-server: 'utf8mb3_bin' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.
2023-06-09T20:57:46.970635Z 1 [ERROR] [MY-011011] [Server] Failed to find valid data directory.
2023-06-09T20:57:46.971124Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2023-06-09T20:57:46.971376Z 0 [ERROR] [MY-010119] [Server] Aborting
2023-06-09T20:57:46.976289Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.33-0ubuntu0.22.04.2) (Ubuntu).
Hope it helps.
Joe
Hi Joe!
From you listing "(mysqld 8.0.33-0ubuntu0.22.04.2)" can be seen that you still run Mysql, not MariaDB.
https://www.cqrlog.com/comment/10993#comment-10993
--
Saku
OH1KH
Thanks, Saku, but I am still confused.
1. I try to install MariaDB (the package is downloaded) and it gives me this error every time:
The repository 'https://ppa.launchpadcontent.net/ok2cqr/ppa/ubuntu jammy Release' does not have a Release file.
2. As to your comment that "you still run Mysql, not MariaDB," I do not know how to change that. CQRLOG is installed, and I just click to open it. Immediately it gives me this error:
Database Problem
MySQL could not be started, please check if the MySQL server is installed properly.
That is, CQRlog is looking for MySQL, not MariaDB, and I can't change that.
My very limited knowledge of Ubuntu and Linux in general has me hung up.
Thanks,
Joe N0NOW
Hi Joe!
I do not know the secrets of Ubuntu as I use Fedora Linux that has different package manager system.
I think that if you have Cqrlog installed but wrong database engine running you should be able to change that with "apt get install" or "apt install" command.
That should remove Mysql and install MariaDB. That is what has helped so many users with similar problem.
Maybe some other Ubuntu user can help you and show how to do this.
I could, perhaps, make it run using various tricks. But it is too complicated to explain via forum messages because I am not certain what to do. Usually trying enough testting results success, hi. I have done some support via AnyDesk remote in cases there is only Ham radio in Linux (so that I can not mess up anything valuable)
--
Saku
OH1KH
Thanks, Saku. I DID get MariaDB installed! CQRlog opened then with no difficulty, and I was able to import the .adi file with all previous QSOs intact. Your comment set the right path.
73's,
Joe
N0NOW