-
Notifications
You must be signed in to change notification settings - Fork 141
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
Synchronisation failed #610
Comments
Hey there @0xZonh, thanks for the report. You're not alone on this, but we have no precise diagnostic or workarounds for now. See the referenced issue above for further context on (what seems to be) your issue. And please, if you can include more of your context, it will be helpful to us to better understand the issue; your CLI configuration, any relevant firewall configuration on the host, how long you've been dealing with the problem, etc. |
@0xZonh can we also know your location (if allowed to be shared) please, in order we check on a node in the same location as you. It might need more time to find good nodes close to you, and we might be able to find the cause and resolve it easier. |
I also have the above problem, how to solve it? How long does it take to find a peer? |
Can you please try using these 3 peers (current bootnodes) by hand?
|
It should be that the speed of finding peers is relatively slow. Now it is observed that synchronization has started. Thank you for your reply. INFO [01-30|22:11:04.058] Syncing: chain download in progress synced=95.82% chain=20.47GiB headers=18,428,891@5.33GiB bodies=18,412,049@12.20GiB receipts=18,412,049@2.94GiB eta=25m36.866s |
@ziogaschr enode://16264d48df59c3492972d96bf8a39dd38bab165809a3a4bb161859a337de38b2959cc98efea94355c7a7177cd020867c683aed934dbd6bc937d9e6b61d94d8d9@64.225.0.245:30303 enode://55bbc7f0ffa2af2ceca997ec195a98768144a163d389ae87b808dff8a861618405c2582451bbb6022e429e4bcd6b0e895e86160db6e93cdadbcfd80faacf6f06@164.90.144.106:30303 |
If you started core-geth with console command, like |
me the same no sync , look number=19,218,133 hash=d66d06..7f6820 td=8,164,776,887,095,361,374,446 age=7h58m44s
I suggest you do something similar to what I did, please check the link https://enode.redecoin.eu/ |
INFO [01-31|12:42:46.138] Block synchronisation started bootnode problem conect |
Once this new release https://github.com/etclabscore/core-geth/releases/tag/v1.12.19 is being used on more nodes in the network, we will probably not have more peering issues. Please update yourselfs. |
I upgraded the geth version from v1.12.13 to v1.12.18 today, and then it seems that the blocks cannot be synchronized normally. I'm a newbie and can't figure out where the problem is.
Please let me know if there is a solution for this. Thank you!
The text was updated successfully, but these errors were encountered: