We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Looks like for some reason an active node, if stopped cannot resume.
Run the docker image and let it sync, once sync stop it. And start it again and check logs.
At least testnet
Medium
############################## WARN [09-25|18:01:04.291] Synchronisation failed, dropping peer peer=dc8080419ade6ac1 err="retrieved hash chain is invalid" ERROR[09-25|18:01:05.550] insert chain error while bc.engine.VerifyHeaders of a block err="pruned ancestor" ERROR[09-25|18:01:05.551] ########## BAD BLOCK ######### Chain config: {ChainID: 2 Engine: konsensus} Number: 925707 Hash: 0x3b55454dcd4b42d1b70babbaedb80e987c34fb147e1c803dd7499ffafab90ead [EMPTY RECEIPTS]```
The text was updated successfully, but these errors were encountered:
This is caused by inconsistent state after reorg panic. As far as #788 is merged, could you recheck full sync on currect dev branch?
@jgimeno @adamking
Sorry, something went wrong.
No branches or pull requests
Type:
Looks like for some reason an active node, if stopped cannot resume.
If it's an issue, how can we reproduce it?:
Run the docker image and let it sync, once sync stop it. And start it again and check logs.
Affected servers or services:
At least testnet
Priority:
Medium
Other info we may need:
The text was updated successfully, but these errors were encountered: