Closed jimjbrettj closed 3 weeks ago
I believe this has been fixed by #4291.
Logs from our baremetal Paseo node, which has the above fix deployed:
2024-10-31 10:21:09.473 | 2024-10-31T03:21:09Z INFO highest block: 1787760 target 23241238 pkg=sync
2024-10-31 10:21:09.473 | 2024-10-31T03:21:09Z INFO ⛓️ synced 382 blocks, tasks on queue 0, disjoint fragments 0, incomplete blocks 0, took: 5.49 seconds, bps: 69.52 blocks/second, target block number #23241238 pkg=sync
2024-10-31 10:20:57.977 | 2024-10-31T03:20:57Z INFO highest block: 1787378 target 23241237 pkg=sync
2024-10-31 10:20:57.977 | 2024-10-31T03:20:57Z INFO ⛓️ synced 382 blocks, tasks on queue 0, disjoint fragments 0, incomplete blocks 0, took: 3.54 seconds, bps: 108.05 blocks/second, target block number #23241237 pkg=sync
2024-10-31 10:20:48.441 | 2024-10-31T03:20:48Z INFO highest block: 1786996 target 23241235 pkg=sync
2024-10-31 10:20:48.441 | 2024-10-31T03:20:48Z INFO ⛓️ synced 382 blocks, tasks on queue 0, disjoint fragments 0, incomplete blocks 0, took: 4.00 seconds, bps: 95.52 blocks/second, target block number #23241235 pkg=sync
Issue summary
For some reason when we start Paseo the target block is not being set and syncing stalls because there is no target. This needs to be debugged and this issue can be resolved when the network is progressing again