Downloader on bor-mainnet is stuck waiting for metadata of v1-054600-054700-borspans.seg
Closed this issue · 8 comments
I'm trying to sync bor-mainnet from scratch with release/2.60 (commit 40d1327), but my node is stuck at
[INFO] [05-07|21:13:16.310] [snapshots] no metadata yet files=1 list=v1-054600-054700-borspans.seg
[INFO] [05-07|21:13:16.336] [1/15 Snapshots] download progress="99.90% 940.4GB/940.4GB" time-left=999hrs:99m total-time=4m0s download=0B/s upload=0B/s peers=2 files=695 metadata=694/695 connections=2 alloc=670.5MB sys=968.4MB
I suspect that it's caused by erigontech/erigon-snapshot#142, which changed the hash of this file for no apparent reason.
#10242 ledgerwatch/erigon-snapshot#159 #10243 ledgerwatch/erigon-snapshot#160
It's not helping unfortunatelly:
[INFO] [05-08|07:08:08.886] Build info git_branch=e2_bor_mainnet_borspan git_tag=v2.54.0-819-g665c9a180c git_commit=665c9a180c54744d6b1f490c0714aae8296d2201
...
[INFO] [05-08|07:11:11.090] [snapshots] no metadata yet files=1 list=v1-054600-054700-borspans.seg
Still have the same issue 054600-054700-borspans.seg, even on the latest release.
Still have the same issue 054600-054700-borspans.seg, even on the latest release.
With v2.60.0? Then please rm <datadir>/snapshots/v1-054600-054700-borspans.seg* and restart.
Yes, with v2.60.0. Removed v1-054600-054700-borspans.seg*, restarted Erigon and the issue still persists. As soon as I restart, v1-054600-054700-borspans.seg* files reappear and it stops syncing.
@bcxyz sorry, i don't believe you :-) show:
- git status
rmcommand which you dolsoutput after rm is done- logs of erigon after restart
Not sure why you wouldn't believe me.
The diagnostics error is due to heimdalld using port 6060. Also tried changing that, with no results.
Am I missing something or making a mistake somewhere?