QRZ Logbook Restored to Service

Just tried to upload new log entries. Looks like it completed but checking, found no new entries.

Tnx & 73,
Joe
W1FIT

 

QRZ has completed the import processing of your logbook file.

File name: BradHRD.ADI (23 records)

Destination Book: "NK8J Logbook" (35621)

Started on: Mon Feb 4 04:24:21 2019
Finished on: Mon Feb 4 04:24:22 2019



Please Help

Import Results:

0 QSO's were inserted
0 duplicates were replaced
0 duplicates ignored
23 errors.


System Messages:

Error 1. Insert error on record: WB2TQE de NK8J on 2019-02-03 12:32:00.
Error 2. Insert error on record: WB2HJQ de NK8J on 2019-02-03 12:30:00.
Error 3. Insert error on record: KG2MD de NK8J on 2019-02-03 12:26:00.
Error 4. Insert error on record: KB5HC de NK8J on 2019-02-03 12:23:00.
Error 5. Insert error on record: VE2SCA de NK8J on 2019-02-03 12:17:00.
Error 6. Insert error on record: K0KC de NK8J on 2019-02-03 12:12:00.
Error 7. Insert error on record: W2JK de NK8J on 2019-02-03 12:04:00.
Error 8. Insert error on record: N6PDB de NK8J on 2019-02-03 11:46:00.
Error 9. Insert error on record: AA1SU de NK8J on 2019-02-03 11:36:00.
Error 10. Insert error on record: N3YEA de NK8J on 2019-02-03 11:33:00.
Error 11. Insert error on record: K5C de NK8J on 2019-02-03 11:31:00.
Error 12. Insert error on record: HK4EI de NK8J on 2019-02-03 11:21:00.
Error 13. Insert error on record: KC1IFK de NK8J on 2019-02-03 08:25:00.
Error 14. Insert error on record: KJ6NA de NK8J on 2019-02-03 08:21:00.
Error 15. Insert error on record: AE4IN de NK8J on 2019-02-03 08:17:00.
Error 16. Insert error on record: WY6S de NK8J on 2019-02-03 08:10:00.
Error 17. Insert error on record: F1RUK de NK8J on 2019-02-02 15:49:00.
Error 18. Insert error on record: IK2WRV de NK8J on 2019-02-02 15:34:00.
Error 19. Insert error on record: VK2AR de NK8J on 2019-02-02 07:31:00.
Error 20. Insert error on record: EA7UW de NK8J on 2019-02-02 07:16:00.
Error 21. Insert error on record: EA7AH de NK8J on 2019-02-02 07:00:00.
Error 22. Insert error on record: EA7JW de NK8J on 2019-02-02 06:54:00.
Error 23. Insert error on record: KG5UAV de NK8J on 2019-02-02 06:23:00.

 

It is what it is. Great job. Thanks for all the hard work yall put into it. Glad it restored again. I kind of felt crippled not being able to use it.

 

Thanks, Fred. As you correctly surmised, there are still some further serious issues that are continuing to keep me offline

1. MINOR: Some edits made just prior to shutdown lost:
The edits I made to my 3 newest log entries present before shutdown were lost. Prior to shutdown, they had been edited to my logbook perfection then uploaded to LoTW. So they were complete and colored LoTW Green. After system restoration, those same 3 records appeared in their virgin, unedited, plain white (non-LoTW UL) state. So, I edited them again and re-uploaded them to LoTW. The edits were save and all looked OK. But, wait, there's more, see Item #2.

2. URGENT Record Edit Not Working:
As of 2019-02-04 at 0424 UTC, the logbook is not saving *any* edits to my log. Without my extensive editing, my logbook is effectively inoperative.
Here's the operational flow of the problem case:
a. Uploaded 50 new log entries I had created offline in AC Log while QRZ was down. Let's call them #1-#50.
b. Proceeded to edit these 50 new imports. Every time I edited and saved them, the record displayed as if no changes were made at all.
To research this further, I edit #50, #49, #1, #2. and #25. All with the same result. Records totally unchanged. Edit ignored.
It is as if my DB records are in a locked state.

I will continue to test to see if the RDBMS is out of breath and needs more time to wake up. Like me in the AM, ha!

As of 2019-02-04 at 0524 UTC, there is no change. Edits of any kind are NOT allowed.

3. System Slow then Unavailable again.
Around 2019-02-04 at 0528 UTC, shortly after conducting the last test above the system became unavailable again with "Connect Timed Out" error.
For about 5 minutes prior to that downage, the system was running very slow. Then it timeout and became unavailable.

KT1TK

 

Not working my side! get "ERR_CONNECTION_TIMED_OUT"
Regards ZS2PA

 

As of 0530 UTC 02/04/2019 it took 3 attempts to send new Q's to LOTW; on the 3rd try it said they were sent successfully, however, those Q's didn't turn green (green highlighted) in my logbook per normal procedure.

 

Pressing "log a new contact" times out
Now no logbook

 

Unable to access log book, server stopped responding.....numerous tries..

 

Same here

 

Logbook not operate

 

I got connected once just long enough to enter a few contacts from the past couple days but can't get connected now. I just get a time out. Perhaps the system is over loaded by hams connecting to upload information?

 

Congrats - and thanks for the update, everything is significantly faster !
Except - I can't access my logbook data, once I click on "My Logbook",
it keeps on "...connecting" and just stays there.
Could you please take a look at it ?
tnx, 73, Bernie dk3xt/ab7iy

 

Get a error message when I try to view my log.

W1OF

 

Thanks everything works great again..
It must have been a nerve-racking process.

73 Niels PD9Q