CQRLOG - bugs

Timeout when running CQRLOG towards MySQL / MariaDB under Linux

The reason for the timeout is the MySQL server timing out on "wait_timeout". This is a parameter in the

/etc/mysql/my.cnf

under

[mysqld]
wait_timeout=28800

It is set to the above value in the normal case. That is why it times out after eight hours. To make it easier to debug the timeout it can be set to e.g. 300 which is five minutes. Note that this change affect all sessions on the MySQL / MariaDB server.

Of the 5 threads setup in src/dData.pas the four last ones time out for me:

Forums: 

Compiling in a Docker container

I tried compiling the CQRLOG in a Docker-image using the existing master branch.

Unfortunately the Dockerfile needs to be updated for the Docker compilation to work due to that the existing Dockerfile uses

FROM ubuntu:eoan

With that version you get a number of missing release files when you try to build the CQRLOG according to the instructions.
FYI also using ubuntu:latest (=focal) will currently not work due to tzdata problems.

Forums: 

Problem with QRZ and HamQTH

Hello everybody,

I encounter problems when I log several QSOs. After every 3 or 4 QSOs cqrlog stucks for up to 3 minutes with increased cpu usage before letting me continue to do the log. After restart of cqrlog everything starts all over again.
A few days ago I discussed that with Petr and it looked like QRZ.com would be the problem. So I switched to hamQTH and it worked for a while. But today I encouter that problem no matter which service I use.

Does anyone else have that issue with version 2.5.2 on a raspberry pi 4?

Forums: 

Callbook field does not get cleared when typing a new call

When i type a call in the new qso window, and press tab, call info gets looked up at QRZ.com.
At the lower right a call + name apears

Then when i double click the call to get it selected and type a different call and press tab, the new call info gets retrieved, but in the lower richt , the call and name of the new call gets added instead of "replaced"
When the new qrz info gets retrieved, this field is not cleared.
For as far as i remember, this used to be the case.

Forums: 

flrig -> cqrlog -> wsjtx

Hi
I have a problem. I have configured cqrlog to work with flrig and here everything works. Unfortunately when I give in cqrlog "remote for wsjtx" and wsjtx configure with flrig this one is not cooperating with working with two vfo. When I configure cqrlog to work with hamlib (Yaesu dx3000) and the same wsjtx there is again the same problem. Only when I run wsjtx alone and configure it to work with hamlib(dx3000) there is not this problem. Anyone encountered something like this?
System: OpenSUSE Tumbleweed

Forums: 

cqrlog - All New Created Databases / Logs are Corrupted!

I am new to crqlog. It looks like it is exactly what I need for my logging needs.

I just installed crqlog 2.3.0-2 via apt on my old 32-bit PC running anti-X Linux.
(Anti-X 19 is based on Debian Buster).

The installation of cqrlog and all its dependencies was successful.

But when I try to open a new Database / Logfile, I see the following error:

"" is an invalid integer.
Press OK to ignore and risk data corruption.
Press Abort to kill the program"

I press OK and nothing happens.

Forums: 

Pages

Subscribe to RSS - CQRLOG - bugs