Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

Did not finalize blocks in sequential order. #4130

Closed
elshan-eth opened this issue Oct 22, 2021 · 7 comments
Closed

Did not finalize blocks in sequential order. #4130

elshan-eth opened this issue Oct 22, 2021 · 7 comments

Comments

@elshan-eth
Copy link

Hi

I restarted kusama node and next launch I had the error: Did not finalize blocks in sequential order.

@bkchr
Copy link
Member

bkchr commented Oct 22, 2021

CC @andresilva

@andresilva
Copy link
Contributor

andresilva commented Oct 22, 2021

Can you provide some more details about how you did the initial sync? Were you using the default options for everything (i.e. polkadot --chain kusama?).

@elshan-eth
Copy link
Author

I used: polkadot --name "kusama node" --chain kusama --listen-addr /ip4/0.0.0.0/tcp/5050/ws --sync Fast --rpc-cors all

@andresilva
Copy link
Contributor

This is almost certainly caused by the usage of fast sync (which is still a relatively new feature). I suppose you don't have any logs for this (just the generic default logs won't provide enough info to figure it out), so we'll need to replicate this on our side.

cc @arkpar

@arkpar
Copy link
Member

arkpar commented Oct 22, 2021

Fast sync is only allowed on a clean start with an empty database. Otherwise the node should print a message and fall back to full sync. Furthermore it won't work on kusama until paritytech/substrate#9239 is merged.

@elshan-eth
Copy link
Author

Thank you!

@bkchr
Copy link
Member

bkchr commented Oct 23, 2021

@CryptoBadBoy I assume this can be closed then?

@bkchr bkchr closed this as completed Oct 23, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants