Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Synchronisation failed #610

Closed
0xZonh opened this issue Jan 29, 2024 · 30 comments
Closed

Synchronisation failed #610

0xZonh opened this issue Jan 29, 2024 · 30 comments

Comments

@0xZonh
Copy link

0xZonh commented Jan 29, 2024 •
edited
Loading

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.
image

Please let me know if there is a solution for this. Thank you!
@meowsbits meowsbits mentioned this issue Jan 29, 2024
Closed
@meowsbits
Copy link
Contributor

meowsbits commented Jan 29, 2024 •
edited
Loading

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.

@ziogaschr
Copy link
Member

@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.

@lixiubao4967
Copy link

lixiubao4967 commented Jan 30, 2024 •
edited
Loading

I also have the above problem, how to solve it? How long does it take to find a peer?
WARN [01-30|17:58:55.238] Synchronisation failed, dropping peer peer=9ab3b037eb1c892569115fb9e97fdc6aa2b8bc5c9a712b1f449cacf53a763dee err=timeout
WARN [01-30|17:59:25.904] Synchronisation failed, retrying err="peer is unknown or unhealthy"
WARN [01-30|17:59:49.244] Synchronisation failed, retrying err="peer is unknown or unhealthy"
WARN [01-30|18:00:00.589] Synchronisation failed, retrying err="peer is unknown or unhealthy"
WARN [01-30|18:00:27.415] Synchronisation failed, retrying err="peer is unknown or unhealthy"
WARN [01-30|18:01:16.414] Synchronisation failed, retrying err="peer is unknown or unhealthy"

@ziogaschr
Copy link
Member

Can you please try using these 3 peers (current bootnodes) by hand?

enode://6b6ea53a498f0895c10269a3a74b777286bd467de6425c3b512740fcc7fbc8cd281dca4ab041dd97d62b38f3d0b5b05e71f48d28a3a2f4b5de40fe1f6bf05531@157.245.77.211:30303

enode://16264d48df59c3492972d96bf8a39dd38bab165809a3a4bb161859a337de38b2959cc98efea94355c7a7177cd020867c683aed934dbd6bc937d9e6b61d94d8d9@64.225.0.245:30303

enode://55bbc7f0ffa2af2ceca997ec195a98768144a163d389ae87b808dff8a861618405c2582451bbb6022e429e4bcd6b0e895e86160db6e93cdadbcfd80faacf6f06@164.90.144.106:30303

@lixiubao4967
Copy link

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,[email protected] bodies=18,412,[email protected] receipts=18,412,[email protected] eta=25m36.866s
INFO [01-30|22:11:04.063] Syncing: state healing in progress accounts=[email protected] slots=[email protected] codes=[email protected] nodes=[email protected] pending=2181
INFO [01-30|22:11:04.135] Loaded most recent local header number=18,426,842 hash=f5e125..ef7d48 td=6,621,534,149,745,222,344,099 age=4mo1d18h
INFO [01-30|22:11:04.135] Loaded most recent local block number=0 hash=d4e567..cb8fa3 td=17,179,869,184 age=54y10mo1w
INFO [01-30|22:11:04.135] Loaded most recent local snap block number=18,412,049 hash=502db0..618035 td=6,593,180,674,639,825,555,472 age=4mo4d1h
INFO [01-30|22:11:04.135] Loaded last snap-sync pivot marker number=19,214,245
WARN [01-30|22:11:04.135] Rolled back chain segment header=18428891->18426842 snap=18412049->18412049 block=0->0 reason="syncing canceled (requested)"
WARN [01-30|22:11:04.135] Synchronisation failed, retrying err="no peers to keep download active"
INFO [01-30|22:11:11.703] Regenerated local transaction journal transactions=0 accounts=0
INFO [01-30|22:11:12.743] Looking for peers peercount=1 tried=42 static=0
INFO [01-30|22:11:23.076] Looking for peers peercount=2 tried=38 static=0
INFO [01-30|22:11:33.265] Looking for peers peercount=2 tried=35 static=0
INFO [01-30|22:11:43.408] Looking for peers peercount=2 tried=36 static=0

@lixiubao4967
Copy link

@ziogaschr
How do I specify these three peers?
enode://6b6ea53a498f0895c10269a3a74b777286bd467de6425c3b512740fcc7fbc8cd281dca4ab041dd97d62b38f3d0b5b05e71f48d28a3a2f4b5de40fe1f6bf05531@157.245.77.211:30303

enode://16264d48df59c3492972d96bf8a39dd38bab165809a3a4bb161859a337de38b2959cc98efea94355c7a7177cd020867c683aed934dbd6bc937d9e6b61d94d8d9@64.225.0.245:30303

enode://55bbc7f0ffa2af2ceca997ec195a98768144a163d389ae87b808dff8a861618405c2582451bbb6022e429e4bcd6b0e895e86160db6e93cdadbcfd80faacf6f06@164.90.144.106:30303

@ziogaschr
Copy link
Member

If you started core-geth with console command, like geth --classic console then you can type there admin.addPeer('enode://6b6ea53a498f0895c10269a3a74b777286bd467de6425c3b512740fcc7fbc8cd281dca4ab041dd97d62b38f3d0b5b05e71f48d28a3a2f4b5de40fe1f6bf05531@157.245.77.211:30303').
If you use JSON RPC APIs and you have admin API open (which is not advised), then you can use https://etclabscore.github.io/core-geth/JSON-RPC-API/modules/admin/#admin_addpeer

@jakubartur
Copy link

jakubartur commented Jan 31, 2024 •
edited
Loading

me the same no sync , look number=19,218,133 hash=d66d06..7f6820 td=8,164,776,887,095,361,374,446 age=7h58m44s
7h+ no sync fix

admin.addPeer('enode://55bbc7f0ffa2af2ceca997ec195a98768144a163d389ae87b808dff8a861618405c2582451bbb6022e429e4bcd6b0e895e86160db6e93cdadbcfd80faacf6f06@164.90.144.106:30303')
true
admin.addPeer('enode://16264d48df59c3492972d96bf8a39dd38bab165809a3a4bb161859a337de38b2959cc98efea94355c7a7177cd020867c683aed934dbd6bc937d9e6b61d94d8d9@64.225.0.245:30303')
true
admin.addPeer('enode://16264d48df59c3492972d96bf8a39dd38bab165809a3a4bb161859a337de38b2959cc98efea94355c7a7177cd020867c683aed934dbd6bc937d9e6b61d94d8d9@64.225.0.245:30303')
true
Looking for peers peercount=0 tried=57 static=2
bootnodes limit 50 peers no open slots conect ??

I suggest you do something similar to what I did, please check the link https://enode.redecoin.eu/

@jakubartur
Copy link

jakubartur commented Jan 31, 2024 •
edited
Loading

INFO [01-31|12:42:46.138] Block synchronisation started
INFO [01-31|12:42:54.157] Looking for peers peercount=1 tried=55 static=3
INFO [01-31|12:43:04.280] Looking for peers peercount=0 tried=51 static=3
INFO [01-31|12:43:14.466] Looking for peers peercount=0 tried=37 static=3
INFO [01-31|12:43:24.607] Looking for peers peercount=0 tried=51 static=3
INFO [01-31|12:43:34.686] Looking for peers peercount=1 tried=60 static=3
INFO [01-31|12:43:44.799] Looking for peers peercount=1 tried=47 static=3
WARN [01-31|12:43:46.138] Synchronisation failed, dropping peer peer=5d1706ab63f92532c709f6c611b6c0f0e508d5f328be9615c689896280bdb328 err=timeout

bootnode problem conect

@ziogaschr
Copy link
Member

ziogaschr commented Feb 5, 2024 •
edited
Loading

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.

@MiningCryptoLive
Copy link

I am trying to sync using the latest version and on classic network and it is taking forever. Used to be able to sync within a couple hours. I am now going on 24 hours and only at 46% downloaded with 66 peers connected.@ziogaschr

@ziogaschr
Copy link
Member

I am trying to sync using the latest version and on classic network and it is taking forever. Used to be able to sync within a couple hours. I am now going on 24 hours and only at 46% downloaded with 66 peers connected.@ziogaschr

Thanks @MiningCryptoLive. Starting a fresh node now to test it.

@ziogaschr
Copy link
Member

I was able to sync latest release on classic in 3 hours. Check the green line @MiningCryptoLive.

Can you share which CLI flags you use to run it and also what OS? I was running it on Ubuntu.

image

@MiningCryptoLive
Copy link

MiningCryptoLive commented Aug 20, 2024 •
edited
Loading

I was able to sync latest release on classic in 3 hours. Check the green line @MiningCryptoLive.

Can you share which CLI flags you use to run it and also what OS? I was running it on Ubuntu.

image

Here is my command line: geth --classic --datadir /home/pool/.ethereum/classic --syncmode=snap --http --http.api eth,net,web3 --mine --miner.etherbase="0x********" --maxpeers 100 --password="/home/pool/.pw" --allow-insecure-unlock --http.port="8545" --unlock="0x******" --port="30305" I am running this on Ubuntu 22.04 @ziogaschr

@MiningCryptoLive
Copy link

I also downloaded geth again. Deleted the.ethereum directory & started syncing again. 4 1/2 hours later and only.15 percent download with 66 peers. Something is definitely wrong

@ziogaschr
Copy link
Member

Can you try and start syncing without the --mine flag. Restart and enable --mine once synced.

Does your machine have enough resources?

@MiningCryptoLive
Copy link

MiningCryptoLive commented Aug 21, 2024 via email

@ziogaschr
Copy link
Member

Perfect. Let me know if you can mine once synced.
I will check if we can handle that flow better.

p.s.: You probably have your machine behind a firewall and with all ports closed already. If not needed I will advice to remove the --http flag.

@MiningCryptoLive
Copy link

I will remove that and let you know once synced and flags added back if mining works

@MiningCryptoLive
Copy link

@ziogaschr Get the following after sync completed and enabled mining. All daemons online. All daemons synced with blockchain. Loading current light cache. No pre-generated cache available. Unable to mine.

@ziogaschr
Copy link
Member

Can you share logs? Do you mine with CPU or GPU? Are you connecting to a pool (which one?)?

@MiningCryptoLive
Copy link

Can you share logs? Do you mine with CPU or GPU? Are you connecting to a pool (which one?)?

I am using gpu's. Mining to a pool. I am assuming that the changes made has affected the mining pool software. That is what is showing that the light cache does not exist. And then it shuts down. I will try a different mining pool software and see if it works. I'll let you know. Thanks for all your help!

@MiningCryptoLive
Copy link

Can you share logs? Do you mine with CPU or GPU? Are you connecting to a pool (which one?)?

I tried different pool software and mining works fine.

@ziogaschr
Copy link
Member

Thanks a lot for sharing.

Can you please let me know which pool is not working and which one works? (please share link to repos if you can)

@MiningCryptoLive
Copy link

Thanks a lot for sharing.

Can you please let me know which pool is not working and which one works? (please share link to repos if you can)

this is the one I am using now and it works fine.

https://github.com/yuriy0803/open-etc-pool-friends

Miningcore is now not working. I am assuming the code needs to be modified. It starts then shuts down at Loading current light cache ... No pre-generated cache available.

https://github.com/blackmennewstyle/miningcore

@ziogaschr
Copy link
Member

Thanks @MiningCryptoLive.
I will close this issue now.

@MiningCryptoLive
Copy link

Also wanted to let you know that I left geth syncing on another machine with all the flags in place. It is almost done syncing after 2 days but it also takes double the storage space. Syncing without the flags takes 48gb and with the flags 151gb so far

@MiningCryptoLive
Copy link

MiningCryptoLive commented Aug 22, 2024 via email

@ziogaschr
Copy link
Member

I was expecting that, and also at some point, probably on a restart, geth will prune the data (still cover all the difference in size).

@MiningCryptoLive
Copy link

MiningCryptoLive commented Aug 22, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@ziogaschr @MiningCryptoLive @meowsbits @lixiubao4967 @jakubartur @0xZonh