Have it installed, but keep getting this message error.
Any help most appreciated.
Joel
2025-03-13T16:07:35.085993Z 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.
2025-03-13T16:07:35.098432Z 0 [Warning] [MY-010075] [Server] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: 46da4064-0025-11f0-916b-9c305b356e9b.
2025-03-13T16:07:35.110768Z 1 [ERROR] [MY-011011] [Server] Failed to find valid data directory.
2025-03-13T16:07:35.110899Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2025-03-13T16:07:35.110911Z 0 [ERROR] [MY-010119] [Server] Aborting
2025-03-13T16:07:35.111245Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.41-0ubuntu0.24.04.1) (Ubuntu).
2025-03-13T16:08:30.336866Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.41-0ubuntu0.24.04.1) starting as process 23896
2025-03-13T16:08:30.337703Z 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.
2025-03-13T16:08:30.337712Z 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.
2025-03-13T16:08:30.345445Z 1 [ERROR] [MY-011011] [Server] Failed to find valid data directory.
2025-03-13T16:08:30.345593Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2025-03-13T16:08:30.345606Z 0 [ERROR] [MY-010119] [Server] Aborting
2025-03-13T16:08:30.345926Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.41-0ubuntu0.24.04.1) (Ubuntu).
2025-04-17T15:05:26.190747Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.41-0ubuntu0.24.04.1) starting as process 47952
2025-04-17T15:05:26.191516Z 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.
2025-04-17T15:05:26.191525Z 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.
2025-04-17T15:05:26.232255Z 1 [ERROR] [MY-011011] [Server] Failed to find valid data directory.
2025-04-17T15:05:26.232386Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2025-04-17T15:05:26.232401Z 0 [ERROR] [MY-010119] [Server] Aborting
2025-04-17T15:05:26.232786Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.41-0ubuntu0.24.04.1) (Ubuntu).
2025-04-17T15:10:04.021050Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.41-0ubuntu0.24.04.1) starting as process 48304
2025-04-17T15:10:04.021818Z 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.
2025-04-17T15:10:04.021826Z 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.
2025-04-17T15:10:04.029853Z 1 [ERROR] [MY-011011] [Server] Failed to find valid data directory.
2025-04-17T15:10:04.029952Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2025-04-17T15:10:04.029968Z 0 [ERROR] [MY-010119] [Server] Aborting
2025-04-17T15:10:04.030397Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.41-0ubuntu0.24.04.1) (Ubuntu).
2025-04-17T15:34:07.290044Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.41-0ubuntu0.24.04.1) starting as process 50648
2025-04-17T15:34:07.290840Z 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.
2025-04-17T15:34:07.290849Z 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.
2025-04-17T15:34:07.298695Z 1 [ERROR] [MY-011011] [Server] Failed to find valid data directory.
2025-04-17T15:34:07.298806Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2025-04-17T15:34:07.298820Z 0 [ERROR] [MY-010119] [Server] Aborting
2025-04-17T15:34:07.299157Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.41-0ubuntu0.24.04.1) (Ubuntu).
Hi Joel!
You have to replace Mysql (mysqld 8.0.41-0ubuntu0.24.04.1) With MariaDB
sudo apt-get install mariadb-client-10.3 mariadb-server-10.3 libmariadb3 libssl-dev
--
Saku
OH1KH
Thank you Saku. I did that and this was returned:
"Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package mariadb-client-10.3 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
mariadb-client
Package mariadb-server-10.3 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
mariadb-server-core mariadb-server mariadb-client
E: Package 'mariadb-client-10.3' has no installation candidate
E: Package 'mariadb-server-10.3' has no installation candidate"
Then I did the following per the suggested action:
Sudo apt-get install mariadb-server-core mariadb-server mariadb-client
Ran CQRLog and now get this error message box:
"Error during connection to database: TMySQL57Connection : Server connect failed."
Joel
KC2GRN
HI Joel!
Maybe those refer to old packets as message was very old where I copied that. I am a Fedora user and do not know what are package names currently with Ubuntu.
I try to dig out.....
sudo apt install mariadb-client mariadb-server mariadb-common
Those should do it with Ubuntu 2204.
They are copied from script I have in my GitHub
https://github.com/OH1KH/CqrlogAlpha/tree/main/compiled
where I have full Cqrlog install script for Ubuntu 2204.
https://github.com/OH1KH/CqrlogAlpha/blob/main/compiled/install_Ubuntu22...
Perhaps those could help you forward.
--
Saku
OH1KH
Saku,
Thank you for the information. I'll give it a try and see what happens!
73, Joel
I, too get the "TMySQL56Connection : Server connect failed." error.
I am running cqrlog v. 2.3.0 and mariadb 10.3.
For reasons I will not go into here, I had to reinstall Linux a few days ago, so the versions of cqrlog and mariadb may have changed. Everything in my ~ tree was unchanged, since I did not reformat the /home partition during the reinstall. I am currently running Debian Linux 10.10, "Buster."
I store my logs locally. If I move the contents out of the ~/.config/cqrlog/database folder, cqrlog loads normally, but there doesn't seem to be any way to load my backup file. (The "Utils" button in the "Database connection" window does not offer the usual file backup or restore options.)
Here's what I get when I attempt to start cqrlog with my existing database folder contents:
mike@N2EM:~/radio/logging$ cqrlog -debug=1
(cqrlog:2267): Gtk-WARNING **: 09:20:51.805: Unable to locate theme engine in module_path: "adwaita",
Cqrlog Ver:2.3.0 (001) Date:2018-06-17
**** DEBUG LEVEL 1 ****
SSL libraries:
/usr/lib/x86_64-linux-gnu/libssl.so.1.1
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1
Loading libmysqlclient: /usr/lib/x86_64-linux-gnu/libmariadbclient.so
**************************
MySQL version: 10.
**************************
**********************************
MySQL version assigned: 5.6
**********************************
Loaded 216935 LoTW users
Loaded 191546 eQSL users
Loaded 5742 SCP calls
*
User home directory: /home/mike/
Program home directory: /home/mike/.config/cqrlog/
Data directory: /home/mike/.config/cqrlog/database/
Members directory: /home/mike/.config/cqrlog/members/
ZIP code directory: /usr/share/cqrlog/zipcodes/
Binary dir: /usr/bin/
Share dir: /usr/share/cqrlog/ TConnection to MySQL: 5.6
*
56 us states loaded
/usr/sbin/mysqld --defaults-file=/home/mike/.config/cqrlog/database/mysql.cnf --datadir=/home/mike/.config/cqrlog/database/ --socket=/home/mike/.config/cqrlog/database/sock --port=64000
Trying to connect to database
TMySQL56Connection : Server connect failed.
Trying:1 (First of many "Trying:n".)
Any help will be appreciated.
73,
Mike, N2EM
Mike, N2EM
Hi Mike!
2.3.0 is really old version. It is even older than latest available from cqrlog.com/downloads (2.5.2) that is also old.
Could it be that you had higher version than 2.3.0 in use before you reinstalled your Linux?
That would explain the missing Utils selections.
As it seems you have backup from your ~/.config/cqrlog folder you can do some tests. If they fail you just restore the folder and try something else.
In worst case delete whole folder, start from zero and import your qsos from aldf.
What I would try is to decide to use latest official Cqrlog 2.5.2 or jump directly to CqrlogAlpha(136).
Cqrlog 2.5.2)
==========
You can override your 2.3.0 with 2.5.2 downloading the tar.gz file from cqrlog.com/downloads
cd /tmp
wget https://github.com/ok2cqr/cqrlog/releases/download/v2.5.2/cqrlog_2.5.2_a...
cd /
sudo tar -vxf /tmp/cqrlog_2.5.2_amd64.tar.gz --strip-components=1
Then try to start cqrlog and see what happens.
CqrlogAlpha(136)
==============
Download and run newupdate.sh to upgrade your existing version:
cd /tmp
wget https://github.com/oh1kh/CqrlogAlpha/raw/refs/heads/main/compiled/newupd...
unzip /tmp/newupdate.zip
/tmp/newupdate.sh
When script starts it will show what to do next.
--
Saku
OH1KH
To help your decide you can scroll down this view and see what has happened after 2.3.0 :
https://html-preview.github.io/?url=https://github.com/OH1KH/CqrlogAlpha...
--
Saku
OH1KH