-
Notifications
You must be signed in to change notification settings - Fork 744
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
TrieDB iteration error: Database missing expected key #663
Comments
We are encountering the exact same error log lines on at least one of our Polkadot ParityDB archive nodes:
|
This is maybe related to not using the latest paritydb release. |
Which should be fixed by 0.9.42 |
@bkchr : I had the same problem on a warp syncing 0.9.41 polkadot node. Restarting does not fix it. startup:
|
@stakeworld would it be possible for you to test latest master? |
@bkchr Sure, is there a binary downloadable somewere or should I compile? |
You would need to compile it yourself with |
It should be downloadable from the Gitlab CI artifacts for a few days: https://gitlab.parity.io/parity/mirrors/polkadot/-/jobs/2679262/artifacts/raw/artifacts/polkadot |
@bkchr a master build fixes the problem and the sync resumes normally |
Ty for reporting back! And with 0.9.41 it was constantly failing? |
Yes, on 0.9.41 it kept crashing also after a restart, with the master build no more errors, restarted normally and continued the sync |
Okay perfect! |
* Remove renounce ownership * script to poll local ethereum for contract events * added comments
Two our our public archive rpc nodes crashed at the same time with the same error.
Version:
polkadot 0.9.41-e203bfb396e
Restarting didn't solve the problem. But downgrading to
polkadot 0.9.39-1-298b4aefe1b
solved the problem for nowParameters:
Logs:
The text was updated successfully, but these errors were encountered: