View Issue Details

IDProjectCategoryView StatusLast Update
0002316Ham Radio DeluxeBugpublic2018-06-13 09:13
Reporterk2ieAssigned ToK7ZCZ 
Status closedResolutionfixed 
PlatformOSWindows 10OS Version1709
Product Version 
Target VersionFixed in Version6.4.0.843 
Summary0002316: Intermittement API reports data added when data NOT added
DescriptionThe HRD API running on TCP/7826 reports that data has been added to the HRD Lobgook when it has not been added. This appears to occur where a remote MySQL/MariaDB database is being used.
Steps To Reproduce1 - Start rig control and logbook.
2 - Open a telnet session to localhost 7826.
3 - db add "K2DLS Logbook" { CALL="VK1ZZZ" NAME="Testing" DXCC="150" COUNTRY="Australia" STATE="ACT" QSO_DATE="20180126" QSO_DATE_OFF="20180126" TIME_ON="062030" TIME_OFF="062530" FREQ="14076000" FREQ_RX="14076000" BAND="20m" BAND_RX="20m" ADDRESS="Single address line" MODE="JT65" RST_SENT="-15" RST_RCVD="15" DISTANCE="250" COMMENT="JT65" CQZ="30" ITUZ="59" PFX="VK1" CONT="OC" MY_GRIDSQUARE="QF55mx" MY_CQ_ZONE="30" MY_ITU_ZONE="59" STATION_CALLSIGN="VK2BYI" QSO_COMPLETE="Y " }
4 - API reports: Found 27 Valid Fields...
Added 27 Fields to K2DLS Logbook...
5 - Check logbook. The data is not there.
6 - Try again.
7 - The data is still not there.
Additional InformationVK2BYI reported that as a kludge, an open local MS-Access HRD DB in the background somehow prevents this from occurring. I tried the kludge and the next insert worked.
TagsNo tags attached.
Testing Beta Successful


related to 0002720 assignedK7ZCZ 2 - Next Dev List (Holding Area) Logbook: Poor error handling when database opening fails 
related to 0002721 new 2 - Next Dev List (Holding Area) Documentation: YouTube video doesn't give complete instructions for switching to MariaDB 



2018-02-22 16:20

administrator   ~0004315

Changing status. Seems to be more work left.


2018-02-23 20:04

viewer   ~0004321

Defect still exists in build 790.

Error.png (12,568 bytes)
Error.png (12,568 bytes)


2018-05-24 13:06

developer   ~0005102

I think there are two causes to this issue.

One is that the default database used the HRDCLI is configurable; and it's possible that users end up in a state where that configuration is invalid after they delete the default database. They're likely to do so because we instruct them to (see related bug). In that state, the user has no idea they're incorrectly configured because we don't give a warning when the configured database is deleted; and we don't give an error at startup when the invalid configuration is observable.

Even if the database used for the network interfaces to the logbook is correctly configured, the insertion may fail for any number of reasons. There is no error handling in the HRDCLI code for the "add" verb. I've added some, so now we'll at least report an error if something goes wrong.

I've never been able to reproduce this problem, so I'm unfortunately doing a bit of inductive reasoning. But I think addressing those issues will remedy this problem for our customers.


2018-05-24 13:06

developer   ~0005103

I believe this issue is addressed with this checkin:


2018-05-29 14:55

viewer   ~0005138

Unable to test this due to insufficient knowledge.


2018-05-30 00:59

viewer   ~0005149

I have personal experience of this defect, and I know of several QSO Relay users that have also experienced it. The workaround has been to have an Access database tab open simultaneously to the desired MySQL/MariaDB or SQL Server database.

With installed, I closed the Access database and ran my usual suite of Logbook API test case scripts and the defect became evident. Refer to the ‘Test Case Results with’ attachment in which test case 06 (pages 2 and 3) passed with Logbook reporting it ‘Added 44 Fields to ‘My Logbook - MySQL...’, but test case 07 (page 3) failed as the contact logged in test 06 could not be found, Similar results with test cases 08 and 09 on pages 3 and 4.

I then installed and reran the same suite of tests, and this time they all passed without having the Access database open – just my MySQL logbook database.

In the past I have found that the I could still log contacts without the Access database being open on occasions, but it became my practice to keep it open to prevent it from reoccurring at an inopportune time. So, I will keep running the test case suite at various times over the next couple of days and report back. But at this stage it looks like it has been fixed.

Good work Mike B! This defect has some visibility in the JTAlert JT65/FT8 mode community, and I am sure this will be seen as a significant gain. A big ‘thumbs up’ from me at least. 73 Chris VK2BYI.

Test Case Results with (42,319 bytes)
Test Case Results with (42,255 bytes)


2018-05-30 08:34

viewer   ~0005153

Closed the "placebo tab" and then added 7 QSOs via JT Alert 2.10.17. No failures noted. DB is an external Maria DB. The change seems successful but I will continue to monitor.

Issue History

Date Modified Username Field Change
2018-01-26 10:44 k2ie New Issue
2018-01-29 14:18 Roger Assigned To => Roger
2018-01-29 14:18 Roger Status new => assigned
2018-01-29 14:18 Roger Testing => Not Started
2018-02-22 12:49 Roger Reproducibility always => random
2018-02-22 12:49 Roger Status assigned => resolved
2018-02-22 12:49 Roger Resolution open => no change required
2018-02-22 12:49 Roger Testing Not Started => Beta Successful
2018-02-22 16:20 WA9PIE Status resolved => assigned
2018-02-22 16:20 WA9PIE Note Added: 0004315
2018-02-23 20:04 k2ie File Added: Error.png
2018-02-23 20:04 k2ie Note Added: 0004321
2018-03-02 10:40 K7ZCZ Assigned To Roger => K7ZCZ
2018-05-18 09:26 K7ZCZ Relationship added related to 0002720
2018-05-18 09:26 K7ZCZ Relationship added related to 0002721
2018-05-24 13:06 K7ZCZ Note Added: 0005102
2018-05-24 13:06 K7ZCZ Status assigned => resolved
2018-05-24 13:06 K7ZCZ Resolution no change required => fixed
2018-05-24 13:06 K7ZCZ Note Added: 0005103
2018-05-26 23:29 K7ZCZ Project 1 - Backlog => 3 - Current Dev List
2018-05-26 23:30 K7ZCZ Fixed in Version =>
2018-05-29 14:55 g3ucq Note Added: 0005138
2018-05-30 00:59 vk2byi File Added: Test Case Results with
2018-05-30 00:59 vk2byi File Added: Test Case Results with
2018-05-30 00:59 vk2byi Note Added: 0005149
2018-05-30 08:34 k2ie Note Added: 0005153
2018-05-31 14:30 WA9PIE Status resolved => closed
2018-06-13 09:13 WA9PIE Fixed in Version =>
2018-06-13 09:13 WA9PIE Project 3 - Current Dev List => Ham Radio Deluxe