<snip>When LoTW was designed more than a decade ago -- long before the present IT staff was here -- an assumption was made as to how many logs could possibly be in the queue at a given time. The assumption was based on users uploading their most recent QSOs perhaps once a week or once a month. The environment in which LoTW now operates is quite different from that assumption, in that many users now upload logs with small numbers of QSOs in them, almost in real time. This creates a much larger number of separate logsWhen a log is uploaded, it is identified by a file name that is assigned by the user. Because there is no way to avoid duplication of file names that are assigned in this fashion, the LoTW system renames each file. Because of the unusual processing delay -- combined with the dramatic increase in the number of submitted logs -- the system began to run out of unique identifiers for the log files. This resulted in a file sometimes being renamed with an identifier that had already been assigned to a log that was still in the queue, causing the earlier log to be overwritten.

Once the problem was identified, designing a fix was relatively easy. It should be in place by 2359 UTC November 28. Because the number of overwritten logs is relatively small, we have decided to keep the system available for use, even though this may result in a few more logs being lost until the fix is in place. <snip>

kudos to K1ZZ for offering some transparency regarding the issue. I am surprised the system wasn't proactively updated by someone who knew the ins and outs of how the system worked every year or so to keep pace with usage and technology... am i missing something

It's a big relief to hear they have figured out the "lost log" problem.

I'm a big fan of LotW and I keep track of what logs I have uploaded and reload them if necessary. But there's another class of user (mostly rare DX!) that only uploads logs to do the rest of us a favor. That type of user is not checking every day to see if his log was processed, so if it's lost, there's a chance it won't get uploaded again.

Just for the hell of it I think I'll upload my 20,000 contacts in one big file. I must have uploads that got lost along the way and he did say it was the small uploads which were the pain in the ass, right?

Just for the hell of it I think I'll upload my 20,000 contacts in one big file. I must have uploads that got lost along the way and he did say it was the small uploads which were the pain in the ass, right?

73,

Chris/NU1O

I just e-mailed each of my 20,000 contacts requesting that they re-upload data from the dates I worked them. Just for insurance, you see?

Well, still nothing. No PT0S upload processed, no CQWWCW upload processed. I guess I was also one of the very few who had their uploads overwritten even after the 25th. Instead of a Power Ball winner, it looks like I'm a LoTW wiener!

Hi,Whats odd is I did much the same as you... I uploaded a large portion of my log after the affected dates, and have not seen a return on them yet... I also have not seen a single confirmation in about a week... This is not normal... I normally get one or two a week easily... I am tempted to upload my entire log, (20K contacts), and see if that flushes things out... Not getting any confirmations for a week or longer is not normal...73'sDave

Well, still nothing. No PT0S upload processed, no CQWWCW upload processed. I guess I was also one of the very few who had their uploads overwritten even after the 25th. Instead of a Power Ball winner, it looks like I'm a LoTW wiener!

I am not seeing anything new in the last week either ... The LoTW page has an update today saying they are 4 days behind now (not 3)...

I wouldn't be surprised if a lot of us uploaded our PT0S contact since we knew they were uploading to LoTW and that created a large number of small files -- the kind evidently that are especially prone to being lost by the system

Copyright 2000-2018 eHam.net, LLC
eHam.net is a community web site for amateur (ham) radio operators around the world.
Contact the site with comments or questions.
WEBMASTER@EHAM.NETSite Privacy Statement