[Action Required] Consensus node operators please update to v0.45.1-consensus-recovery and run these commands and restart

Node Operations
1

hello Flow Consensus node operators,

Flow mainnet has run into an issue and transaction sealing has stopped. The earlier resolution did not work and we had to make an update to the consensus node software to resume.

Please run the following commands again but additionally also update the Consensus node to docker tag v0.45.1-consensus-recovery.

We have tested this tag on the foundation nodes and they recovered OK.

We have identified the issue and resolved it on the Flow Foundation nodes.

Please run the following commands on each of your Flow Consensus nodes and restart the node:

  1. Download the util and untar (skip this if you had downloaded this earlier. There is no change to the utility)

gsutil cp gs://flow-genesis-bootstrap/tools/v0.46.2-util-remove-execution-fork/util.tar .

tar -xvf util.tar
  1. Move the util to the flow directory

cp util /var/flow/util-remove-execution-fork

  1. Stop the node

systemctl stop flow-consensus (if you are using systemctl) or just stop the docker container directly.

  1. Run the command

/var/flow/util-remove-execution-fork remove-execution-fork

  1. Please remove these flags (entirely) if you have it set:
  • emergency-sealing-active=true
  • required-construction-seal-approvals=0 (or any other value)

If you don’t have those flags, then no action is required for this step.

  1. Update the node docker tag to v0.45.1-consensus-recovery

  2. Start the node

systemctl start flow-consensus (if you use systemctl) or just start the docker container directly.

This should recover the node and it should start catching up.

Please reach out to us on Discord if you have any questions or need help.

Please treat this also as an urgent request.

Thank you,
Flow Foundation

PS: Again, no action required from any other node operators.