-
Notifications
You must be signed in to change notification settings - Fork 20k
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
Need help to solve the synchronization problem. #25598
Comments
is it possible the |
The chaindata was corrupted in 1.10.22. Honestly the simplest solution is to do |
I experienced this issue with
|
I couldn't execute
so tried another way like this: #25589 (comment) Node restarted synchronizing. |
You cannot do |
What do you mean? That log is from a node which most definitely has chaindata intact, not removed at all |
I also removedb , and was getting a similar message...
|
I'm not sure what happened, but doesn't the |
No, not at all. State pruning is something entirely different. To remove the chain data, but leave ancients intact, use |
oops, you're right of course. Sorry for the confusion |
Finally, completed sync!! Close. |
Hello there.
I need help. It seems to be my node's problem; geth client is not wrong.
I newly started runnig node, using following client.
I faced problem: the synchronization is going wrong due to BAD BLOCK.
Is there any solution here?
Logs:
The text was updated successfully, but these errors were encountered: