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

FinalizedBlock stop syncing after #1280777 (Westend) #1755

Closed
anhcao142 opened this issue Sep 26, 2020 · 1 comment Β· Fixed by paritytech/substrate#7321
Closed

FinalizedBlock stop syncing after #1280777 (Westend) #1755

anhcao142 opened this issue Sep 26, 2020 · 1 comment Β· Fixed by paritytech/substrate#7321

Comments

@anhcao142
Copy link

Here is some of the log:

2020-09-26 10:08:37.794 tokio-runtime-worker INFO substrate  πŸ’€ Idle (7 peers), best: #2379455 (0x40a7…61e2), finalized #1280777 (0xd438…17b2), ⬇ 5.3kiB/s ⬆ 3.3kiB/s
2020-09-26 10:08:37.910 tokio-runtime-worker INFO substrate  ✨ Imported #2379456 (0x3ca5…0a04)
2020-09-26 10:08:39.104 tokio-runtime-worker INFO sc_network::service  πŸ’” Invalid justification provided by 12D3KooWPVPzs42GvRBShdUMtFsk4SvnByrSdWqb6aeAAHvLMSLS for #0x6497…1ac2
2020-09-26 10:08:41.342 tokio-runtime-worker INFO sc_network::service  πŸ’” Invalid justification provided by 12D3KooWNTdEfs9zEMZami5QUmvA84idGm2jiBCijmrXVzfSJXUg for #0x6497…1ac2
2020-09-26 10:08:41.723 tokio-runtime-worker WARN sync  Received message on non-registered protocol: [100, 111, 116, 50]
2020-09-26 10:08:42.166 tokio-runtime-worker INFO sc_network::service  πŸ’” Invalid justification provided by 12D3KooWGYpUczvWdZwqobcWMhgc8X1rnRHbnYyJmXXi1ZUZMjX8 for #0x6497…1ac2
2020-09-26 10:08:42.359 tokio-runtime-worker INFO sc_network::service  πŸ’” Invalid justification provided by 12D3KooWSjTJk8Qd7CCR61r6dnPzTKUZkXYNaPnxWtrMZAqLhqxE for #0x6497…1ac2
2020-09-26 10:08:42.799 tokio-runtime-worker INFO substrate  πŸ’€ Idle (8 peers), best: #2379456 (0x3ca5…0a04), finalized #1280777 (0xd438…17b2), ⬇ 5.8kiB/s ⬆ 3.9kiB/s
2020-09-26 10:08:43.339 tokio-runtime-worker INFO sc_network::service  πŸ’” Invalid justification provided by 12D3KooWS7KgBupG57tRaNz5wT6k86SPzxPXjuYBjrYQ2ojepsXD for #0x6497…1ac2
2020-09-26 10:08:43.477 tokio-runtime-worker INFO sc_network::service  πŸ’” Invalid justification provided by 12D3KooWM46mD2uZMkQJgH7XXJCDbn4Yj2h7DcWtBqWYub2rbecX for #0x6497…1ac2
2020-09-26 10:08:44.042 tokio-runtime-worker INFO substrate  ✨ Imported #2379443 (0x9ae4…7bc9)
2020-09-26 10:08:44.083 tokio-runtime-worker INFO substrate  ✨ Imported #2379457 (0x76b4…0ad6)
2020-09-26 10:08:44.887 tokio-runtime-worker INFO sc_network::service  πŸ’” Invalid justification provided by 12D3KooWRqpXYcAXwxvLQvM7beaUYwyVUzbsokwa78SZqnc3yKY1 for #0x6497…1ac2
2020-09-26 10:08:45.887 tokio-runtime-worker INFO sc_network::service  πŸ’” Invalid justification provided by 12D3KooWJJwQ7BFigyWz1Dhckiut22yeTjdGXxhKAUojCD89uerB for #0x6497…1ac2
2020-09-26 10:08:47.134 tokio-runtime-worker INFO sc_network::service  πŸ’” Invalid justification provided by 12D3KooWByVpK92hMi9CzTjyFg9cPHDU5ariTM3EPMq9vdh5S5Po for #0x6497…1ac2
2020-09-26 10:08:47.488 tokio-runtime-worker WARN sync  Received message on non-registered protocol: [100, 111, 116, 50]
2020-09-26 10:08:47.807 tokio-runtime-worker INFO substrate  πŸ’€ Idle (7 peers), best: #2379457 (0x76b4…0ad6), finalized #1280777 (0xd438…17b2), ⬇ 6.5kiB/s ⬆ 4.3kiB/s
2020-09-26 10:08:48.665 tokio-runtime-worker WARN sync  Received message on non-registered protocol: [100, 111, 116, 49]
2020-09-26 10:08:48.665 tokio-runtime-worker WARN sync  Received message on non-registered protocol: [100, 111, 116, 49]
2020-09-26 10:08:49.046 tokio-runtime-worker INFO sc_network::service  πŸ’” Invalid justification provided by 12D3KooWRF5mBBV3QL4zTfHokJin9Dc4TYPaUXAvPgpeZZzue8n3 for #0x6497…1ac2
2020-09-26 10:08:49.615 tokio-runtime-worker INFO substrate  ✨ Imported #2379458 (0x8eb4…c403)
2020-09-26 10:08:49.745 tokio-runtime-worker INFO sc_informant  ♻️  Reorg on #2379458,0x8eb4…c403 to #2379458,0x1578…8830, common ancestor #2379457,0x76b4…0ad6
2020-09-26 10:08:49.745 tokio-runtime-worker INFO substrate  ✨ Imported #2379458 (0x1578…8830)
2020-09-26 10:08:50.631 tokio-runtime-worker INFO sc_network::service  πŸ’” Invalid justification provided by 12D3KooWN6bf9Fq1Yo4v4qR6Z6fHtkvmag3ceCb59MFshTbqFhAX for #0x6497…1ac2
2020-09-26 10:08:52.807 tokio-runtime-worker INFO substrate  πŸ’€ Idle (8 peers), best: #2379458 (0x1578…8830), finalized #1280777 (0xd438…17b2), ⬇ 5.0kiB/s ⬆ 3.2kiB/s
2020-09-26 10:08:52.876 tokio-runtime-worker INFO sc_network::service  πŸ’” Invalid justification provided by 12D3KooWKer94o1REDPtAhjtYR4SdLehnSrN8PEhBnZm5NBoCrMC for #0x6497…1ac2

Here is the node info:

2020-09-26 10:08:54.051 main INFO sc_cli::runner  Parity Polkadot
2020-09-26 10:08:54.051 main INFO sc_cli::runner  ✌️  version 0.8.23-d327000af-x86_64-linux-gnu
2020-09-26 10:08:54.051 main INFO sc_cli::runner  ❀️  by Parity Technologies <admin@parity.io>, 2017-2020
2020-09-26 10:08:54.051 main INFO sc_cli::runner  πŸ“‹ Chain specification: Westend
2020-09-26 10:08:54.051 main INFO sc_cli::runner  🏷  Node name: cuddly-rule-1468
2020-09-26 10:08:54.052 main INFO sc_cli::runner  πŸ‘€ Role: FULL
2020-09-26 10:08:54.052 main INFO sc_cli::runner  πŸ’Ύ Database: RocksDb at /polkadot/.local/share/polkadot/chains/westend2/db
2020-09-26 10:08:54.052 main INFO sc_cli::runner  β›“  Native runtime: westend-43 (parity-westend-0.tx3.au2)
2020-09-26 10:09:04.610 main INFO sub-libp2p  🏷  Local node identity is: 12D3KooWKN3PeEhFziHymAQyGgNZtCdUoeEF95365vzCxgFD3Z7a (legacy representation: QmSWqapNptg9UZeqcbqB5r4PGW7CeawCPf5BByDxfnRbSp)
2020-09-26 10:09:04.621 main INFO sc_service::builder  πŸ“¦ Highest known block at #2379458

Here is the command I used to start the node

docker run -d -p 30333:30333 -p 9933:9933 -v /me/data:/data chevdor/polkadot:latest polkadot --rpc-external --chain westend
@andresilva
Copy link
Contributor

This will be fixed by paritytech/substrate#7321 although paritytech/substrate#7307 and paritytech/substrate#7322 also help. Should be included in the next polkadot release. You will have to resync from scratch though since some data in your local db is already inconsistent and unrecoverable.

This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants