The synchronization node keeps showing this log "[downloader] Added future link" about bsc-erigon HOT 10 CLOSED

INFO[08-23|19:08:14.587] logging to file system                   log dir=data/logs file prefix=erigon log level=info json=false
INFO[08-23|19:08:19.828] [snapshots] Blocks Stat                  blocks=29500k indices=29500k alloc=2.3GB sys=2.5GB
Note: prune_at doesn't mean 'all data before were deleted' - it just mean stage.Prune function were run to this block. Because 1 stage may prune multiple data types to different prune distance.

 				 stage_at 	 prune_at
Snapshots 			 31100989 	 0
Headers 			 31101643 	 0
BlockHashes 			 31101643 	 0
Bodies 				 31101643 	 0
Senders 			 31101643 	 0
Execution 			 31101643 	 31101643
Translation 			 0 		 0
HashState 			 31101643 	 0
IntermediateHashes 		 31101643 	 31101643
AccountHistoryIndex 		 31101643 	 0
StorageHistoryIndex 		 31101643 	 0
LogIndex 			 31101643 	 0
CallTraces 			 31101643 	 31101643
TxLookup 			 31101643 	 30359000
Finish 				 31101643 	 0
--
prune distance: 

blocks.v2: blocks=29499999, segments=29499999, indices=29499999

history.v3: false, idx steps: 0.00, lastMaxTxNum=0->0, lastBlockInSnap=0

sequence: EthTx=4709356989, NonCanonicalTx=0

in db: first header 29500000, last header 31101643, first body 29500000, last body 31101643

Restarting a node can sometimes solve this problem, but after running for a period of time, the problem reappears.

from bsc-erigon.

Is this issue related to bandwidth? My bandwidth is 100Mbps downstream, 100Mbps upstream, and the hard drive is 12TB SSD

from bsc-erigon.

It's been 3 days now, and it's still stuck here

from bsc-erigon.

integration stage_headers --reset

from bsc-erigon.

Is this issue related to bandwidth? My bandwidth is 100Mbps downstream, 100Mbps upstream, and the hard drive is 12TB SSD

It's seem something wrong with node

from bsc-erigon.

集成 stage_headers --reset

I have tried, but the problem still exists.
I also deleted 'data/snapshots/' and couldn't solve the problem.

from bsc-erigon.

Do I need to delete all data and resynchronize to solve this problem?

from bsc-erigon.

If unwind can't fix, may you need download a new snapshots and resync

from bsc-erigon.

The error was fixed at the cost of not being able to request the trace module of rpc between blocks 29500000-31100000. During the snapshot generation process, I executed "integration stageheaders -- reset" and recovered to 29500000. However, after starting erigon, the block was 31100000, so the data in between cannot be requested. However, for me, it is already sufficient, and I guess this is a problem with "48Club" data

from bsc-erigon.

The error was fixed at the cost of not being able to request the trace module of rpc between blocks 29500000-31100000. During the snapshot generation process, I executed "integration stageheaders -- reset" and recovered to 29500000. However, after starting erigon, the block was 31100000, so the data in between cannot be requested. However, for me, it is already sufficient, and I guess this is a problem with "48Club" data

Most of the faulty blocks are after the snapshot we released. This is a problem that occurs during synchronization, not in the snapshot. see #199 (comment)

from bsc-erigon.