paritytech
Block syncing is in progress, but not proceed.
Hello there.
I newly started running node using v0.9.26, aside from release of v0.9.27. However, my node stop getting new finalized block after #9282048. Is there any solution here, or have to rerun?
Runtime: v0.9.26 Chain: Polkadot Option:
--rpc-external
--chain=polkadot
--database=rocksdb
--pruning=150000
--rpc-port=9933
--sync=Full
--rpc-cors=all
--detailed-log-output
--log=info
Logs:
2022-07-28 09:13:12.832 INFO tokio-runtime-worker substrate: ⚙️ Syncing 28.7 bps, target=#11357184 (42 peers), best: #9281904 (0x519f…f7c1), finalized #9281536 (0x2e36…3ea7), ⬇ 576.6kiB/s ⬆ 1.9kiB/s
2022-07-28 09:13:18.680 INFO tokio-runtime-worker substrate: ⚙️ Syncing 24.6 bps, target=#11357185 (42 peers), best: #9282048 (0xda82…994d), finalized #9281536 (0x2e36…3ea7), ⬇ 571.0kiB/s ⬆ 0.7kiB/s
2022-07-28 09:13:24.536 INFO tokio-runtime-worker substrate: ⚙️ Syncing 28.5 bps, target=#11357186 (42 peers), best: #9282215 (0xc362…a1e3), finalized #9282048 (0xda82…994d), ⬇ 542.5kiB/s ⬆ 0.8kiB/s
2022-07-28 09:13:30.427 INFO tokio-runtime-worker substrate: ⚙️ Syncing 8.6 bps, target=#11357187 (42 peers), best: #9282266 (0xc0ee…a2b9), finalized #9282048 (0xda82…994d), ⬇ 379.1kiB/s ⬆ 0.8kiB/s
2022-07-28 09:13:36.273 INFO tokio-runtime-worker substrate: ⚙️ Syncing 0.0 bps, target=#11357188 (42 peers), best: #9282266 (0xc0ee…a2b9), finalized #9282048 (0xda82…994d), ⬇ 4.0kiB/s ⬆ 0.8kiB/s
2022-07-28 09:13:42.116 INFO tokio-runtime-worker substrate: ⚙️ Syncing 0.0 bps, target=#11357189 (41 peers), best: #9282266 (0xc0ee…a2b9), finalized #9282048 (0xda82…994d), ⬇ 4.3kiB/s ⬆ 1.1kiB/s
2022-07-28 09:13:47.963 INFO tokio-runtime-worker substrate: ⚙️ Syncing 0.0 bps, target=#11357190 (41 peers), best: #9282266 (0xc0ee…a2b9), finalized #9282048 (0xda82…994d), ⬇ 10.7kiB/s ⬆ 15.1kiB/s
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2022-07-28 09:18:11.764 INFO tokio-runtime-worker substrate: ⚙️ Syncing 0.0 bps, target=#11357233 (42 peers), best: #9282266 (0xc0ee…a2b9), finalized #9282048 (0xda82…994d), ⬇ 9.1kiB/s ⬆ 0.6kiB/s
2022-07-28 09:18:17.599 INFO tokio-runtime-worker substrate: ⚙️ Syncing 0.0 bps, target=#11357234 (42 peers), best: #9282266 (0xc0ee…a2b9), finalized #9282048 (0xda82…994d), ⬇ 5.3kiB/s ⬆ 2.9kiB/s
2022-07-28 09:18:23.473 INFO tokio-runtime-worker substrate: ⚙️ Syncing 0.0 bps, target=#11357235 (42 peers), best: #9282266 (0xc0ee…a2b9), finalized #9282048 (0xda82…994d), ⬇ 3.7kiB/s ⬆ 0.6kiB/s
2022-07-28 09:18:29.494 INFO tokio-runtime-worker substrate: ⚙️ Syncing 0.0 bps, target=#11357236 (42 peers), best: #9282266 (0xc0ee…a2b9), finalized #9282048 (0xda82…994d), ⬇ 3.2kiB/s ⬆ 0.3kiB/s
2022-07-28 09:18:35.359 INFO tokio-runtime-worker substrate: ⚙️ Syncing 0.0 bps, target=#11357237 (42 peers), best: #9282266 (0xc0ee…a2b9), finalized #9282048 (0xda82…994d), ⬇ 164.1kiB/s ⬆ 77.7kiB/s
2022-07-28 09:18:41.265 INFO tokio-runtime-worker substrate: ⚙️ Syncing 0.0 bps, target=#11357238 (42 peers), best: #9282266 (0xc0ee…a2b9), finalized #9282048 (0xda82…994d), ⬇ 28.8kiB/s ⬆ 5.8kiB/s
2022-07-28 09:18:47.138 INFO tokio-runtime-worker substrate: ⚙️ Syncing 0.0 bps, target=#11357239 (42 peers), best: #9282266 (0xc0ee…a2b9), finalized #9282048 (0xda82…994d), ⬇ 150.5kiB/s ⬆ 45.3kiB/s
2022-07-28 09:18:49.787 WARN async-std/runtime trust_dns_proto::xfer::dns_exchange: failed to associate send_message response to the sender
2022-07-28 09:18:49.787 WARN async-std/runtime trust_dns_proto::xfer::dns_exchange: failed to associate send_message response to the sender
2022-07-28 09:18:49.787 WARN async-std/runtime trust_dns_proto::xfer::dns_exchange: failed to associate send_message response to the sender
2022-07-28 09:18:50.231 WARN async-std/runtime trust_dns_proto::xfer::dns_exchange: failed to associate send_message response to the sender
2022-07-28 09:18:53.000 INFO tokio-runtime-worker substrate: ⚙️ Syncing 0.0 bps, target=#11357240 (43 peers), best: #9282266 (0xc0ee…a2b9), finalized #9282048 (0xda82…994d), ⬇ 95.2kiB/s ⬆ 26.7kiB/s
Can you please try the latest release? We have fixed some syncing issues, maybe also your problem.
How long is it staying at 0.0 bps?
@bkchr Thanks for your reply.
How long is it staying at 0.0 bps?
Almost a week. I noticed this problem yesterday.
Anyway I will try the latest.
I remember also seeing this happen once when I was testing out some stuff, but I was experimenting with some of the parameters so I assumed it was my fault and not that something's potentially broken. If I'll see it again I'll try to investigate in more detail.
