This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
stop nodeos on ship error #10113
Labels
Comments
This was referenced May 3, 2021
A 2.0.13 WAX node encountered this error, and stopped as expected. But it can't restart, as state history is missing the block. Failure where it stopped:
Failure after restart:
I'll restart it from a snapshot and I'm sure it will work. Just a note that the node leaves an inconsistent state after the failure. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If state history plugin has problems writing the history, nodeos must stop immediately.
related issue: #9483
Another condition is if the node starts from a snapshot that is newer than the state history's last block. The node moves along and does not write any history.
Currently it just prints a warning and goes along.
In case of an error, the operator needs to restart nodeos from a snapshot, and sometimes this condition is difficult to detect. Normally if someone installs a node with state history enabled, it's the primary job of the node to deliver history.
The text was updated successfully, but these errors were encountered: