4

After fixing stalled finality which was due to 5 of 13 valdidators broken, finality is now 502 blocks behind, but it is not catching up to production.

We get this error:

2022-09-29 20:13:03 Safeguard enforced finalization of child forced_target=0xd0df478b4bf96df1871fa22890f73c526c4d79b840496c9543bb2b080009e5ca

enter image description here

You can view the chain here: https://apps.decentration.org/?rpc=wss%3A%2F%2Fpopart1.jelliedowl.com#/explorer

It seems like block production may have also gone into a “slow mode” because finality is so far behind?

We are running Rococo release-v0.9.26-1

How can we remedy this?

Improve this question

1 Answer 1

Reset to default
2
+50

You can send:

Initializer::ForceApprove(Root, HighestBlock)

Send this as transaction to the chain and it should start finalizing.

Improve this answer
8
  • ForceApprove is different than forcing a GRANDPA set change, which is perhaps what's needed?
    – rob
    Commented Oct 5, 2022 at 5:10
  • i tried to forcApprove up to 5 blockcs behind the best block, but i didnt see any change. Then i try Grandpa noteStalled, but still finalized blocks are 500 behind, with 1 minute blocks. Perhaps i need to wait for session change?
    – Ramsey - Decentration
    Commented Oct 5, 2022 at 9:57
  • Now it looks like it is completely down?
    – bkchr ♦
    Commented Oct 5, 2022 at 14:54
  • yes it’s down, sigh, I think that would have bricked it, because of babe, now must restart I assume.
    – Ramsey - Decentration
    Commented Oct 5, 2022 at 20:55
  • 2
    Next time I propose that you read the docs of the extrinsic before sending it.Using delay of 0 is wrong.
    – bkchr ♦
    Commented Oct 7, 2022 at 6:34

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.