Merge pull request #1086 from supermario/logs-submission-tool

New log submissions process and tooling

Author: supermario

logs.md

@@ -0,0 +1,52 @@
+## Logs
+
+Currently for the OT3 release fairly verbose logging is enabled by default for the node software. Approx 2GB of logs per day is generated by a continually running node.
+
+
+
+### Log submission
+
+For B1/B2/B6 challenges, proof of runtime via logs is required.
+
+We've created a small tool `retrieve_minified_logs` to sample your full set of log files and output a summary that is acceptable for submission.
+
+- [Download retrieve_minified_logs for Linux](https://client-distribution-testnet.concordium.com/retrieve_minified_logs-linux-v1)
+- [Download retrieve_minified_logs for OS X](https://client-distribution-testnet.concordium.com/retrieve_minified_logs-macos-v1)
+- [Download retrieve_minified_logs for Windows](https://client-distribution-testnet.concordium.com/retrieve_minified_logs-windows-v1.exe)
+
+
+Simply run the relevant binary on your system where the Concordium Node has been running. The tool will output two files in the folder it is run.
+
+**⚠️ These files must be submitted without modifications. Tampering with the summary log will be detected and result in disqualification from all challenges.**
+
+
+
+### Log sizes & rotation
+
+After running the node for a significant time you may find that you are running out of disk space on your node.
+
+You can find your log file location by running:
+
+```
+docker inspect --format='{{.LogPath}}' <container_name_or_id>
+```
+
+Where the `<container_name_or_id>` is found by running `docker ps -a`.
+
+
+**⚠️ Make sure you generate log summaries for submission _before_ clearing any logs!**
+
+
+You can then clear out your current logs via the command line:
+
+```
+# On OSX / Linux
+truncate -s 0 <log_path>
+
+# On Windows
+echo.> <log_path>
+```
+
+Repeat this process if the log size gets too large again.
+
+Make sure to submit all your log summaries if you're doing any of the B1/B2/B6 challenges.

status.md

@@ -21,11 +21,12 @@ The purpose of this document is to provide real-time information when it comes t
   * ⚠️ On Sunday, October 25th, between 5am and 11am BST, there might be disruption in the identity issuing service, due to scheduled maintenance on the side of our identity issuer.
 
 
-### ⚠️ Challenges & supporting tooling
+### ✅ Challenges & supporting tooling
+
+* No known major issues
+
+See [Issues](https://github.com/Concordium/Testnet3-Challenges/issues) for existing reports & statuses before posting an issue.
 
-* Investigating: Known issue for large log size submission for challenges requiring it.
-  * No need to post logs for now, just keep the logs until we advise the changed submission process.
-  * This will also cover the out-of-memory issues with `concordium-node-retrieve-logs`
 
 ### FAQs and Troubleshooting