-
Notifications
You must be signed in to change notification settings - Fork 606
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
sync: failed to fetch block hash for height ####: block not found #978
Comments
This comment has been minimized.
This comment has been minimized.
By checking the birthday I got past the birthday block, but it got stuck again at a later block, so may be something else.
There's a suspicious error before this second spat starts. did not get response before timeout:
|
I think recovery needs a rollback like here Line 481 in 311812f
|
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
This seems to be a random sync error. Its been around forever but I don't see an issue for it. The particular block seems to differ, but sync will get stuck with this error and never fix itself, even restarting:
The block exists but is reported as block 858,853 here, so I guess its not finding the parent block hash? https://www.blockchain.com/explorer/blocks/btc/000000000000000000007101d8cb8f46c7c17c7c12f873eb0f717d8751628c08
The text was updated successfully, but these errors were encountered: