-
Notifications
You must be signed in to change notification settings - Fork 20.5k
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
canonical block #12291468 unknown #22763
Comments
Can you please provide more log (especially of the start) - and ideally in text-form - not as a screenshot? |
Could you please try (from a geth console --
|
|
The following is my startup log, which I have had before,But my block seems to be synchronized to the latest and can be used normally
|
Please try |
get result is null |
So, the missing block is If so, the location where the index thinks the header should reside is occupied by something else -- or even does not exist.
Also, your node reports a lot of unclean shutdowns. I don't know how you usually run the node, but you should ensure that you give it sufficient time to shut down, and not just blindly kill the process. |
Sorry, I use the ethereum/client-go node running by docker, I have no way to stop the geth program, and then execute: geth db freezer-index headers 12291466 12291470 |
I have never found information on how to stop geth running in the manual. I always stop the process by sending a kill signal to geth. Do you know a more elegant way to stop it? |
Yes, you can send it the
|
I also have this error message spamming my logs:
Edit: Updated to the latest version today - did not help |
Hey, I have the same error in my logs but it seems it is syncing fine to the latest block |
Ah It seems now I am not able to even run the node properly. As mentioned above, I was getting the error earlier but it was syncing fine. Now, I tried to upgrade geth node and restarted it and getting below error. I am running geth with --syncmode=full |
Most likely, yes. If the OS crashes, the db is very likely to become corrupt. |
UUIC, the original problem was due to unclean shutdowns. I don't think this issue is actionable from our perspective, so closing this. |
@holiman Is there a way to fix this without deleting geth data and doing a full sync? |
System information
Geth version: Geth/v1.10.2-stable-97d11b01/linux-amd64/go1.16.3
OS & Version: Centos docker
Commit hash : (if
develop
)Expected behaviour
ERROR[04-29|04:07:16.857] Section processing failed type=bloombits error="canonical block #12291468 unknown"
The text was updated successfully, but these errors were encountered: