-
Notifications
You must be signed in to change notification settings - Fork 235
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
New node sync crashed with 'key 012f002f626c6f636b2d72656c6...not found' (v0.11.11) #1936
Comments
Hello!
As I said the daemon has run for many days before dying with this error, so it should not be in syncing phase. Here are version informations:
|
I had faced same issue today with v0.12.6. Any solution? |
Same here is there any solution (2.12.1 version) |
Does resetting the DB fixes the problem? |
I just installed it from source on (Ubuntu 22.04.1 LTS), launched it from scratch, and after synchronizing the blockchain I received a message: ./kaspad --utxoindex
|
happens on windows too. |
How to fix it? |
Happened to me today on Windows, Any idea how to fix it?? |
Hi,
I upgraded my kaspad from 0.11.9 to 0.11.11 (by precompiled kaspad binary for linux) and after few tens of minutes I end up with error below. I have Debian Linux Bullseye.
This error happends immediately after
./kaspad --utxoindex
.Btw, i deleted (moved) previous datadir2 content, because just after upgrade kaspad binary and start it again, after 2-3 hours there was only lot of "Connecting to... lot of IPs", so kaspad was not unable to sync. After that i deleted datadir2 content and restarted kaspad. Kaspad started to sync from 2022-01-25 which was OK, but after tens of minutes it crashed with error below.
The text was updated successfully, but these errors were encountered: