Feature/submissions

[dndj355]

Submissions for OT4-B1, OT4-B4, OT4-T1, OT4-T2, OT4-T3, OT4-T4.

PLEASE NOTE: On 2021-02-05 during the period of unexpected high load on the consortium network I responded to a request to submit FULL logs. These were subsequently uploaded to https://drive.google.com/file/d/12tvWk2xiLK_HsjcBx6rx1uzGu0dGY6MU/view?usp=sharing

I noticed that extracting the logs cleared the logs thus I was unable to prove the period of approx, 14 days running the node.

This was discussed with @supermario via Discord who reassured me that this would be considered in the submission.

Please also note that while the node was offline I took the opportunity to take the latest upgrade to Docker Desktop and hit the following issue #70 . After downgrading I was unable to resume with the original node due to errors when trying to catch up. After approximately 1 week of clearing databases and retrying I eventually cleared down all my local files and started a new node. I was in discussion with @pablozsc via discord during this time.

I've kept a full journal of the issue shown below and have minified logs of all the catch up attempts if they would be of use.

The consequence of this is that on 2021-02-13 my node id changed from e4c12f039286d02a to c559edf3b400e047.

This may impact OT4-B4 for which I have specified the original node id in submission.txt. While there is nothing that states we needed to use the same node to complete the challenge I wanted to bring this to your attention.

Journal of events following high load on concordium - 2021-02-05

2021-02-05

• Transactions started failing due to high load on network.
• Concordium requested that affected people upload logs. Email with full logs sent through for investigation.
• Unlike reports from others, no disk space issues were encountered
• Installed latest Docker Update (Windows) - Mistake in hindsight!
• Installed latest version of node 0.4.11. Assumed that since I wasn't experiencing disk space issues I didn't need to capture minified logs.
• After 10 hours realized that people were reporting that they had lost logs due to node installation.
• Took minified logs, realized uptime was low.
• Contacted @supermario , he said to hold tight and keep original full logs from earlier in the day.
• Node still stuck on "Attempting bootstrap", assume this is related to high load on network.

2021-02-07

• Node still stuck on "Attempting bootstrap"
• Searched Discord and found Node on Windows fails to bootstrap with Docker Desktop 3.1.0 #70
• Took minified logs again (not sure whether this counts against OT4-B1)
• Reset node data
• Installed Docker v2.5.0.1
• Restarted node.

2021-02-09

• node caught up about 70% then got stuck with Couldn't process a finalization message from peer 5684f0407bf4c0fa due to error code InvalidResult errors. This carried on for the best part of 2 days.
• Took minified logs again
• Reset data and tried again.

2021-02-10

• Following conversation with @pablozsc (Modarator) on Discord, he suggested I try again.
• Minified logs captured.

2021-02-11

• Same issue with InvalidResult error.
• @pablozsc (Moderator) forwarded instructions on how to move node to another server (linux to linux).
• After several failed attempts I was unable to migrate from windows to linux successfully.

2021-02-12

• Same issue with InvalidResult error.
• Updated to version 3.0.4 of Docker Desktop and tried again.

2021-02-13

• Same issue.
• Final attempt was to start from scratch with completely new node.
• Cleared both local and roaming concordium folders

2021-02-14

• Finally, node was able to catch up fully!!
• Unfortunately, with a new node id c559edf3b400e047 :(.
• Restarted Baker and Transaction challenges.

[dndj355]

Form Submitted
12-05-2022 @21:40 BST