Weird behavior on genesis generation. After "Consensus(Shutdown)" node shutdown. about casper-node

[matsuro-hadouken]

0: casper_node::panic_hook
1: core::ops::function::Fn::call
2: std::panicking::rust_panic_with_hook
at rustc/0cd7ff7ddfb75a38dca81ad3e76b1e984129e939/src/libstd/panicking.rs:530:17
3: rust_begin_unwind
at rustc/0cd7ff7ddfb75a38dca81ad3e76b1e984129e939/src/libstd/panicking.rs:437:5
4: std::panicking::begin_panic_fmt
at rustc/0cd7ff7ddfb75a38dca81ad3e76b1e984129e939/src/libstd/panicking.rs:391:5
5: casper_node::effect::EffectBuilder::fatal::{{closure}}
6: <futures_util::future::future::Map<Fut,F> as core::future::future::Future>::poll
7: <core::future::from_generator::GenFuture as core::future::future::Future>::poll
8: <core::future::from_generator::GenFuture as core::future::future::Future>::poll
9: <std::panic::AssertUnwindSafe as core::ops::function::FnOnce<()>>::call_once
10: tokio::runtime::task::raw::poll
11: std::thread::local::LocalKey::with
12: tokio::runtime::thread_pool::worker::Context::run_task
13: tokio::runtime::thread_pool::worker::Context::run
14: tokio::macros::scoped_tls::ScopedKey::set
15: tokio::runtime::thread_pool::worker::run
16: tokio::loom::std::unsafe_cell::UnsafeCell::with_mut
17: <std::panic::AssertUnwindSafe as core::ops::function::FnOnce<()>>::call_once
18: tokio::runtime::task::harness::Harness<T,S>::poll
19: tokio::runtime::blocking::pool::Inner::run
20: tokio::runtime::context::enter
21: tokio::runtime::handle::Handle::enter
22: std::sys_common::backtrace::__rust_begin_short_backtrace
23: core::ops::function::FnOnce::call_once{{vtable.shim}}
24: <alloc::boxed::Box as core::ops::function::FnOnce>::call_once
at rustc/0cd7ff7ddfb75a38dca81ad3e76b1e984129e939/src/liballoc/boxed.rs:1081:9
<alloc::boxed::Box as core::ops::function::FnOnce>::call_once
at rustc/0cd7ff7ddfb75a38dca81ad3e76b1e984129e939/src/liballoc/boxed.rs:1081:9
std::sys::unix::thread::Thread::new::thread_start
at rustc/0cd7ff7ddfb75a38dca81ad3e76b1e984129e939/src/libstd/sys/unix/thread.rs:87:17
25: start_thread
26: clone

panicked at 'fatal error [node/src/components/consensus/era_supervisor.rs:724]: Consensus shutting down due to inability to participate in the network', node/src/effect.rs:366:9

[matsuro-hadouken]

Just processed another restart, no success, here is full log attached.
Uploading attached.log…

[goral09]

Hi @matsuro-hadouken , thanks for the report.

From the logs, it looks like you start your node after the Genesis era start:

Shutdown if current era is inactive.
…
Consensus shutting down due to inability to participate in the network

In the PoS network, you cannot trust blocks created by validators you don't "know". Software detects that case and shuts down.

If you start a node after Genesis era start you have to provide a trusted hash.

[matsuro-hadouken]

@goral09 trusted hash been set in config and updated every restated mentioned above. This is why I believe here we have issue. I didn't check people logs, but we facing this every day in #node-rust chat. The way to fix this thing is just constantly update hash and restart + clean data folder in between. Is something not right, I try to catch hash on era change, but it doesn't helps much, it looks like something random is going on behind.

[goral09]

The way to fix this thing is just constantly update hash and restart + clean data folder in between. Is something not right, I try to catch hash on era change, but it doesn't helps much, it looks like something random is going on behind.

This shouldn't be necessary anymore.

We've tried to replicate the issues with joining but it worked every time (using PCs in different geographical locations).

[MParlikar]

We have not observed this issue for quite some time, closing.