I unclicked the Upload immediately option then tried the menu Online Log / QRZ,com / Upload all changes.
I got the window saying:
_QRZLog: INSERT F1PPH
_QRZLog: INSERT GEYUE
_QRZLog: ACTION missing in request
_QRZLog: Failed - check with debug!
I wish that there was just a working pair of Up and Down load buttons like there are for LoTW & eQSL.
21 August 2026
Carl - WC4H / HI3CHI unclicked the Upload immediately option then tried the menu Online Log / QRZ,com / Upload all changes.
I got the window saying:
_QRZLog: INSERT F1PPH
_QRZLog: INSERT GEYUE
_QRZLog: ACTION missing in request
_QRZLog: Failed - check with debug!
I wish that there was just a working pair of Up and
Well. QRZlog is only for upload.
AI says:
QRZ Logbook, export your contacts as an ADIF (.adi) file from your logging software (like WSJT-X or Log4OM). Then, open your QRZ logbook, go to Settings > Import/Export ADIF, choose your file, and click Upload.
I have never tested that. But when QRZlog and others are all up to date with Cqrlog you can use QSOlist-Online logs-> "Mark EVERY QSO as uploaded to ALL logs"
That will clean up the upload_status and log_changes tables.
It is also good to have Preferences/Online log upload/ two checkboxes checked:
"Close the 'Status of log upload' windows after succesfull upload" and "When closing do AutoClean to table log_changes if everything is uploaded (keeps table small)"
Carl - WC4H / HI3CHI unclicked the Upload immediately option then tried the menu Online Log / QRZ,com / Upload all changes.
I got the window saying:
_QRZLog: INSERT F1PPH
_QRZLog: INSERT GEYUE
_QRZLog: ACTION missing in request
_QRZLog: Failed - check with debug!
I wish that there was just a working pair of Up and
I have never faced "Action missing in request" from QRZ.
After implemented QRZlog I have mostly used "immediately upload" for all online logs to see how they all work.
So far just some breaks with HamQTH and HRDlog because of server side problem, but they have fixed themself after servers have been back online.
It would be interesting to see the debug if "Action missing in request" repeats itself.
cqrlog —debug=-256
will show just online log debugs. Note the negative debug number.
Saku OH1KHI have never faced "Action missing in request" from QRZ.
After implemented QRZlog I have mostly used "immediately upload" for all online logs to see how they all work.
So far just some breaks with HamQTH and HRDlog because of server side problem, but they have fixed themself after servers have been
Does it create a debug file? I don't see one. Do I need to copy the screen content?
Файл
CqrlogImproved_Qt6_SRC_Manual_EN.pdf · 302 KB · click to show
CqrlogImproved_Qt6_SRC_Manual_EN.pdf · 302 KB · click to show
Subject: CqrlogImproved Qt6 Installation Guide – Safe SRC Build and Database Migration
Hello,
I am attaching a prepared CqrlogImproved Qt6 installation and configuration guide. It describes, step by step, how to build the program from source (SRC), prepare the required libraries, create the Qt6 environment, configure MariaDB and Hamlib, and integrate the program into the Linux desktop application menu.
The main purpose of this guide is to make CqrlogImproved installation as safe and predictable as possible, especially in regard to existing CQRLOG databases. In practice, database migration problems are quite common when moving between CQRLOG versions. Typical causes include differences between MariaDB versions, use of the wrong data directory, incompatible database schema changes, or accidental overwriting of an existing configuration.
For this reason, the guide gives particular attention to data protection and recovery. Before any changes are made, a complete backup of the existing CQRLOG environment is c
Subject: CqrlogImproved Qt6 SRC Installation Manual
Hello,
Thank you for accepting my CqrlogImproved Qt6 SRC installation manual.
If you consider it useful for other users, I would be very happy if the manual could also be published on the CQRLOG/CqrlogImproved website, documentation section, GitHub repository, or another appropriate place related to the project.
The manual is intended to help users install CqrlogImproved from source with fewer problems, especially when dealing with MariaDB databases, existing logbooks, configuration migration, Qt6 and the required runtime libraries.
At the moment I have prepared the manual in English and Latvian.
If there is interest, I can also prepare the same manual in other languages or adapt the description for a website/documentation page.
Thank you for your work on CqrlogImproved and for making the project available to the amateur radio community.
Best regards,
Arnis Armans, YL3GBC
Saku OH1KHNope.
cqrlog —debug=-256 > /tmp/debug.txt
That did not create a debug file either. I also tried to put it into /home/myuser/.local/tmp and it did not create a file.
22 August 2026
Carl - WC4H / HI3CHThat did not create a debug file either. I also tried to put it into /home/myuser/.local/tmp and it did not create a file.
If you see debug text with
cqrlog —debug=-256
in command console then redirecting it to file is done with arrow right followed by path and file name.
26 August 2026
1 September 2026
2 September 2026
Фотография
click to show
click to show
GA everybody,
while doing some QSL card management, I just recognized, a QS_R date ist shown, although card isn't confirmed. Column qslr is empty.
If I type Ctrl-R for Card received, that column is correctly shown Q and QS_R is updated with todays date.
So I'm wondering, where the initial date in QS_R is coming from ...
Rolf SchmidtGA everybody,
while doing some QSL card management, I just recognized, a QS_R date ist shown, although card isn't confirmed. Column qslr is empty.
If I type Ctrl-R for Card received, that column is correctly shown Q and QS_R is updated with todays date.
So I'm wondering, where the initial date in
Фотография
click to show
click to show
This view is from CqrlogImproved.
At least there seems to be problem with qslr_date that is set to current date.
Note that the qsl_r and qsrl and their dates are different.
While qsl_r means paper card qslr means combination of all confirmations.
ToDo:
qslr_date needs fixing it cannot be current date, it should be first date of any of the confirmations received.
Rolf SchmidtGA everybody,
while doing some QSL card management, I just recognized, a QS_R date ist shown, although card isn't confirmed. Column qslr is empty.
If I type Ctrl-R for Card received, that column is correctly shown Q and QS_R is updated with todays date.
So I'm wondering, where the initial date in
Forgot to mention that also status line (below grid) needs fix. It takes now value from qslr_date and claims it is qsl_r_date
Фотография
click to show
click to show
Hello Saku, thank you for your reply. Now I understood, checkmark QSL sent maps to qsl_s column. Received QSL (all in one) maps to qsl_r.
In detail panel QS_S is derived from the date, where I trigger the QSL-Print. LoTW-QS_S/R is showing correct dates (see next image).
But I have no idea, which activity sets QS_R date in detail panel. In your example, it's today. In my case it's set to last week friday.
3 September 2026
Rolf SchmidtGA everybody,
while doing some QSL card management, I just recognized, a QS_R date ist shown, although card isn't confirmed. Column qslr is empty.
If I type Ctrl-R for Card received, that column is correctly shown Q and QS_R is updated with todays date.
So I'm wondering, where the initial date in
WARNING!
There is a serious bug in Cqrlog_Improved:
If you mark QSL (paper) received as "Q" by NewQSO/Edit qso
and save edited qso that will turn all qsl_r_dates to current date in WHOLE LOG !
That happens because qsl_r_date is updated to log database without the ID of selected qso.
It is safe to mark QSL received via QSO_list using Ctrl+R key
This affects to versions 142(2026-05-12), 143(2026-06-12) and 144(2026-08-01).
I am very sorry for this inconvenience. It will be fixed in release 145.