qdrvm / kagome

Kagome - C++20 implementation of Polkadot Host
https://kagome.readthedocs.io
Apache License 2.0
159 stars 34 forks source link

Cannot restart syncing archive node #1694

Open AltOrder opened 1 year ago

AltOrder commented 1 year ago

Starting and stopping a syncing archive node fails for Kusama and Polkadot. This happens both in Full and Fast mode.

docker logs kagome -f
...
...
23.07.14 19:30:28.992889  kagome           Info      BlockExecutor  Imported block #484 (0x8e38…b0c1) within 28 ms. (lag 1324 days)
23.07.14 19:30:29.022523  kagome           Info      BlockStorage  Added block #485 (0x92f7…62ac) as child of #484 (0x8e38…b0c1)
23.07.14 19:30:29.022667  kagome           Info      BlockExecutor  Imported block #485 (0x92f7…62ac) within 28 ms. (lag 1324 days)
Fatal: callImport: unknown import: env.��]^AV
23.07.14 19:30:47.467629  kagome           Info      AppConfiguration  Soramitsu Kagome started. Version: 0.9.0-70
23.07.14 19:30:47.468121  kagome           Info      AppConfiguration  Automatically added IPv6 listen address /ip6/::/tcp/30363
23.07.14 19:30:47.468154  kagome           Info      AppConfiguration  Automatically added IPv4 listen address /ip4/0.0.0.0/tcp/30363
23.07.14 19:30:47.468341  kagome           Info      AppConfiguration  Listen addresses are set. The p2p port value would be ignored then.
23.07.14 19:30:47.526633  kagome           Warning   chain_spec  Field 'chainType' was not specified in the chain spec. 'Live' by default.
23.07.14 19:30:47.526691  kagome           Warning   chain_spec  A non-empty set of 'badBlocks' encountered! They might not be taken into account!
23.07.14 19:30:47.836981  kagome           Warning   Injector  Can not obtain a libp2p keypair from crypto storage. A unique one will be generated
23.07.14 19:30:47.847528  kagome           Info      BlockTree  Highest block: #485 (0x92f7…62ac), Last finalized: #0 (0xb0a8…dafe)
23.07.14 19:30:47.856044  kagome           Warning   BlockTree  Can't add existing non-finalized block #0 (0xb0a8…dafe) to block tree: block, which should have been inserted, already exists in the tree
23.07.14 19:30:47.952965  kagome           Warning   PrunerStateRecovery  Running pruner on a non-empty non-pruned storage may lead to skipping some stored states.
Harrm commented 1 year ago

This happens due to some problems with the new trie pruner, when https://github.com/soramitsu/kagome/pull/1702 is merged you will be able to run the node without it, while it's still unstable.