5

I am facing an issue with syncing new nodes to the bootnodes of my parachain on Kusama. The bootnodes were synced using the following commands:

  • For fast sync: binary --chain <parachainchain> -- --sync=fast
  • For warp sync: binary --chain <parachainchain> -- --sync=warp

However, when I try to sync a new node with these bootnodes, I encounter the following log entries:

2023-11-29 09:13:37 [Parachain] Report 12D3KooWCEZ635J1LtCSX95vSjk6WzAm6oHdzKdEhiKzLNtiUvpT: -536870912 to -2147483648. Reason: Not requested block data. Banned, disconnecting. 2023-11-29 09:13:37 [Parachain] Report 12D3KooWAkbe8ecKSGUyRjgZwh8DifGiu5oe6s1VbVdBcVmc7mkS: -536870912 to -2147483648. Reason: Not requested block data. Banned, disconnecting. 2023-11-29 09:13:38 [Parachain] Report 12D3KooWQjuPJkXHj25W4QMuemGtcLFHBAiFMMd9snbhqSTB2vn5: -536870912 to -2147483648. Reason: Not requested block data. Banned, disconnecting.

As a result, no new node is able to sync with the parachain. I'm seeking advice or insights on the following:

  1. What could be causing the "Not requested block data" issue in the context of syncing new nodes with the bootnodes?
  2. The numeric values reported in the logs (-536870912 to -2147483648) are confusing. Can someone explain their significance?
  3. Are there any known solutions or workarounds to resolve this syncing issue?
Improve this question
3
  • substrate.stackexchange.com/questions/10561/… Commented Nov 29, 2023 at 15:50
  • I am experiencing this issue too, I am syncing the relaychain with warp sync and started seeing this exact message in the logs Commented Apr 12, 2024 at 9:22
  • it seems the reason to be those nodes to not be archive nodes and not having the body of the requested block. Commented Apr 17, 2024 at 8:46

0

Reset to default

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.