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
{{ message }}
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.
Parity Ethereum version: 2.2.1-beta (Previously also 2.0.9-stable)
Operating system: Linux
Installation: one-line installer (2.0.9-stable was built from source)
Fully synchronized: no
Network: ethereum
Restarted: yes
I'm trying to sync my node to the head of the Ethereum mainnet chain. At the time this error first appeared, I was running Parity-Ethereum 2.0.9-stable built from source. I recently upgraded to 2.2.1-beta using the one-line installer for Linux. I am running parity with default settings.
After receiving the error message, I've attempted the following settings to get around the error:
parity --warp-barrier=6703000 to warp past the error-prone block, unsuccessful
parity --reserved-peers ~/parity/bootnode --reserved-only using a few different bootnodes provided by Parity
I do not want to mess with my DB so close to the head of the chain. Is there a way I can solve this issue without killing my DB?
Repost from another discussion just in case anyone suffers from the same error. Our Error are a little bit confusing from first glance. We have:
TrieError::InvalidStateRoot, in which case it indicates that the given block's state root simply cannot be found! So it's a plain DB corruption and currently there's no way to recover it. (In the future we may be able to utilize fast sync or other stuff to try to fix this.)
BlockError::InvalidStateRoot, in which case it indicates a consensus failure.
For this case, it's unfortunately the former. There's nothing we can do about it at this moment other than reset the database.
I'm trying to sync my node to the head of the Ethereum mainnet chain. At the time this error first appeared, I was running Parity-Ethereum 2.0.9-stable built from source. I recently upgraded to 2.2.1-beta using the one-line installer for Linux. I am running parity with default settings.
After receiving the error message, I've attempted the following settings to get around the error:
parity --warp-barrier=6703000
to warp past the error-prone block, unsuccessfulparity --reserved-peers ~/parity/bootnode --reserved-only
using a few different bootnodes provided by ParityI do not want to mess with my DB so close to the head of the chain. Is there a way I can solve this issue without killing my DB?
Error Message:
The text was updated successfully, but these errors were encountered: