This one I reproduced this twice on 34.65.46.56:~/broken3.sh which is captured by polkadot-v0.9.41 syncing Kusama
2023-04-19 23:13:03 💾 Database: ParityDb at /home/ubuntu/polkadot.broken3/chains/ksmcc3/paritydb/full
2023-04-19 23:13:03 ⛓ Native runtime: kusama-9401 (parity-kusama-0.tx21.au2)
====================
Version: 0.9.41-e203bfb396e
0: sp_panic_handler::set::{{closure}}
1: <alloc::boxed::Box<F,A> as core::ops::function::Fn<Args>>::call
at /rustc/9eb3afe9ebe9c7d2b84b71002d44f4a0edac95e0/library/alloc/src/boxed.rs:2002:9
std::panicking::rust_panic_with_hook
at /rustc/9eb3afe9ebe9c7d2b84b71002d44f4a0edac95e0/library/std/src/panicking.rs:692:13
2: std::panicking::begin_panic_handler::{{closure}}
at /rustc/9eb3afe9ebe9c7d2b84b71002d44f4a0edac95e0/library/std/src/panicking.rs:577:13
3: std::sys_common::backtrace::__rust_end_short_backtrace
at /rustc/9eb3afe9ebe9c7d2b84b71002d44f4a0edac95e0/library/std/src/sys_common/backtrace.rs:137:18
4: rust_begin_unwind
at /rustc/9eb3afe9ebe9c7d2b84b71002d44f4a0edac95e0/library/std/src/panicking.rs:575:5
5: core::panicking::panic_fmt
at /rustc/9eb3afe9ebe9c7d2b84b71002d44f4a0edac95e0/library/core/src/panicking.rs:64:14
6: core::panicking::panic
at /rustc/9eb3afe9ebe9c7d2b84b71002d44f4a0edac95e0/library/core/src/panicking.rs:114:5
7: parity_db::file::TableFile::read_at
8: parity_db::column::Column::get_value
9: parity_db::column::HashColumn::get_in_index
10: parity_db::column::HashColumn::get
11: parity_db::db::Db::get
12: <sc_client_db::parity_db::DbAdapter as sp_database::Database<H>>::get
13: sc_service::builder::new_db_backend
14: polkadot_service::new_full
15: polkadot_cli::command::run_node_inner::{{closure}}::{{closure}}
16: sc_cli::runner::Runner<C>::run_node_until_exit
17: polkadot_cli::command::run
18: polkadot::main
19: std::sys_common::backtrace::__rust_begin_short_backtrace
20: main
21: <unknown>
22: __libc_start_main
23: _start
Thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/parity-db-0.4.4/src/file.rs:116
This is a bug. Please report it at:
https://github.com/paritytech/polkadot/issues/new
the odd thing is my colleague claims that the node has Externalities not allowed to fail within runtime: "Trie lookup error: Database missing expected key: 0x294d588cf096b9a001ef2d5817558b007fb67577c41bf3094b6578e93560a941" problem
This one I reproduced this twice on
34.65.46.56:~/broken3.sh
which is captured by polkadot-v0.9.41 syncing Kusamathe odd thing is my colleague claims that the node has
Externalities not allowed to fail within runtime: "Trie lookup error: Database missing expected key: 0x294d588cf096b9a001ef2d5817558b007fb67577c41bf3094b6578e93560a941"
problem