-
Notifications
You must be signed in to change notification settings - Fork 333
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
Thread 'tokio-runtime-worker' panicked #595
Comments
Tried running with debugging options I've seen in #541 It has changed nothing, seems like something in my data is corrupted, will try to run other node with other data location, keeping those for a week or so in case if you need the data files to investigate further. |
Thank you for trying.
|
I will try on the chain that was failing yesterday but I am afraid that the same thing may happen as it did happen with second attempt node - which after waiting some time and restarting went further and fully synchronized the chain. |
The way I tried to start the node does not seem to take the provided arguments: How else I may try to set those debugging/tracing options? |
@gdzien-co you should try to put the flags before the |
Perfect, log is now way faster to scroll the screen, if the node will fail (I am running it as the 2nd one on the same network, so some network port collision is expected). |
log-new-net.zip Can provide corrupted files upon request. |
Closing it in favor of #541 |
2021-07-12 17:23:30 [Relaychain] ✨ Imported #676997 (0xe8a9…f680)
====================
Version: 0.9.1-78d1dae-x86_64-linux-gnu
0: sp_panic_handler::set::{{closure}}
1: std::panicking::rust_panic_with_hook
at rustc/fe1bf8e05c39bdcc73fc09e246b7209444e389bc/library/std/src/panicking.rs:595:17
2: std::panicking::begin_panic_handler::{{closure}}
at rustc/fe1bf8e05c39bdcc73fc09e246b7209444e389bc/library/std/src/panicking.rs:497:13
3: std::sys_common::backtrace::__rust_end_short_backtrace
at rustc/fe1bf8e05c39bdcc73fc09e246b7209444e389bc/library/std/src/sys_common/backtrace.rs:141:18
4: rust_begin_unwind
at rustc/fe1bf8e05c39bdcc73fc09e246b7209444e389bc/library/std/src/panicking.rs:493:5
5: core::panicking::panic_fmt
at rustc/fe1bf8e05c39bdcc73fc09e246b7209444e389bc/library/core/src/panicking.rs:92:14
6: core::option::expect_failed
at rustc/fe1bf8e05c39bdcc73fc09e246b7209444e389bc/library/core/src/option.rs:1292:5
7: sc_client_db::Backend::try_commit_operation
8: <sc_client_db::Backend as sc_client_api::backend::Backend>::commit_operation
9: <sc_service::client::client::Client<B,E,Block,RA> as sc_client_api::backend::LockImportRun<Block,B>>::lock_import_and_run::{{closure}}
10: <core::future::from_generator::GenFuture as core::future::future::Future>::poll
11: <core::future::from_generator::GenFuture as core::future::future::Future>::poll
12: <core::future::from_generator::GenFuture as core::future::future::Future>::poll
13: <core::future::from_generator::GenFuture as core::future::future::Future>::poll
14: <core::future::from_generator::GenFuture as core::future::future::Future>::poll
15: <core::future::from_generator::GenFuture as core::future::future::Future>::poll
16: <core::future::from_generator::GenFuture as core::future::future::Future>::poll
17: <futures_util::future::future::map::Map<Fut,F> as core::future::future::Future>::poll
18: <sc_service::task_manager::prometheus_future::PrometheusFuture as core::future::future::Future>::poll
19: <core::future::from_generator::GenFuture as core::future::future::Future>::poll
20: <tracing_futures::Instrumented as core::future::future::Future>::poll
21: std::thread::local::LocalKey::with
22: futures_executor::local_pool::block_on
23: tokio::runtime::task::core::Core<T,S>::poll
24: tokio::runtime::task::harness::Harness<T,S>::poll::{{closure}}
25: tokio::runtime::task::harness::Harness<T,S>::poll
26: tokio::runtime::blocking::pool::Inner::run
27: tokio::runtime::context::enter
28: std::sys_common::backtrace::__rust_begin_short_backtrace
29: core::ops::function::FnOnce::call_once{{vtable.shim}}
30: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce>::call_once
at rustc/fe1bf8e05c39bdcc73fc09e246b7209444e389bc/library/alloc/src/boxed.rs:1546:9
<alloc::boxed::Box<F,A> as core::ops::function::FnOnce>::call_once
at rustc/fe1bf8e05c39bdcc73fc09e246b7209444e389bc/library/alloc/src/boxed.rs:1546:9
std::sys::unix::thread::Thread::new::thread_start
at rustc/fe1bf8e05c39bdcc73fc09e246b7209444e389bc/library/std/src/sys/unix/thread.rs:71:17
31: start_thread
32: clone
Thread 'tokio-runtime-worker' panicked at 'existence of block with number
new_canonical
implies existence of blocks with all numbers before it; qed', /home/gh-actions/.cargo/git/checkouts/substrate-7e08433d4c370a21/9c57262/client/db/src/lib.rs:1218
This is a bug. Please report it at:
The text was updated successfully, but these errors were encountered: