Hi
I know this issue has been the subject of several inquires, but I have been unable to fix the issue on my system after applying the various fixes.
When starting CQRlog, I get the TMySQL57connection - Server connect fail.
I ran the program with --debug=1 option and found:
Could not open required defaults file /home/larrie/.config/crqlog/database/mysql.cnf
fatal error in defaults handling
These errors have been discussed before and I have followed all of the suggestions, but nothing seems to work. I have uninstalled and reinstalled the program, taking care to remove all files so that when cqrlog starts it comes up as a first time run. I select save data to local machine, then get the error box called " database problem" with the suggestion to see if mysql is properly installed. For some reason, no mysql.err file is made. It doesn't open when clicking on the button in the box and I cannot find the file on my computer.
This is a freshly installed ubuntu 20.04. I noticed that under the synaptic package installer, there are many versions, flavors of mysql. Could it be I don't all of correct packages installed?
Thanks for any suggestions.
Larrie, AF7NU
Hello Larrie,
I tried to find a simple and good working solution for cqrlog and ubuntu 20.04 users.
It all depends on the mysql server version.
Can you try this please:
sudo apt-get install libcanberra-gtk-module mariadb-server-10.3 mariadb-client-10.3 cqrlog
What happend:
The mysql server is changed to MariaDB - should not make any difference to cqrlog users.
Then use this command to start cqrlog:
dbus-launch --exit-with-session cqrlog
I tested it here with a fresh Ubuntu 20.04 64bit installation and these are the commands to startup cqrlog fast and easy.
73 de Martin, DL1MTG
--
73 de Martin, DL1MTG
DL1MTG's solution worked perfectly to correct CQRLOG after an upgrade from 18.04 LTS to 20.04.
Thanks,
Steve, N8IFQ
Hi,
I have a fresh xubuntu 20.04 and the trick doesn't work for me. Always the same error : unable to connect to mysql. The error file is empty.
I have tried with mysql and mariadB.
Any solution ?
Phil, F5OWL
I have just noticed that mariadb was not installed properly :
$ sudo apt-get install libcanberra-gtk-module mariadb-server-10.3 mariadb-client-10.3 cqrlog
....
Paramétrage de mariadb-server-10.3 (1:10.3.22-1ubuntu1) ...
Created symlink /etc/systemd/system/mysql.service → /lib/systemd/system/mariadb.service.
Created symlink /etc/systemd/system/mysqld.service → /lib/systemd/system/mariadb.service.
Created symlink /etc/systemd/system/multi-user.target.wants/mariadb.service → /lib/systemd/system/mariadb.service.
Job for mariadb.service failed because a timeout was exceeded.
See "systemctl status mariadb.service" and "journalctl -xe" for details.
.....
$ systemctl status mariadb.service
mariadb.service - MariaDB 10.3.22 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Active: failed (Result: timeout) since Fri 2020-05-29 15:50:10 CEST; 3min 30s ago
Docs: man:mysqld(8)
https://mariadb.com/kb/en/library/systemd/
Main PID: 14682 (code=exited, status=0/SUCCESS)
mai 29 15:35:08 jupiter systemd[1]: Starting MariaDB 10.3.22 database server...
mai 29 15:35:08 jupiter mysqld[14682]: 2020-05-29 15:35:08 0 [Note] /usr/sbin/mysqld (mysqld 10.3.22-MariaDB-1ubuntu1) starting as process 14682 ...
mai 29 15:50:08 jupiter systemd[1]: mariadb.service: start operation timed out. Terminating.
mai 29 15:50:10 jupiter systemd[1]: mariadb.service: Failed with result 'timeout'.
mai 29 15:50:10 jupiter systemd[1]: Failed to start MariaDB 10.3.22 database server.
~
After I see this spot : https://cqrlog.com/node/2475
I knew I had to reboot.
I knonw it works.
Great
73
I really don't know why the conflict occurs when the DXCC and Manager update boxes are active.
After doing countless tests, I discovered that the error was here.
I hope that it helps someone as it did me and that it can be solved more deeply.
Greetings
Carl
translated by Google
File:
Hi!
https://www.cqrlog.com/comment/11598#comment-11598
dxcc update package has MASTER.SCP file that has too big size
--
Saku
OH1KH