Where is bps obtained from, and the node has not been syncing for a long time

Support
,
1 
2023-10-10 14:19:11 [Consensus] ⚙️  Syncing  0.0 bps, target=#803413 (37 peers), best: #788489 (0x0656…1c2a), finalized #664495 (0x95f5…c7a0), ⬇ 59.8kiB/s ⬆ 1.2kiB/s    
2023-10-10 14:19:16 [Consensus] ⚙️  Syncing  0.0 bps, target=#803413 (36 peers), best: #788489 (0x0656…1c2a), finalized #664495 (0x95f5…c7a0), ⬇ 33.7kiB/s ⬆ 0.3kiB/s    
2023-10-10 14:19:21 [Consensus] ⚙️  Syncing  0.0 bps, target=#803414 (34 peers), best: #788489 (0x0656…1c2a), finalized #664495 (0x95f5…c7a0), ⬇ 34.0kiB/s ⬆ 0.4kiB/s    
2023-10-10 14:19:26 [Consensus] ⚙️  Syncing  0.0 bps, target=#803414 (35 peers), best: #788489 (0x0656…1c2a), finalized #664495 (0x95f5…c7a0), ⬇ 46.2kiB/s ⬆ 0.7kiB/s    
2023-10-10 14:19:31 [Consensus] ⚙️  Syncing  0.0 bps, target=#803415 (35 peers), best: #788489 (0x0656…1c2a), finalized #664495 (0x95f5…c7a0), ⬇ 40.2kiB/s ⬆ 0.4kiB/s    
2023-10-10 14:19:36 [Consensus] ⚙️  Syncing  0.0 bps, target=#803416 (36 peers), best: #788489 (0x0656…1c2a), finalized #664495 (0x95f5…c7a0), ⬇ 35.2kiB/s ⬆ 0.5kiB/s    
2023-10-10 14:19:41 [Consensus] ⚙️  Syncing  0.0 bps, target=#803417 (37 peers), best: #788489 (0x0656…1c2a), finalized #664495 (0x95f5…c7a0), ⬇ 16.0kiB/s ⬆ 0.7kiB/s    
2023-10-10 14:19:46 [Consensus] ⚙️  Syncing  0.0 bps, target=#803417 (37 peers), best: #788489 (0x0656…1c2a), finalized #664495 (0x95f5…c7a0), ⬇ 29.4kiB/s ⬆ 0.7kiB/s    
2023-10-10 14:19:51 [Consensus] ⚙️  Syncing  0.0 bps, target=#803417 (37 peers), best: #788489 (0x0656…1c2a), finalized #664495 (0x95f5…c7a0), ⬇ 33.6kiB/s ⬆ 0.7kiB/s    
2023-10-10 14:19:56 [Consensus] ⚙️  Syncing  0.0 bps, target=#803417 (36 peers), best: #788489 (0x0656…1c2a), finalized #664495 (0x95f5…c7a0), ⬇ 33.9kiB/s ⬆ 0.3kiB/s    
2023-10-10 14:20:01 [Consensus] ⚙️  Syncing  0.0 bps, target=#803418 (36 peers), best: #788489 (0x0656…1c2a), finalized #664495 (0x95f5…c7a0), ⬇ 38.4kiB/s ⬆ 0.7kiB/s    
2023-10-10 14:20:06 [Consensus] ⚙️  Syncing  0.0 bps, target=#803418 (39 peers), best: #788489 (0x0656…1c2a), finalized #664495 (0x95f5…c7a0), ⬇ 33.1kiB/s ⬆ 0.8kiB/s

If bps is obtained from other nodes, then why would there be a situation where there is no bps for a long time? If bps is obtained from an official main node, then what is the address of this node?

2

bps stands for blocks per second and just shows the rate at which your node is importing blocks during sync process. 0 means it doesn’t import anything, yet it thinks it should be syncing.

There are two sync mechanisms in Subspace:

  1. Sync from DSN for old archival history
  2. Substrate sync for recent history

The first one doesn’t have extensive communication in logs right now, so it is most likely what node is doing right now. For sync from DSN node will reach out to the rest of the network, determine how much history was archived so far, download pieces of archival history that are potentially useful and import blocks contained in there.

The second usually happens fairly quickly and should show some non-zero progress shortly.

It is currently expected to see 0 bps for a few minutes on node restart as it collects information about archived history from other nodes on the network and collects pieces that potentially contain useful blocks. We will try to improve logging around this in the future.

3

I had the same problem, it got stuck at ‘best: #794769 (0x3ecd…c575)’ and wouldn’t move any further. Is your problem solved?

1 Like