ErrorLog file regarding: [DXLab] Error Logging from JTAlert to DXKeeper


Dave AA6YQ
 

Thanks for the errorlog, Russ. It shows that DXKeeper received a directive from JTAlert log a QSO with KG5HTH and submit it to eQSL and LoTW.

2021-03-12 01:15:44.900 > TCPServerModule.DataArrival, ByteCount = 744
2021-03-12 01:15:44.902 > Request = <command:11>eqsllotwlog<parameters:705><CALL:6>KG5HTH<QSO_DATE:8>20210312<TIME_ON:6>011415<TIME_OFF:6>011515<FREQ:9>10.138186<FREQ_RX:9>10.138186<MODE:3>FT8<RST_SENT:3>+13<RST_RCVD:3>+02<GRIDSQUARE:6>EM02wi<LAT:11>N032 21.250<LON:11>W098 07.500<DISTANCE:4>1216<TX_PWR:2>12<COMMENT:49>Test QSO for Dave to debug DXK double log problem<NAME:18>PHILIP R FLINN, II<QTH:11>Morgan Mill<STATE:2>TX<CNTY:8>TX,Erath<ADDRESS:68>Philip R Flinn, II
PO BOX 96
Morgan Mill
TX, 76465
UnitedStates<ANT_AZ:2>85<DXCC:3>291<CQZ:1>4<ITUZ:1>7<CONT:2>NA<APP_DXKeeper_LOTW_MEMBER:1>Y<APP_DXKeeper_EQSL_MEMBER:1>A<SFI:2>78<A_INDEX:1>4<K_INDEX:1>3<APP_DXKEEPER_USER_DEFINED_1:1>Y<MY_GRIDSQUARE:6>DM41LX<OPERATOR:4>KR6W<STATION_CALLSIGN:4>KR6W<QSO_COMPLETE:1>Y<EOR>

The QSO was successfully logged

2021-03-12 01:15:46.104 > ADIF.ImportRecord complete

and then successfully submitted to TQSL for uploading to LoTW:

2021-03-12 01:15:47.840 > TQSL Version 2.5.7 [v2.5.7]
2021-03-12 01:15:47.841 > Signing using Callsign KR6W, DXCC Entity UNITED STATES OF AMERICA
2021-03-12 01:15:47.841 >
2021-03-12 01:15:47.842 > Attempting to upload one QSO
2021-03-12 01:15:47.843 > C:\DXLab\DXKeeper\LotWUpload.ADI: Log uploaded successfully with result:
2021-03-12 01:15:47.843 >
2021-03-12 01:15:47.844 > File queued for processing
2021-03-12 01:15:47.844 > After reading this message, you may close this program.
2021-03-12 01:15:47.845 > Final Status: Success(0)
.

5 seconds later, DXKeeper received a second directive from JTAlert to log the same QSO with KG5HTH, and submit it to eQSL and LoTW:

2021-03-12 01:15:53.395 > TCPServerModule.DataArrival, ByteCount = 744
2021-03-12 01:15:53.395 > Request = <command:11>eqsllotwlog<parameters:705><CALL:6>KG5HTH<QSO_DATE:8>20210312<TIME_ON:6>011415<TIME_OFF:6>011515<FREQ:9>10.138186<FREQ_RX:9>10.138186<MODE:3>FT8<RST_SENT:3>+13<RST_RCVD:3>+02<GRIDSQUARE:6>EM02wi<LAT:11>N032 21.250<LON:11>W098 07.500<DISTANCE:4>1216<TX_PWR:2>12<COMMENT:49>Test QSO for Dave to debug DXK double log problem<NAME:18>PHILIP R FLINN, II<QTH:11>Morgan Mill<STATE:2>TX<CNTY:8>TX,Erath<ADDRESS:68>Philip R Flinn, II
PO BOX 96
Morgan Mill
TX, 76465
United States<ANT_AZ:2>85<DXCC:3>291<CQZ:1>4<ITUZ:1>7<CONT:2>NA<APP_DXKeeper_LOTW_MEMBER:1>Y<APP_DXKeeper_EQSL_MEMBER:1>A<SFI:2>78<A_INDEX:1>4<K_INDEX:1>3<APP_DXKEEPER_USER_DEFINED_1:1>Y<MY_GRIDSQUARE:6>DM41LX<OPERATOR:4>KR6W<STATION_CALLSIGN:4>KR6W<QSO_COMPLETE:1>Y<EOR>

The attempt to submit this QSO to LoTW failed, since it had already been uploaded:

2021-03-12 01:15:55.098 > TQSL Version 2.5.7 [v2.5.7]
2021-03-12 01:15:55.098 > Signing using Callsign KR6W, DXCC Entity UNITED STATES OF AMERICA
2021-03-12 01:15:55.099 > Already Uploaded QSO suppressed on line 5
2021-03-12 01:15:55.099 > CALL: KG5HTH
2021-03-12 01:15:55.100 > TIME_ON: 011415
2021-03-12 01:15:55.100 > QSO_DATE: 20210312
2021-03-12 01:15:55.101 > MODE: FT8
2021-03-12 01:15:55.101 > BAND: 30M
2021-03-12 01:15:55.102 > FREQ: 10.138186
2021-03-12 01:15:55.102 > BAND_RX: 30M
2021-03-12 01:15:55.103 > FREQ_RX: 10.138186
2021-03-12 01:15:55.104 > PROP_MODE: F2
2021-03-12 01:15:55.105 > Signing aborted
2021-03-12 01:15:55.106 > All QSOs are already uploaded; aborted
2021-03-12 01:15:55.106 > No records to upload
2021-03-12 01:15:55.107 > Final Status: No QSOs written(8)

I do not know why JTAlert is sending two "Log QSO" directives to DXKeeper.

73,

Dave, AA6YQ


HamApps Support (VK3AMA)
 

On 12/03/2021 12:45 pm, Dave AA6YQ wrote:
I do not know why JTAlert is sending two "Log QSO" directives to DXKeeper. 
It doesn't. It only ever sends one instruction, no repeats ever.

A zombie JTAlert process running perhaps?

I suggest the OP restarts his PC and see if that corrects the behavior.
FWIW, there have been no other reports of duplicate logging to DXKeeper in the 3 months since JTAlert 2.16.17 was released.

de Laurie VK3AMA




Russ Ravella
 

Ok Dave,

Thanks very much.  I contacted you since I was hearing about the problem from DXK but this is obviously a JTA issue. I’ll contact Laurie and see what he thinks.  Thanks again for diagnosing this !

Have a great evening!
Russ


On Mar 11, 2021, at 7:04 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 12/03/2021 12:45 pm, Dave AA6YQ wrote:
I do not know why JTAlert is sending two "Log QSO" directives to DXKeeper. 
It doesn't. It only ever sends one instruction, no repeats ever.

A zombie JTAlert process running perhaps?

I suggest the OP restarts his PC and see if that corrects the behavior.
FWIW, there have been no other reports of duplicate logging to DXKeeper in the 3 months since JTAlert 2.16.17 was released.

de Laurie VK3AMA




Dave AA6YQ
 

+ AA6YQ comments below

It doesn't. It only ever sends one instruction, no repeats ever.

A zombie JTAlert process running perhaps?

I suggest the OP restarts his PC and see if that corrects the behavior.
FWIW, there have been no other reports of duplicate logging to DXKeeper in the 3 months since JTAlert 2.16.17 was released.

+ Nor have I, Laurie.

+ Another possibility: the same message conveyed by TCP being delivered more than once. I've never encountered that either, but...

        73,

             Dave, AA6YQ