-
Notifications
You must be signed in to change notification settings - Fork 836
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Finalized block got stuck #2074
Comments
More information: Code: https://github.com/stafiprotocol/stafi-node/tree/v0.6.2 Subscan: https://stafi.subscan.io/ Apps: https://apps.stafi.io/ |
https://substrate.stackexchange.com/a/380/452 Check this answer, in particular using the RPC API to figure out the GRANDPA round state (e.g. who is not voting). |
Yeah, we tried the solution too(https://stafi.subscan.io/extrinsic/0xe4431deafd133d9cdfcd952a610b58cad0a53ce026d33c83e7c90b91a6efbb2a). Just like I said, even tried multiple times using higher height, but all didn't work. About the GRANDPA round state,
The result is: There are indeed many missing prevotes(When we first requested this RPC yesterday, the setId was 4819, currentWeight of prevotes was 100. And now the returned setId is 4821, currentWeight of prevotes is 101. When will it be changed? The currentSetId of Grandpa is 4829 now). |
Here are some debug logs from our validator node(
|
Hey @Tore19 for more visibility, please also raise the same issue on Stackexchange so that the support engineers can also take a look at it! This also helps keep the information stored for future reuse when a solution is found. |
Got it! Will do it. |
If the current set id returned from the RPC API has changed it means that the |
Can we please stop this? Stackexchange is not for posting this kind of issues. Stackexchange is not for bugs that require interaction between people to find a solution, aka debugging etc. |
Got it! Thanks for your explanation! Working on replacing faulty validators. |
If the current best finalized block number is 16448401 then that's the number what you should provide. Check against multiple validators to see if they all have the same number. |
Sure. Let me check again. |
@andresilva @joshuacheong Hi, replaced some faulty validators and tried grandpa.noteStalled function. Then it was fixed. Everything work fine now. We will also continue to monitor the validator status. Thanks for your guys help! |
Code: https://github.com/stafiprotocol/stafi-node/tree/v0.6.2
StaFi chain has been running stably for a long time using version v2.0.0 of substrate, and the current version is v0.6.2. But the finalized block suddenly got stuck. Like this:
Can check details here:
https://telemetry.polkadot.io/#list/0x290a4149f09ea0e402c74c1c7e96ae4239588577fe78932f94f5404c68243d80.
We didn't find any error or useful logs for this. And we also tried to use the
grandpa.noteStalled
function to try to restore, actually we even tried multiple times, but all didn't work.So any ideas about this? And any possible solution?
The text was updated successfully, but these errors were encountered: