Hello,
The topic has been discussed. After a few QSOs added to CQRlog, I end up with this message:
TMySQL57Connection : Error executing query: Server has gone away.
Press OK to ignore and risk data corruption.
Press Abort to kill the program.
Linux Mint 2.13 up to date Cinnamon 6.0.4
CQRlog Alpha 132 GtK2
Server version: 10.6.18-MariaDB-0ubuntu0.22.04.1 Ubuntu 22.04
The problem is random. Am I the only one in this case? Do you have a solution. I did some research on the internet but the problem persists.
Ps: by re-installing the Alpha 119 version .... everything is ok.
73 Yves F5JQF
Hi Yves!
Yes, this has been discussed a long time ago.
Problem usually happens if Cqrlog stays running idle for long time. Whole day, or over the night.
But as you say it is very random.
Normally restarting Cqrlog removes this problem.
We did many tests in past to resolve this problem, but without luck. Reason is the MariaDB connection (there are several of them open while running) that closes for timeout because of no traffic for long time.
--
Saku
OH1KH
Hi Saku,
First of all thanks for answering. I appreciate your work and I try every time your updates of CQRlog Alpha xxx. I also followed your exchanges on the forum about this problem which is very random.
I downgraded my version of CQRlog by copying the binary 119 instead of 132. In the same operating configuration of CQRlog (DXcluster, RBN, Map, BandMap and remote in service with Wsjt-z and all in automatic) everything works very well.
Maybe a difference in the source code between 119 and the following versions?.
In the meantime thank you for what you do.
73, Yves F5JQF
73 Yves, F5JQF
[ CQRlog Ver.Alpha_(xxx)_Gtk2 / Hamlib 4.7 / Linux Mint 22.1 Cinnamon 6.4.6 ]
..
HI!
While struggling with other sql query problems I found this parameter that may be worth of testing .
It should reconnect client if server connection is lost. I think it has never been tried (as long as I remember)
Via that line it is possible to add msql client parameter "--reconnect" to created connection.
From same source if found a way to make simple database ping.
Ping has been tried with Cqrlog by the long way where where timer has started a true database query.
Timer is still there but the part of source is commented out (disabled) at some version.
How ever the long code can be replaced with simple line:
mysql_ping(<connection_name>)
I think I try those next, even I can not see "server has gone away" here (due to shutting PC down when I am not in shack)
--
Saku
OH1KH
Hello Saku,
Thanks for this information. I appreciate your maintenance work for the Alpha version. At my level I think I can't make this change in the source code. If this change solves the problem it would be really great!..
For my part, I reconfigured my "PC Radio" with a clean distribution, compiled the latest Alpha 135 GtK2 configured the whole thing to support 4 transceivers. During traffic adding a QSO can crash CqrLog or not, including in remote control mode. Second observation, when leaving CqrLog (CTRL+Q) the log backup starts and the crash appears with the message "TMySQL57Connection etc..."
Back to the binary of the Alpha 119 version instead of the 135 and everything is ok!..
In the meantime, a big thank you again and hats off (French expression to salute your efforts!)
73 Yves, F5JQF
[ CQRlog Ver.Alpha_(xxx)_Gtk2 / Hamlib 4.7 / Linux Mint 22.1 Cinnamon 6.4.6 ]
..
Ok!
Forgot the mysql_options line.
Although it compiles ok it does cause a runtime crash.
(134) should be also quite stable. You find sources for that at https://github.com/OH1KH/CqrlogAlpha/tree/main
There is also branch "devel" that is now used instead of "loc_testing"
--
Saku
OH1KH