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
Since the 0.4.0 version update, there have been about 10 reported issues, including mine. When nodes are stopped and restarted, some nodes get stuck and fail to restart. The problematic nodes repeatedly fetch only a specific part of a block's TX and do not receive the next block information, causing the block height to not increase.
The above issue seems to have been experienced by some users. This issue occurred when updating to 0.3.1 and 0.4.0 governance.
Steps to reproduce:
Upgrade manually from v0.3.1 to v0.4.0, in my case it happened to 2 public RPC nodes, while the validator node (not serving as public RPC) was not stuck
The text was updated successfully, but these errors were encountered:
If it’s stuck on “executed block,” it may be because the background process is currently pruning. Try setting pruning to “nothing,” then restart to see if it still gets stuck there.
Validator node
Since the 0.4.0 version update, there have been about 10 reported issues, including mine. When nodes are stopped and restarted, some nodes get stuck and fail to restart. The problematic nodes repeatedly fetch only a specific part of a block's TX and do not receive the next block information, causing the block height to not increase.
The above issue seems to have been experienced by some users. This issue occurred when updating to 0.3.1 and 0.4.0 governance.
Steps to reproduce:
Upgrade manually from v0.3.1 to v0.4.0, in my case it happened to 2 public RPC nodes, while the validator node (not serving as public RPC) was not stuck
The text was updated successfully, but these errors were encountered: