bug in the upload process to eQSL.cc

[JA9HWD]

On January 18, 2025, I noticed a bug in the upload process to eQSL.cc. This had happened twice before, but I finally realized that Log4OM2 was the problem.

There is one duplicate piece of data between the last one before switching accounts in Log4OM2 and the first one after switching. There are no duplicates in the Log4OM2 log, but both accounts upload one piece to each corresponding eQSL.cc account, and eQSL.cc displays "There is duplicate data in another account" for both accounts. In this case, I have to manually delete the data from the incorrect account in eQSL.cc.

I cannot check this in advance, so I have not established a workaround.

[JA9HWD]

On January 22, 2025, after today's POTA activation ended, the final data from the day before POTA activation was uploaded to eQSL.cc as the first data for today's POTA activation. Since I noticed this, it has been happening every time, so I think there is an error in the account switching judgment process when uploading in QSL Manager.

[JA9HWD]

Although there is only one log data in Log4OM2, it ends up existing in OutBox of two eQSL.cc accounts.

2025-01-22 eQSL_DupAc2.png (214.59 KiB) Viewed 25053 times

[JA9HWD]

This is the eQSL.cc OutBox for JA9HWD/P. It was uploaded via ADIF on 2025-01-22.
This should have been uploaded from the Log4OM2 QSL Manager, where the log showed a "Request" status.
This means that one item that was already in the "Yes" status was uploaded together with another item from a different Log4OM2 account.

2025-01-22 eQSL_DupAc_OutBox.png (39.8 KiB) Viewed 25051 times

[JA9HWD]

By the way, the dark gray message surrounded by red says in Japanese, "Duplicate data found."

[IW3HMH]

Good catch. I don't have a multiple station account on eqsl, may i ask you guys to:
Enable log level to trace
Reproduce the issue (sorry for making you eqsl log dirty)
Create a support request in help menu writing the call of the bad qso (log is very verbose in trace mode)

Then send the log to [email protected]

Thanks!

[JA9HWD]

Daniele,

I understand. I will set the log level to "trace" and collect logs.

However, unfortunately, due to the winter weather that will continue for a while, I do not plan to perform mobile operations, and it will take a few days to send the results, so please wait.

If anyone is experiencing the same problem, please cooperate, and if there are people who do not have any problems when switching accounts, please report that there are no problems.

[JA9HWD]

Good catch. I don't have a multiple station account on eqsl, may i ask you guys to:
Enable log level to trace
Reproduce the issue (sorry for making you eqsl log dirty)
Create a support request in help menu writing the call of the bad qso (log is very verbose in trace mode)

Then send the log to [email protected]

Thanks!

Today I performed POTA activation to test the antenna for rainy weather.
I am sending you the trace log from switching accounts to uploading to eQSL.cc. It took a long time to start the QSL manager after the upload was completed, but this is because dinner started at my house after the upload.
As expected, the last one before the account switching was uploaded after the account switching. The duplicate call sign is "JR4ARN/P", but it is a coincidence that it is the same call sign as last time.
The trace log shows a total of 31 items, but the number of items in the Log4OM2 log is only 30. Looking at this number, I imagine that I crossed accounts by mistake and made a mistake in identifying the number of items and the record position of the start of the upload.

For reference, I am also attaching the data imported with Log4OM2 at that time.
I will send the same content as the forum and email, but I will not send an attachment to the forum because the password is displayed in the trace log.

I hope this will help you solve the problem.

[JA9HWD]

I activated POTA again today.
However, today there was no duplication of data across accounts.

This has changed my prediction of the bug a little.
I think this is not just a bug in the account switching process, but a bug in the judgment and management of uploaded data to eQSL.cc, which was originally incorrect.

With my regular account, Log4OM2 automatically uploads data after a certain amount of time has passed since the QSO. This is done properly every time a QSO is added.
However, when I search for "Request" in QSL Manager at a different time or on a different day, it is listed as an upload target, but when I press the "Uplaod Selected QSO" button and execute it, there is a duplicate error from eQSL.cc. You will see a message appear. Since it is actually uploaded properly, I thought it was an error in the search process and did not worry about it.
I have not actually encountered any adverse effects. Even if I report this as a bug, I think I will be called a liar or ignored again, so I have not reported it.

However, if the eQSL.cc accounts are different, duplication errors are not detected when uploading. It is also unrealistic to cross-check in real time with different accounts. Therefore, I think that the data is cross-checked when it is complete, and a cross-account duplication error is displayed.

The bug this time is...
An error in the settings process resulted in "Request" not being changed to "Yes" for some reason for data that had already been uploaded.
Even though this data was from a different account, it was treated as a target for upload and was uploaded.
I think this is the result of two bugs occurring at different times being combined.

[G4POP]

I activated POTA again today.
However, today there was no duplication of data across accounts.

This has changed my prediction of the bug a little.
I think this is not just a bug in the account switching process, but a bug in the judgment and management of uploaded data to eQSL.cc, which was originally incorrect.

With my regular account, Log4OM2 automatically uploads data after a certain amount of time has passed since the QSO. This is done properly every time a QSO is added.
However, when I search for "Request" in QSL Manager at a different time or on a different day, it is listed as an upload target, but when I press the "Uplaod Selected QSO" button and execute it, there is a duplicate error from eQSL.cc. You will see a message appear. Since it is actually uploaded properly, I thought it was an error in the search process and did not worry about it.
I have not actually encountered any adverse effects. Even if I report this as a bug, I think I will be called a liar or ignored again, so I have not reported it.

However, if the eQSL.cc accounts are different, duplication errors are not detected when uploading. It is also unrealistic to cross-check in real time with different accounts. Therefore, I think that the data is cross-checked when it is complete, and a cross-account duplication error is displayed.

The bug this time is...
An error in the settings process resulted in "Request" not being changed to "Yes" for some reason for data that had already been uploaded.
Even though this data was from a different account, it was treated as a target for upload and was uploaded.
I think this is the result of two bugs occurring at different times being combined.

Have you actually done what Lele requested in his earlier post and sent him a 'Support request' having emulated the issue with Trace mode turned on?