-
Notifications
You must be signed in to change notification settings - Fork 533
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"waiting for 3 peers to be connected" while sync a node #2750
Comments
2024-05-06 03:47:18 ⏩ Warping, Waiting for 3 peers to be connected, 0.00 Mib (16 peers), best: #0 (0xfc41…a64c), finalized #0 (0xfc41…a64c), ⬇ 57 B/s ⬆ 64 B/s the number of peers increased but still not syncing |
remove the Lines 350 to 360 in 16f147e
|
It should be supported. I'm waiting for the relaychain to sync the state.
|
paritytech/polkadot-sdk#2467 should fix it.
@xlc please publish the 2.25.0 docker image. |
Thanks, this could work. Hope 2.25.0 can resovle it. |
2.25 is published |
Parachain
|
maybe wrap sync depends on the new trie format #2467 |
Describe the bug
I tried to sync a node with:
sudo docker run -it --privileged=true -v /my disk:/acala/data acala/acala-node:2.24.0 --base-path=/acala/data --chain=acala --name=name --rpc-external --rpc-cors=all --rpc-port=9933 --sync=warp -- --sync=warp
using the warp mode
this
"Waiting for 3 peers to be connected " has been occuring a whole day but my previous experience tells me ususaly this sync process only lasts one or two hours.
Is this normal ?
See the log below:
⏩ Warping, Waiting for 3 peers to be connected, 0.00 Mib (10 peers), best: #0 (0xfc41…a64c), finalized #0 (0xfc41…a64c), ⬇ 2.4kiB/s ⬆ 0.5kiB/s
2024-05-05 03:02:42 [Relaychain] ✨ Imported #20635030 (0xf240…3221)
2024-05-05 03:02:45 [Relaychain] 💤 Idle (8 peers), best: #20635030 (0xf240…3221), finalized #20635026 (0x91d7…89f3), ⬇ 141.1kiB/s ⬆ 229.3kiB/s
2024-05-05 03:02:45 ⏩ Warping, Waiting for 3 peers to be connected, 0.00 Mib (10 peers), best: #0 (0xfc41…a64c), finalized #0 (0xfc41…a64c), ⬇ 57 B/s ⬆ 51 B/s
Many thanks
The text was updated successfully, but these errors were encountered: