You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While the node is stuck in this state, it replies on RPC commands normally, eg. returns the same response on getblockchaininfo with the same blocks and headers number. Therefore, it is impossible to detect that the node is corrupted, solely via the RPC interface
I have several nodes, and one of them stopped syncing without any reason.
Node version: 0.21.3
This is very important for business continuity, please advise how can handle it
I see the following error:
ERROR: ConnectTip: ConnectBlock d6ab36f7b181669dc2b459f9d15a24906c648c116b5503015e397c4d11d98156 failed, mweb-connect-failed, MWEB::Node::ConnectBlock(): Failed to connect MWEB block: ApplyBlock: Consensus Error: MMR_MISMATCH
The text was updated successfully, but these errors were encountered: