-
Notifications
You must be signed in to change notification settings - Fork 677
New issue
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
[investigate]: Prevoting nil err, wrong Block.Header.AppHash. #3061
Comments
Thank you for opening the issue! Could you let us know if you used a snapshot to sync after the upgrade or you upgraded your existing nodes? This would help us with triage. Please let us know if this happens again. If you have further issues try running Besides that, what usually works is re-syncing from a snapshot. |
Hi
Both current node were running from a snapshot |
Thanks for the clarification. Apphash errors show more frequently on some of the snapshot providers. Let's leave this issue opened in case it happens again. We'll keep an eye on the reports here and in other places. |
Hi @MSalopek
So you're guess is that the issue come from the snapshot I'm using? Can you explain more? Thks |
I think the easiest would be to statesync instead of using a node snapshot using v15.2.0 binary. Try using this as a starting point: https://polkachu.com/state_sync/cosmos. From where are you getting your node snapshots? Besides that, try purging your addressbook and download a new one and check that your persistent peers are upgraded correctly (if you use persistent peers). Are you running a validator node or an RPC node? Are you accepting Txs or is it just used for reading state? Could you share your |
There is already the two config files you've asked for. I'll have a look for state_sync in the mean time.
A RPC node that allow tx |
Hello @MSalopek
They come from the following source: https://quicksync.io/cosmos.json |
Have you had any luck with other node snapshot providers or statesync? Has the issue been resolved? |
Network upgraded to v16.0.0 and there was no recent activity on this issue. I'm closing it for now. Feel free to reopen if the issue happens for v16.x. |
Is there an existing issue for this?
What happened?
I'm running two nodes (v15.2.0), they both suddently stopped to work yesterday when they reached the block 20012316
I reinitialized one of them and is now working fine but I'm just concerned by the fact that it might happen again.....
Thks for your help
Gaia Version
v15.2.0
How to reproduce?
No response
The text was updated successfully, but these errors were encountered: