Open WietzeSlagman opened 7 months ago
Thanks for the report and the logs, I'll look into this when I get the chance!
I also encourage everyone participating in CanaryNet to also look at the codepaths where this was emitted, usually that helps make it apparent why this happened. Let's all attempt to look into this and see if we can discover why this happened!
π Bug Report
Validator (aleo1z838c4zukt8qpwndz3gnjd374skg6zucd8q6pz30r3v2gcuh4q8qvdf8p9) on Canary net stopped participating in consensus after round 37666, and stopped producing blocks (never elected as leader) and thus also potentially stopped accruing rewards. The node itself was not down and kept being insync with tip, receiving new blocks and propagating them to it's clients. EDIT: Rewards seem to be unimpacted
Following this change in behaviour the logs produced by the validator skyrocketed, produced the same amount of log data in 2 days as it did in the previous 10. This could be related to it having to receive all memorypool requests over and over again without being able to process any of it into blocks.
Steps to Reproduce
logs around the time of occurence:
the message this log ends with can be seen repeating for a few hours but eventually also stopping:
Log file with a larger timeframe: validator-consenus-anomaly.log
The validator was restarted when the anomaly was detected, this did fix the issue and the validator proceeded to take part in block production again
Expected Behavior
Expected the node to continue participating in block production and not require a restart to do so.
Your Environment