Local MySQL Database Issue

27 posts / 0 new
Last post
G8FXM
G8FXM's picture
Local MySQL Database Issue

I have successfully changed to using an external MySQL database rather than the db that comes with CQRLOG. This is working fine, however when I first set it up I connected to the database using the root user. I now wna tot change to a new user I have created called cqrlog. When I fire up CQRLog it asks for the db username and password, to now saves the cqrlog user I have created but the password seems to be stuck with the origional root password, so each time I start up CQRLog I have to retype the password. Is this the way it's supposed to work or can I get it to automatically connect to the MySQL database using the cqrlog username and password.

ok2cqr
ok2cqr's picture
Re: Local MySQL Database Issue

Hi Dave,

I just looked to the source code and username & password are saved always when the Connect button is clicked.

Please click to Disconnect before you change the username & password and click to connect again when password is changed.

73 Petr, OK2CQR

G8FXM
G8FXM's picture
Hi Petr, I tried that but I

Hi Petr, I tried that but I cant seem to get CQRLog to forget the previous 'root' password, I have to re-enter it every time. Is there a way I can delete in in a config file somewhere?

73'd De Dave, G8FXM O/S Linux Mint 18.1 KDE Plasma 64 bit  g8fxm@uksmg.org

ok2cqr
ok2cqr's picture
Hi Dave,

Hi Dave,

It's stored in ~/.config/cqrlog/cqrlog_login.cfg. I'll create special database on my computer and try to reproduce the problem.

73 Petr

G8FXM
G8FXM's picture
Hi Petr, I've tried editing

Hi Petr, I've tried editing the ~/.config/cqrlog/cqrlog_login.cfg directly. Even with the correct password manually entered into this file, CQRLOG still wont autoconnect, but if I type the password in manually on the connect UI, it works. It seems like CQRLOG isn’t reading the password from cqrlog_login.cfg, but somewhere else?

73'd De Dave, G8FXM O/S Linux Mint 18.1 KDE Plasma 64 bit  g8fxm@uksmg.org

ok2cqr
ok2cqr's picture
Re: Hi Petr, I've tried editing

Dave,

do you have "Store data to local machine" checked? It has to be unchecked even if you are using dedicated mysql server running on your machine. Maybe that will be the problem.

73 Petr

G8FXM
G8FXM's picture
Hi Petr, no, that is

Hi Petr, no, that is unchecked I have attached a screenshot to this reply for reference.

File: 

73'd De Dave, G8FXM O/S Linux Mint 18.1 KDE Plasma 64 bit  g8fxm@uksmg.org

G8FXM
G8FXM's picture
I have had permissions issues

I have had permissions issues previously, so thinking this may be the reason why CQRLOG cant read the cqrlog_login.cfg file for the password I ran a check on the file and got this result:

$ ls -l cqrlog_login.cfg
-rw-r--r-- 1 dave dave 242 Mar 21 21:37 cqrlog_login.cfg

Let me know if that’s not ok?

73'd De Dave, G8FXM O/S Linux Mint 18.1 KDE Plasma 64 bit  g8fxm@uksmg.org

VE4PER
VE4PER's picture
Unable to connect to MySQL vers 8.0 database

Hello Petr,
I had mysql up and running properly with MariadB added into the mix. When I attempted to connect to the dB with CQRlog something occurred that locked up everything and all databases were corrupted and I lost 3 yrs of archived weather data from my station weather station. When it corrupted, I was unable to uninstall or reinstall the databases properly and running the synaptic package manager to attempt to uninstall and start over from scratch would not work either because the corrupted state made synaptic think service was running when not, and would not clear it in attempts to stop it. I had to manually go through and delete /var/log/mysql logs, remove all references to mysql from the rc0 - rc6 startup lists as well as all refs to mysql in /etc , /etc/default folders as well then delete all mysql components one at a time using synaptic was finally successful getting mysql and mariadB out, and allowed a clean re-install.

I also had to re-install phpmyadmin. and using a combination of it and mysql command line I was able to set password for root user in mysql 8.0 as well as create three more users. One admin user, a normal weather station database user and a cqrlog UID and cqrlog as it's password. cqrlog user has all privileges and DROP so that it can create and populate/update the database. The CQRLog program login cqrlog and assoc PW works to login as an auth'd user using phpmy admin so I know the uerid and PW are OK. But when I remove the checkmark from save to local data space, and for it to use mySQL database on the sql server on the same machine using localhost:3306 or 127.0.0.1:3306 It does not connect. I am using the same UID and PW cqrlog to login as I did using the phpmyadmin.

File: 

Cheers, 73 & Good DX

oh1kh
Unable to connect to MySQL vers 8.0 database

Hi !
Did you check this?
https://cqrlog.com/comment/8751

--
Saku
OH1KH

VE4PER
VE4PER's picture
Unable to connect to MySQL vers 8.0 database

Yes I have it set to 0.0.0.0

Cheers, 73 & Good DX

VE4PER
VE4PER's picture
Unable to connect to MySQL vers 8.0 database

The database server came up and running as a service as expected and the weather station software immediately accessed the server correctly and created the archive database properly and has been updating it ever since. So there isn't anything wrong with the server operation it would appear.
I created the cqrlog user and password as specified with the appropriate specified privileges to be able to do the same database and table creation but it does not connect at all to allow it to run and set it up properly. I read in another post here that it creates a database named cqrlog, with two tables one with a name that ends in 001 and I believe the second ends in 'common' if I am not mistaken. I tried to find the post to get the correct names but couldn't find the post again.

Cheers, 73 & Good DX

oh1kh
Unable to connect to MySQL vers 8.0 database

Hi !
OK abt the listen IP address.

Cqrlog creates own database for every log starting from 001. Each database has several tables. Then there is one common database for all logs.

Have you tried to connect from command console specifying host and port? (I.E. not using mysqladmin)

Here are databases from my laptop. Ignore ais, information_schema, mysql, performance_schema and test they are not related to cqrlog.

[saku@hamtpad ~]$ mysql --host=127.0.0.1 --port=3306 -ucqrlog -p
Enter password:
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 17
Server version: 10.4.14-MariaDB-log MariaDB Server

Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MariaDB [(none)]> show databases;
+--------------------+
| Database |
+--------------------+
| ais |
| cqrlog001 |
| cqrlog002 |
| cqrlog003 |
| cqrlog004 |
| cqrlog005 |
| cqrlog006 |
| cqrlog007 |
| cqrlog008 |
| cqrlog009 |
| cqrlog_common |
| information_schema |
| mysql |
| performance_schema |
| test |
+--------------------+
15 rows in set (0.001 sec)

MariaDB [(none)]> show tables from cqrlog_common;
+-------------------------+
| Tables_in_cqrlog_common |
+-------------------------+
| bands |
| db_version |
| dxcc_ref |
| dxclusters |
| iota_list |
| log_list |
| qslmgr |
+-------------------------+
7 rows in set (0.001 sec)

MariaDB [(none)]> show tables from cqrlog001;
+---------------------------------+
| Tables_in_cqrlog001 |
+---------------------------------+
| call_alert |
| club1 |
| club2 |
| club3 |
| club4 |
| club5 |
| cqrlog_config |
| cqrlog_main |
| db_version |
| dxcc_id |
| freqmem |
| log_changes |
| long_note |
| notes |
| profiles |
| upload_status |
| version |
| view_cqrlog_main_by_callsign |
| view_cqrlog_main_by_qsodate |
| view_cqrlog_main_by_qsodate_asc |
| zipcode1 |
| zipcode2 |
| zipcode3 |
+---------------------------------+
23 rows in set (0.001 sec)

MariaDB [(none)]> quit
Bye
[saku@hamtpad ~]$

--
Saku
OH1KH

oh1kh
Unable to connect to MySQL vers 8.0 database

Hi !
Another question:

Have you watched what happens in interface lo using tcpdump when you try to connect?
I get similar error message as you if I put wrong password. It does not say wrong password, it says server connect failed that may lead to wrong track.

Try this in command console while pressing connect button at cqrlog / open database

sudo tcpdump -X -i lo port 3306

Then try to dig from the right side text what really happened.

--
Saku
OH1KH

VE4PER
VE4PER's picture
Unable to connect to MySQL vers 8.0 database

I followed up on your suggestions and have further symptoms & err log report .
Text below error log illustrates commands used logging into mysql with cqrlog userID.

root@[HOSTNAME]:/var/log/mysql# cat error.log
2020-11-11T06:44:47.757283Z 0 [System] [MY-013172] [Server] Received SHUTDOWN from user . Shutting down mysqld (Version: 8.0.22-0ubuntu0.20.04.2)
.
2020-11-11T06:44:53.556935Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.22-0ubuntu0.20.04.2)  (Ubuntu).
2020-11-11T06:46:32.699222Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.22-0ubuntu0.20.04.2) starting as process 1767
2020-11-11T06:46:33.456157Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2020-11-11T06:46:39.883963Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2020-11-11T06:46:43.425115Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /var/run/mysqld/mysqlx.sock
2020-11-11T06:46:44.993859Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2020-11-11T06:46:44.994352Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel
.
2020-11-11T06:46:45.425335Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.22-0ubuntu0.20.04.2'  socket: '/var/run/mysqld/
mysqld.sock'  port: 3306  (Ubuntu).
root@cedar:/var/log/mysql# cat error.log
2020-11-11T06:44:47.757283Z 0 [System] [MY-013172] [Server] Received SHUTDOWN from user . Shutting down mysqld (Version: 8.0.22-0ubuntu0.20.04.2)
.
2020-11-11T06:44:53.556935Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.22-0ubuntu0.20.04.2)  (Ubuntu).
2020-11-11T06:46:32.699222Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.22-0ubuntu0.20.04.2) starting as process 1767
2020-11-11T06:46:33.456157Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2020-11-11T06:46:39.883963Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2020-11-11T06:46:43.425115Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /var/run/mysqld/mysqlx.sock
2020-11-11T06:46:44.993859Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2020-11-11T06:46:44.994352Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel
.
2020-11-11T06:46:45.425335Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.22-0ubuntu0.20.04.2'  socket: '/var/run/mysqld/
mysqld.sock'  port: 3306  (Ubuntu).
root@cedar:/var/log/mysql# mysql --host=192.168.149.12 --port=3306 -ucqrlog -p          
Enter password:  
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 94
Server version: 8.0.22-0ubuntu0.20.04.2 (Ubuntu)

Copyright (c) 2000, 2020, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> show databases
   -> ;
+--------------------+
| Database           |
+--------------------+
| information_schema |
| mysql              |
| performance_schema |
| sys                |
| weewx              |
+--------------------+
5 rows in set (0.00 sec)

mysql> exit
Bye

File: 

Cheers, 73 & Good DX

oh1kh
Unable to connect to MySQL vers 8.0 database

Hi!
I returned to reading your fist message https://www.cqrlog.com/comment/8911#comment-8911.

Did I understand right that you have a mixture of MySql and MariaDB ?
And if so, why is that? Can't MariaDB alone work with all your needs?

You can find many messages here telling that installing MariaDB instead of MySQL solves all problems with cqrlog. This is one of them, more in earlier threads https://www.cqrlog.com/node/2994

According your picture "CQRLOG mysql connect local dB chkd.png" have you tried with "server name" as localhost or 127.0.0.1 ?
Did you check your connection attempt with tcpdump? Does cqrlog even try to open 3306 port connection?

--
Saku
OH1KH

VE4PER
VE4PER's picture
oh1kh Unable to connect to MySQL vers 8.0 database

Yes I have used, 127.0.0.1 , localhost, cedar (hostname from hosts file) and 192.168.149.12 all of these to attempt to login.

NONE works.

the link you refer to the Lazarus dll file refers to a fix for this on a windows machine as the installer is a zip file and the name itself includes dll.

The machine I am running this on is ubuntustudio 20.04LTS linux box.

As I understood the matter, I had run into some confusion with another program using mySQL 8.0 alone and had added the amended dB server package so that it was not just running the Oracle proprietary package MySQL but then included the open source compatible MariadB which also seemed to work seamlessly. This why both have indications.

The weewx weather station software package I use on the linux box had some difficulties and I had to remove both the previous version of MySQL and MariadB completely and install MySQL Vers 8.0 alone to recover the weather reporting system properly. It supplies, Weather Underground, AWEKAS, NOAA/CWOP systems with my data.

Log4OM is running on the windows 10 machine , no problem with mySQL v 8 and there is no CQRLOG for windows platforms hence the need to use both here.

I have tried to install the applicable vers 5.7 library file for the linux box from synaptic package manager but it does not appear to be available.

I apologize for this exchange winding up in a wrong thread but I thought when I clicked on the new button it was creating a new topic unrelated to the current one.

Cheers, 73 & Good DX

oh1kh
Unable to connect to MySQL vers 8.0 database

Yep!
It is dll, so its windoze file. Did not read carefully enough.

But it does not change the root reason. Lazaus sql connection uses 5.7 and there is no higher version to use. Cqrlog is made with Lazarus, without any external database tool libraries. So it wants 5.7 or below for connection. And that mysql 8 can not provide.

Solution is MariaDB, alone. It provides 5.7 level connection.

Let me know if you find something smart to get mysql 8 working.

--
Saku
OH1KH

oh1kh
Unable to connect to MySQL vers 8.0 database

Hi!

Googled a bit more as I was remembering that there has been discussions about mysql 8 before.

Here it is :
https://forum.lazarus.freepascal.org/index.php?topic=41855.0

As you see from error splash cqrlog uses MySQL57Connection and that does not work with Mysql 8 because cqrlog is made with Free Pascal/Lazarus.
You could try the solution said at link thread's last message if you need to keep Mysql 8 running. If you just can find library from old mysql installation.

Easier may be to give up Mysql 8 and install only MariaDB.

--
Saku
OH1KH

VE4PER
VE4PER's picture
Unable to connect to MySQL vers 8.0 database

re "give up on MySQL 8 and install Mariadb Only"
The installer just removes Maria and puts everything back to MySQL so this is a catch 22 it would seem. Please explain this to me? he said waiting patiently.

With all the remarks about many others solved it by taking out Mysql8 and just using mariadb ??? Don't know how they did that using commandline results in text error info above and so does using synaptic to install cqrlog !!!!

The following packages were automatically installed and are no longer required:
galera-3 libconfig-inifiles-perl libdbd-mysql-perl libdbi-perl libreadline5 libterm-readkey-perl socat
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
cqrlog-data default-mysql-server-core libmecab2 mysql-client-core-8.0 mysql-server-core-8.0
Recommended packages:
default-mysql-server
The following packages will be REMOVED:
mariadb-backup mariadb-client mariadb-client-10.3 mariadb-client-core-10.3 mariadb-server mariadb-server-10.3 mariadb-server-core-10.3
The following NEW packages will be installed:
cqrlog cqrlog-data default-mysql-server-core libmecab2 mysql-client-core-8.0 mysql-server-core-8.0
0 upgraded, 6 newly installed, 7 to remove and 1 not upgraded.
Need to get 22.0 MB/33.7 MB of archives.
After this operation, 43.8 MB of additional disk space will be used.
Do you want to continue? [Y/n] n

Cheers, 73 & Good DX

VE4PER
VE4PER's picture
Unable to connect to MySQL vers 8.0 database UPDATE

I was able to get the linux PC set with just selecting mariadB client, server and common software from the synaptic package manager in the ubuntustudio 20.04LTS OS. I just let it all install automatically and the installer included any common needed mysql apps or sub apps/libraries. I then used the terminal window (aka console) to access the mariadb equivalent commands to run mysqladmin to set the root user password. Then logging into mysql/mariadb at the command prompt I used standard mariadb syntax commands to create the cqrlog user with a password "cqrlog" . I granted ALL privileges NO GRANT to cqrlog user @ "%" and "localhost" on cqrlog_common.* and cqrlog001.* databases. (although neither db is existing at this point the user is set up and available when needed by installer to initialize the databases). Having installed apache2 (www server) , php latest current version, and phpmyadmin. (phpmyadmin works with mariadb normally as it does with mysql).
I then moved on to install cqrlog program itself; WARNING using synaptic package manager, or command line apt install methods dependent on ppa sources to install CQRLOG it did not work as the installer is designed to use the latest current version of mySQL (which is the problematic vers 8.0) server and client and it will remove/uninstall the mariadb already installed and configured and replace it with mysql 8.0.
Instead I chose to use the .deb installer file through the linux software installer ( not to be confused with the synaptic package manager). It did install CQRLOG program as well as used the cqrlog user in the mariadb database to create and initialize the cqrlog001 and cqrlog_common db's with included tables as specified in CQRLOG docs. To this point I have yet to get the program to run and connect satisfactorily to the backend database. This is progress from initial posts by me here in this forum. The installer has proven the program can connect and create/modify/initialize the database properly using Mariadb. Where the problem exists now is just getting the connection to work reliably everytime one wants to use the CQRLOG program. [attached is phpmyadmin graphic showing the db's and associated tables that were created. At least I am down to one problem to solve now. thanks for all he tips and assists here. I will update this with the solution if I find one. In the meantime I am still glad to see any further help or tips.
Thanks again 73 & Gud DX stay safe Andy de ve4per

File: 

Cheers, 73 & Good DX

VE4PER
VE4PER's picture
Unable to connect to MySQL vers 8.0 database UPDATE 2

Although the .deb installer created the initial cqrlog_common and cqrlog001 dB when I went to use the launcher to open the cqrlog app it was not anywhere and although locate cqrlog said it was installed, inspecting the various folders indicated files were not installed. I downloaded the generic linux OS tarball installer rather than the .deb installer, and it etxracted but did not install in the usually expected standard linux folders. it extracted in place and creating a shortcut to that application file seems to get it running, however trying to enter qso's, or show qso lists etc seems to generate errors that warn I am risking database corruption. I have att png file and include debug=1 text details. "New Log' resulted in creation of cqrlog002 in the mariadb database.

root@cedar:/home/USERid/installs/cqrlog/cqrlog-2.4.0/usr/bin# ls
cqrlog
root@cedar:/home/USERid/installs/cqrlog/cqrlog-2.4.0/usr/bin# su USERid
USERid@cedar:~/installs/cqrlog/cqrlog-2.4.0/usr/bin$ cqrlog

Command 'cqrlog' not found, but can be installed with:

sudo apt install cqrlog

USERid@cedar:~/installs/cqrlog/cqrlog-2.4.0/usr/bin$ ls
cqrlog
USERid@cedar:~/installs/cqrlog/cqrlog-2.4.0/usr/bin$ ~/installs/cqrlog/cqrlog-2.4.0/usr/bin/cqrlog

Cqrlog Ver:2.4.0 (001) Date:2019-10-27
**** DEBUG LEVEL 0 ****
**** CHANGE WITH --debug=1 PARAMETER ****

OS:
Linux version 5.4.0-53-lowlatency (buildd@lcy01-amd64-007) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #59-Ubuntu SMP PREEMPT Wed Oct 21 11:21:50 UTC 2020
TApplication.HandleException TMySQL57Connection : Error executing query: Unknown database 'cqrlog000'
Stack trace:
$00000000009355DF
$0000000000936CC8
$00000000006E4E0A
$00000000006E5653
$00000000006E4CF6
$00000000004311CF
$000000000067355D
$0000000000848302
$000000000085A361
Closing ini file ...
USERid@cedar:~/installs/cqrlog/cqrlog-2.4.0/usr/bin$ ~/installs/cqrlog/cqrlog-2.4.0/usr/bin/cqrlog --debug=1

Cqrlog Ver:2.4.0 (001) Date:2019-10-27
**** DEBUG LEVEL 1 ****

OS:
Linux version 5.4.0-53-lowlatency (buildd@lcy01-amd64-007) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #59-Ubuntu SMP PREEMPT Wed Oct 21 11:21:50 UTC 2020
SSL libraries:
libssl.so
libcrypto.so
Loaded 134350 LoTW users
Loaded 125829 eQSL users
Loaded 36919 SCP calls
*
User home directory: /home/USERid/
Program home directory: /home/USERid/.config/cqrlog/
Data directory: /home/USERid/.config/cqrlog/database/
Memebers directory: /home/USERid/.config/cqrlog/members/
ZIP code directory: /home/USERid/installs/cqrlog/cqrlog-2.4.0/usr/share/cqrlog/zipcodes/
Binary dir: /home/USERid/installs/cqrlog/cqrlog-2.4.0/usr/bin/
Share dir: /home/USERid/installs/cqrlog/cqrlog-2.4.0/usr/share/cqrlog/
*
56 us states loaded
Grid map created
select * from tables where table_schema = 'cqrlog_common'

SELECT log_nr,log_name FROM cqrlog_common.log_list order by log_nr

TApplication.HandleException "" is an invalid integer
Stack trace:
$000000000046F55C
$00000000005BCA22
$00000000006E4E0A
$00000000006E5653
$00000000006E4CF6
$00000000004311CF
$000000000067355D
$0000000000848302
$000000000085A361
use cqrlog000

TApplication.HandleException TMySQL57Connection : Error executing query: Unknown database 'cqrlog000'
Stack trace:
$00000000009355DF
$0000000000936CC8
$00000000006E4E0A
$00000000006E5653
$00000000006E4CF6
$00000000004311CF
$000000000067355D
$0000000000848302
$000000000085A361
TApplication.HandleException Access violation
Stack trace:
$000000000051C0C2
$00000000006E4E0A
$00000000006E5653
$00000000006E4CF6
$00000000004311CF
$000000000067355D
$0000000000848302
$000000000085A361
select log_nr from cqrlog_common.log_list order by log_nr

select log_nr from cqrlog_common.log_list where log_nr = 1

CREATE DATABASE IF NOT EXISTS cqrlog001 DEFAULT CHARACTER SET = utf8 DEFAULT COLLATE = utf8_bin;

use cqrlog001;

CREATE TABLE cqrlog_main (
id_cqrlog_main INT AUTO_INCREMENT PRIMARY KEY,
qsodate DATE NOT NULL,
time_on VARCHAR(5) NOT NULL,
time_off VARCHAR(5) DEFAULT '',
callsign VARCHAR(20) NOT NULL,
freq NUMERIC(10,4) NOT NULL,
mode VARCHAR(12) NOT NULL,
rst_s VARCHAR(20) DEFAULT '',
rst_r VARCHAR(20) DEFAULT '',
name VARCHAR(40) DEFAULT '',
qth VARCHAR(60) DEFAULT '',
qsl_s VARCHAR(4) DEFAULT '',
qsl_r VARCHAR(3) DEFAULT '',
qsl_via VARCHAR(30) DEFAULT '',
iota VARCHAR(6) DEFAULT '',
pwr VARCHAR(10) DEFAULT '',
itu INT DEFAULT 0,
waz INT DEFAULT 0,
loc VARCHAR(10) DEFAULT '',
my_loc VARCHAR(10) DEFAULT '',
county VARCHAR(30) DEFAULT '',
award VARCHAR(50) DEFAULT '',
remarks VARCHAR(200) DEFAULT '',
adif INTEGER DEFAULT 0,
/*dxcc_ref VARCHAR(20) DEFAULT '',*/
band VARCHAR(6) DEFAULT '',
qso_dxcc INT DEFAULT 0,
profile INT DEFAULT 0,
idcall VARCHAR(20) DEFAULT '',
state VARCHAR(4) DEFAULT '',
lotw_qslsdate DATE,
lotw_qslrdate DATE,
lotw_qsls VARCHAR(3) DEFAULT '' not null,
lotw_qslr VARCHAR(3) DEFAULT '' not null,
cont VARCHAR(3) DEFAULT '',
qsls_date VARCHAR(10),
qslr_date VARCHAR(10),
club_nr1 VARCHAR(100) DEFAULT '',
club_nr2 VARCHAR(100) DEFAULT '',
club_nr3 VARCHAR(100) DEFAULT '',
club_nr4 VARCHAR(100) DEFAULT '',
club_nr5 VARCHAR(100) DEFAULT '',
eqsl_qsl_sent varchar(1) default '' not null,
eqsl_qslsdate date default null,
eqsl_qsl_rcvd varchar(1) default '' not null,
eqsl_qslrdate date default null,
rxfreq NUMERIC(10,4) NULL,
satellite VARCHAR(30) DEFAULT '',
prop_mode VARCHAR(30) DEFAULT '',
contestname VARCHAR(40) NULL,
stx VARCHAR(6) NULL,
srx VARCHAR(6) NULL,
stx_string VARCHAR(50) NULL,
srx_string VARCHAR(50) NULL
);

TApplication.HandleException TMySQL57Connection : Error executing query: Table 'cqrlog_main' already exists
Stack trace:
$00000000009355DF
$0000000000936CC8
$00000000006E4E0A
$00000000006E5653
$00000000006E4CF6
$00000000004311CF
$000000000067355D
$0000000000848302
$000000000085A361
select log_nr from cqrlog_common.log_list order by log_nr

select log_nr from cqrlog_common.log_list where log_nr = 2

CREATE DATABASE IF NOT EXISTS cqrlog002 DEFAULT CHARACTER SET = utf8 DEFAULT COLLATE = utf8_bin;

use cqrlog002;

CREATE TABLE cqrlog_main (
id_cqrlog_main INT AUTO_INCREMENT PRIMARY KEY,
qsodate DATE NOT NULL,
time_on VARCHAR(5) NOT NULL,
time_off VARCHAR(5) DEFAULT '',
callsign VARCHAR(20) NOT NULL,
freq NUMERIC(10,4) NOT NULL,
mode VARCHAR(12) NOT NULL,
rst_s VARCHAR(20) DEFAULT '',
rst_r VARCHAR(20) DEFAULT '',
name VARCHAR(40) DEFAULT '',
qth VARCHAR(60) DEFAULT '',
qsl_s VARCHAR(4) DEFAULT '',
qsl_r VARCHAR(3) DEFAULT '',
qsl_via VARCHAR(30) DEFAULT '',
iota VARCHAR(6) DEFAULT '',
pwr VARCHAR(10) DEFAULT '',
itu INT DEFAULT 0,
waz INT DEFAULT 0,
loc VARCHAR(10) DEFAULT '',
my_loc VARCHAR(10) DEFAULT '',
county VARCHAR(30) DEFAULT '',
award VARCHAR(50) DEFAULT '',
remarks VARCHAR(200) DEFAULT '',
adif INTEGER DEFAULT 0,
/*dxcc_ref VARCHAR(20) DEFAULT '',*/
band VARCHAR(6) DEFAULT '',
qso_dxcc INT DEFAULT 0,
profile INT DEFAULT 0,
idcall VARCHAR(20) DEFAULT '',
state VARCHAR(4) DEFAULT '',
lotw_qslsdate DATE,
lotw_qslrdate DATE,
lotw_qsls VARCHAR(3) DEFAULT '' not null,
lotw_qslr VARCHAR(3) DEFAULT '' not null,
cont VARCHAR(3) DEFAULT '',
qsls_date VARCHAR(10),
qslr_date VARCHAR(10),
club_nr1 VARCHAR(100) DEFAULT '',
club_nr2 VARCHAR(100) DEFAULT '',
club_nr3 VARCHAR(100) DEFAULT '',
club_nr4 VARCHAR(100) DEFAULT '',
club_nr5 VARCHAR(100) DEFAULT '',
eqsl_qsl_sent varchar(1) default '' not null,
eqsl_qslsdate date default null,
eqsl_qsl_rcvd varchar(1) default '' not null,
eqsl_qslrdate date default null,
rxfreq NUMERIC(10,4) NULL,
satellite VARCHAR(30) DEFAULT '',
prop_mode VARCHAR(30) DEFAULT '',
contestname VARCHAR(40) NULL,
stx VARCHAR(6) NULL,
srx VARCHAR(6) NULL,
stx_string VARCHAR(50) NULL,
srx_string VARCHAR(50) NULL
);

CREATE INDEX main_index ON cqrlog_main(qsodate DESC,time_on DESC);

CREATE INDEX callsign ON cqrlog_main(callsign);

CREATE INDEX name ON cqrlog_main(name);

CREATE INDEX qth ON cqrlog_main(QTH);

CREATE INDEX adif ON cqrlog_main(adif);

CREATE INDEX idcall ON cqrlog_main(idcall);

CREATE INDEX band ON cqrlog_main(band);

CREATE INDEX club_nr1 ON cqrlog_main(club_nr1);

CREATE INDEX club_nr2 ON cqrlog_main(club_nr2);

CREATE INDEX club_nr3 ON cqrlog_main(club_nr3);

CREATE INDEX club_nr4 ON cqrlog_main(club_nr4);

CREATE INDEX club_nr5 ON cqrlog_main(club_nr5);

CREATE TABLE notes(
id_notes INT AUTO_INCREMENT PRIMARY KEY,
callsign VARCHAR(20) DEFAULT '',
longremarks VARCHAR(256) DEFAULT ''
);

CREATE INDEX callsign ON notes(callsign);

CREATE TABLE profiles (
id_profiles INT AUTO_INCREMENT PRIMARY KEY,
nr INT NOT NULL,
locator VARCHAR(6) DEFAULT '',
qth VARCHAR(250) DEFAULT '',
rig VARCHAR(250) DEFAULT '',
remarks VARCHAR(250) DEFAULT '',
visible INT DEFAULT 1
);

CREATE INDEX nr ON profiles(nr);

CREATE TABLE long_note (
id_long_note INT AUTO_INCREMENT PRIMARY KEY,
note LONGTEXT
);

CREATE TABLE version (
major INTEGER DEFAULT 0,
minor INTEGER DEFAULT 9,
releas INTEGER DEFAULT 4
);

CREATE TABLE club1 (
id_club1 INT AUTO_INCREMENT PRIMARY KEY,
club_nr VARCHAR(100) DEFAULT '',
clubcall VARCHAR(100) DEFAULT '',
fromdate DATE,
todate DATE
);

CREATE INDEX club_nr ON club1(club_nr);

CREATE INDEX fromdate ON club1(fromdate);

CREATE INDEX todate ON club1(todate);

CREATE INDEX clubcall ON club1(clubcall);

CREATE TABLE club2 (
id_club2 INT AUTO_INCREMENT PRIMARY KEY,
club_nr VARCHAR(100) DEFAULT '',
clubcall VARCHAR(100) DEFAULT '',
fromdate DATE,
todate DATE
);

CREATE INDEX club_nr ON club2(club_nr);

CREATE INDEX fromdate ON club2(fromdate);

CREATE INDEX todate ON club2(todate);

CREATE INDEX clubcall ON club2(clubcall);

CREATE TABLE club3 (
id_club3 INT AUTO_INCREMENT PRIMARY KEY,
club_nr VARCHAR(100) DEFAULT '',
clubcall VARCHAR(100) DEFAULT '',
fromdate DATE,
todate DATE
);

CREATE INDEX club_nr ON club3(club_nr);

CREATE INDEX fromdate ON club3(fromdate);

CREATE INDEX todate ON club3(todate);

CREATE INDEX clubcall ON club3(clubcall);

CREATE TABLE club4 (
id_club4 INT AUTO_INCREMENT PRIMARY KEY,
club_nr VARCHAR(100) DEFAULT '',
clubcall VARCHAR(100) DEFAULT '',
fromdate DATE,
todate DATE
);

CREATE INDEX club_nr ON club4(club_nr);

CREATE INDEX fromdate ON club4(fromdate);

CREATE INDEX todate ON club4(todate);

CREATE INDEX clubcall ON club4(clubcall);

CREATE TABLE club5 (
id_club5 INT AUTO_INCREMENT PRIMARY KEY,
club_nr VARCHAR(100) DEFAULT '',
clubcall VARCHAR(100) DEFAULT '',
fromdate DATE,
todate DATE
);

CREATE INDEX club_nr ON club5(club_nr);

CREATE INDEX fromdate ON club5(fromdate);

CREATE INDEX todate ON club5(todate);

CREATE INDEX clubcall ON club5(clubcall);

CREATE TABLE zipcode1 (
id_zipcode1 INT AUTO_INCREMENT PRIMARY KEY,
zip VARCHAR(20) DEFAULT '',
county VARCHAR(100) DEFAULT ''
);

CREATE INDEX zip ON zipcode1(zip);

CREATE TABLE zipcode2 (
id_zipcode2 INT AUTO_INCREMENT PRIMARY KEY,
zip VARCHAR(20) DEFAULT '',
county VARCHAR(100) DEFAULT ''
);

CREATE INDEX zip ON zipcode2(zip);

CREATE TABLE zipcode3 (
id_zipcode3 INT AUTO_INCREMENT PRIMARY KEY,
zip VARCHAR(20) DEFAULT '',
county VARCHAR(100) DEFAULT ''
);

CREATE INDEX zip ON zipcode3(zip);

CREATE TABLE cqrlog_config (
id_cqrlog__config INT AUTO_INCREMENT PRIMARY KEY,
config_file LONGTEXT
);

INSERT INTO cqrlog_config (config_file) VALUES ('');

CREATE TABLE dxcc_id
(
id_dxcc INT AUTO_INCREMENT PRIMARY KEY,
adif INT DEFAULT 0,
dxcc_ref VARCHAR(16) NOT NULL,
country VARCHAR(100) NOT NULL
);

CREATE INDEX adif ON dxcc_id(adif);

CREATE TABLE db_version
(
nr SMALLINT NOT NULL
);

CREATE TABLE log_changes (
id int NOT NULL AUTO_INCREMENT PRIMARY KEY,
id_cqrlog_main int(11) NULL,
cmd varchar(20) NOT NULL,
qsodate date NULL,
time_on varchar(5) NULL,
callsign varchar(20) NULL,
mode varchar(12) NULL,
band varchar(6) NULL,
freq numeric(10,4) NULL,
old_qsodate date NULL,
old_time_on varchar(5) NULL,
old_callsign varchar(20) NULL,
old_mode varchar(12) NULL,
old_band varchar(6) NULL,
old_freq numeric(10,4) NULL,
upddeleted int(1) default 1
) COLLATE 'utf8_bin';

ALTER TABLE log_changes
ADD INDEX id_cqrlog_main (id_cqrlog_main);

ALTER TABLE log_changes
ADD FOREIGN KEY (id_cqrlog_main) REFERENCES cqrlog_main (id_cqrlog_main) ON DELETE SET NULL ON UPDATE CASCADE;

CREATE TABLE upload_status (
id int NOT NULL AUTO_INCREMENT PRIMARY KEY,
logname varchar(30) NOT NULL,
id_log_changes int(11) NULL,
FOREIGN KEY (id_log_changes) REFERENCES log_changes (id) ON DELETE SET NULL
) COLLATE 'utf8_bin';

CREATE TABLE call_alert (
id int NOT NULL AUTO_INCREMENT PRIMARY KEY,
callsign varchar(20) NOT NULL,
band varchar(6) NULL,
mode varchar(12) NULL
) COLLATE 'utf8_bin';

ALTER TABLE call_alert ADD INDEX (id);

ALTER TABLE call_alert ADD INDEX (callsign);

CREATE TABLE freqmem (
id int NOT NULL AUTO_INCREMENT PRIMARY KEY,
freq numeric(10,4) NOT NULL,
mode varchar(12) NOT NULL,
bandwidth int NOT NULL,
info varchar(25) NULL
) COLLATE 'utf8_bin';

CREATE VIEW view_cqrlog_main_by_qsodate AS SELECT id_cqrlog_main,qsodate,time_on,time_off,callsign, freq,mode,rst_s,rst_r,name,qth,qsl_s,qsl_r,qsl_via,iota,pwr,itu,waz,loc,my_loc,county,
award,remarks, band, dxcc_id.dxcc_ref AS dxcc_ref ,qso_dxcc, profile,idcall, state, lotw_qslsdate, lotw_qslrdate,lotw_qsls, lotw_qslr, cont, qsls_date,qslr_date,club_nr1,club_nr2,club_nr3,
club_nr4, club_nr5, eqsl_qsl_sent, eqsl_qslsdate, eqsl_qsl_rcvd,eqsl_qslrdate,concat(qsl_r,lotw_qslr,eqsl_qsl_rcvd) as qslr,dxcc_id.country, rxfreq, satellite, prop_mode, srx, stx, srx_string, stx_string, contestname FROM cqrlog_main JOIN dxcc_id ON dxcc_id.adif = cqrlog_main.adif order by qsodate DESC, time_on DESC;

CREATE VIEW view_cqrlog_main_by_qsodate_asc AS SELECT id_cqrlog_main,qsodate,time_on,time_off,callsign, freq,mode,rst_s,rst_r,name,qth,qsl_s,qsl_r,qsl_via,iota,pwr,itu,waz,loc,my_loc,county,
award,remarks, band, dxcc_id.dxcc_ref AS dxcc_ref ,qso_dxcc, profile,idcall, state, lotw_qslsdate, lotw_qslrdate,lotw_qsls, lotw_qslr, cont, qsls_date,qslr_date,club_nr1,club_nr2,club_nr3,
club_nr4,club_nr5,eqsl_qsl_sent,eqsl_qslsdate,eqsl_qsl_rcvd,eqsl_qslrdate,concat(qsl_r,lotw_qslr,eqsl_qsl_rcvd) as qslr,dxcc_id.country, rxfreq, satellite, prop_mode, srx, stx, srx_string, stx_string, contestname FROM cqrlog_main JOIN dxcc_id ON dxcc_id.adif = cqrlog_main.adif order by qsodate ASC, time_on ASC;

CREATE VIEW view_cqrlog_main_by_callsign AS SELECT id_cqrlog_main,qsodate,time_on,time_off,callsign, freq,mode,rst_s,rst_r,name,qth,qsl_s,qsl_r,qsl_via,iota,pwr,itu,waz,loc,my_loc,county,
award,remarks, band, dxcc_id.dxcc_ref AS dxcc_ref ,qso_dxcc, profile,idcall, state, lotw_qslsdate, lotw_qslrdate,lotw_qsls, lotw_qslr, cont, qsls_date,qslr_date,club_nr1,club_nr2,club_nr3,
club_nr4,club_nr5,eqsl_qsl_sent,eqsl_qslsdate,eqsl_qsl_rcvd,eqsl_qslrdate,concat(qsl_r,lotw_qslr,eqsl_qsl_rcvd) as qslr,dxcc_id.country, rxfreq, satellite, prop_mode, srx, stx, srx_string, stx_string, contestname FROM cqrlog_main JOIN dxcc_id ON dxcc_id.adif = cqrlog_main.adif order by callsign;

insert into db_version (nr) values(16)

insert into cqrlog_common.log_list (log_nr,log_name) values (2,'cqrlog002')

insert into log_changes (id,cmd) values(1,'ALLDONE')

insert into upload_status (logname, id_log_changes) values ('HamQTH',1)

insert into upload_status (logname, id_log_changes) values ('ClubLog',1)

insert into upload_status (logname, id_log_changes) values ('HRDLog',1)

SELECT log_nr,log_name FROM cqrlog_common.log_list order by log_nr

SELECT log_nr,log_name FROM cqrlog_common.log_list order by log_nr

TApplication.HandleException Access violation
Stack trace:
$000000000051C0C2
$00000000006E4E0A
$00000000006E5653
$00000000006E4CF6
$00000000004311CF
$000000000067355D
$0000000000848302
$000000000085A361
Closing DXCluster window
Closing TRXControl window
Closing GrayLine window
Closing dDXCC
Deleting config file: cqrlog.cfg
Closing dData
Closing ini file ...
USERid@cedar:~/installs/cqrlog/cqrlog-2.4.0/usr/bin$

File: 

Cheers, 73 & Good DX

oh1kh
Unable to connect to MySQL vers 8.0 database UPDATE

Good morning!

Nice to see that you have managed to install MariaDB and cqrlog.

Package installing is problem.Specially if package is not up to date. I do not have experience with Ubuntu installer, but with Fedora there is parameter "no-deps" (not sure about syntax, it is so long that I last used it) but it does not install dependencies of package.

Cqrlog is very easy to install from .tgz ("for other systems", the last selection in download page) using command console and command tar.
Then only program itself is installed and user have to install all dependencies and also startup icons manually.

It is also possible to "save" cqrlog installed from package. Just copy file /usr/bin/cqrlog and folder /usr/share/cqrlog with all files and subfolders. Those two holds the whole program. third item is ~/.config/cqrlog folder with its files and subfolders It holds your logs and settings. That one is not touched if you remove cqrlog package from package manger.

After remove you can restore those saved two items back to their places (you need to use sudo) and you have again running cqrlog. Be aware that package manager may remove some dependencies needed and also startup icons. Those you have to restore manually. Just like when doing install with tar from .tgz file.
After that you have cqrlog, but your package manager does not know anything about it.

What ever you have done I recommend to update cqrlog after that. Package version is very old and buggy.
You can either compile latest version from source:
https://cqrlog.com/node/2984
https://cqrlog.com/node/2998

Or try to use ready compiled version. It may not work with all versions of linux because it is done with Fedora32. But many users have it running ok.
https://github.com/OH1KH/cqrlog/tree/loc_testing/compiled

--
Saku
OH1KH

oh1kh
Unable to connect to MySQL vers 8.0 database

Here is what I mean:

File: 

--
Saku
OH1KH

VE4PER
VE4PER's picture
Unable to connect to MySQL vers 8.0 database

Here is results of err.log info saved in ~/.config/cqrlog/database it seems to point at not finding the expected database on the server. This makes sense to me as neither I nor the CQRLOG program initialization process created said data directory and dictionary.

20-11-03T16:48:17.311055Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.22-0ubuntu0.20.04.2) starting as process 32439
2020-11-03T16:48:17.312063Z 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-11-03T16:48:17.312070Z 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-11-03T16:48:17.405807Z 1 [ERROR] [MY-011011] [Server] Failed to find valid data directory.
2020-11-03T16:48:17.406368Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2020-11-03T16:48:17.406575Z 0 [ERROR] [MY-010119] [Server] Aborting
2020-11-03T16:48:17.407714Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.22-0ubuntu0.20.04.2) (Ubuntu).
2020-11-11T04:05:08.791982Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.22-0ubuntu0.20.04.2) starting as process 110203
2020-11-11T04:05:08.792857Z 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-11-11T04:05:08.792864Z 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-11-11T04:05:08.902142Z 1 [ERROR] [MY-011011] [Server] Failed to find valid data directory.
2020-11-11T04:05:08.902274Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2020-11-11T04:05:08.902326Z 0 [ERROR] [MY-010119] [Server] Aborting
2020-11-11T04:05:08.902652Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.22-0ubuntu0.20.04.2) (Ubuntu).
2020-11-11T04:17:00.560431Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.22-0ubuntu0.20.04.2) starting as process 110701
2020-11-11T04:17:00.561031Z 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-11-11T04:17:00.561038Z 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-11-11T04:17:00.565857Z 1 [ERROR] [MY-011011] [Server] Failed to find valid data directory.
2020-11-11T04:17:00.565980Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2020-11-11T04:17:00.566027Z 0 [ERROR] [MY-010119] [Server] Aborting
2020-11-11T04:17:00.566314Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.22-0ubuntu0.20.04.2) (Ubuntu).
2020-11-11T07:34:32.966982Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.22-0ubuntu0.20.04.2) starting as process 6492
2020-11-11T07:34:32.967712Z 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-11-11T07:34:32.967720Z 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-11-11T07:34:33.541114Z 1 [ERROR] [MY-011011] [Server] Failed to find valid data directory.
2020-11-11T07:34:33.541499Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2020-11-11T07:34:33.541651Z 0 [ERROR] [MY-010119] [Server] Aborting
2020-11-11T07:34:33.542445Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.22-0ubuntu0.20.04.2) (Ubuntu).

Cheers, 73 & Good DX

dl1mtg
dl1mtg's picture
Unable to connect to MySQL vers 8.0 database

Hello Andrew,

the error message "/usr/sbin/mysqld (mysqld 8.0.22-0ubuntu0.20.04.2)" let me guess, you have installed mysql-server!

Saku explained some lines before how to change to mariadb, see the links / comments.
mariadb is working flawlessly with cqrlog and ubuntu 20.

Good luck

--
73 de Martin, DL1MTG

VE4PER
VE4PER's picture
reur reply to Una 2 connect to MySQL vers 8.0 database UPDATE 2

No there is NO mySQL V 8.0 install. ALL was removed and MariadB 10.3 was installed. When attempts to install CQRLOG from PPA sources using command line apt install or synaptic manager the install process warned that it would remove ALL mariaDB files and re-install MySQL v 8.0 instead> I did not use those options. I had to use the tarball option and install it manually so that I had CQRLOG working with MariaDB only as Petri reccommended. I did however there is some glitches still in the system, i SUSPECT are missing dependency related as the databases get created but any further options to edit or view usually lock up and freeze the program so can't say it is fully functional at this point. I have posted a note in the forum here to see if anyone has a completed list of ubuntustudio 20.04LTS dependencies I need to confirm are installed; to date I have yet to see a list. I did see a post that suggested a qt5 related lib file was needed that I installed but that appears to be OK but ithers may be missing also. So it is an ongoing saga for me now.

Cheers, 73 & Good DX