[ADXA] Copied from LOTW reflector
Roger
n5qs at ncaars.org
Thu Mar 26 14:14:40 EDT 2020
The statement below was copied from the LOTW reflector.
If you had an upload during that period you need to change it in some
way and reupload it.
I check all my uploads and found it before this came out.
73
Roger, N5QS
Monday evening just before the Connecticut Governor's shutdown went into
effect at 8PM, ARRL IT rushed to relocate and reconfigure some computer
room hardware. The goal was to improve the odds that Logbook would be
able to gracefully tolerate and/or recover from power interruptions
without human intervention during their prolonged absence.
In their rush, something must have been missed that resulted in
triggering an error and failing for SOME uploads. This applies to SOME
(but not all) uploads from 23Z Monday the 23rd to 09Z Tuesday the 24th .
The only way for a user to know if their upload was affected is to check
their Activity report on the LoTW web site. SOME logging programs will
check for which QSOs have not been uploaded and then upload them again
so the issue is self-correcting for such users
One caveat for old school users is that the identical-duplicate log
detection in Logbook is real simple. The routine is unaware of whether
the same file had previously triggered an exception and should be
allowed a second chance at the processor. So subsequent uploads of the
exact same file -- even after the problem was corrected -- bring no joy:
identical retries are summarily rejected as duplicates. Some minimal
change must be made to the log for it to escape detection by the
automaton guarding the gates.
The suggestion is to just swap two of the log records. This is easy to
do when feeding an ADIF file to TQSL .It is not so easy if there is a
logging program trying to upload the exact same QSO sequence. For those
cases one might have to alter the time of one QSO by a second. Or just
make another QSO and add it to the upload.
More information about the ADXA
mailing list