Open halfalicious opened 5 years ago
This ultimately looks like a peering issue - if Aleth had at least 2 peers which are on the canonical longest Ropsten chain, it would go through a chain reorg and sync on the correct chain.
Hitting this again when syncing Aleth (built from source, head = c47760657321d216c74bc9d5849a2857da29d7e1) from genesis on Ropsten.
(Originally found when investigating #5312 )
I hit a case when syncing Aleth where it ends up on a Ropsten fork and stops syncing because it's unable to sync with Ropsten boot nodes. Log: ropsten_fork_sync_stop.txt
Log snippet:
Aleth keeps asking node 865a6325 for blocks starting with 470069 but it doesn't have any, which is strange given that it's a Ropsten boot node: https://github.com/ethereum/aleth/blob/e80e19770e2ab60d2ba8fbace27a7f8b1d006f02/libp2p/Common.cpp#L261-L265
Aleth will occasionally connect to the node which has the fork (6332792c…) and sync some blocks: