run fullnode get error authenticator_state disabled

[zilongliang]

authenticator_state disabled thread 'sui-node-runtime' panicked at crates/sui-core/src/authority/authority_per_epoch_store.rs:903:2024-10-09T06:50:35.204262Z ERROR AuthorityPerEpochStore::new{epoch=0}: telemetry_subscribers: panicked at crates/sui-core/src/authority/authority_per_epoch_store.rs:903:13:

[stefan-mysten]

Hi @zilongliang

Thanks for the report. Could you provide a few more details about your setup? Which sui-node version are you using?

[mwtian]

Also can you show the full backtrace please? Btw it is a lot faster to restore from a snapshot instead of starting a fullnode from epoch 0.

[zilongliang]

Also can you show the full backtrace please? Btw it is a lot faster to restore from a snapshot instead of starting a fullnode from epoch 0.

2024-10-10T05:03:37.410911Z INFO AuthorityPerEpochStore::new{epoch=0}: sui_core::authority::authority_per_epoch_store: authenticator_state disabled thread 'sui-node-runtime' panicked at crates/sui-core/src/authority/authority_per_epoch_store.rs:903:2024-10-10T05:03:37.411095Z ERROR AuthorityPerEpochStore::new{epoch=0}: telemetry_subscribers: panicked at crates/sui-core/src/authority/authority_per_epoch_store.rs:903:13: assertion failed: s.randomness_state_enabled() panic.file="crates/sui-core/src/authority/authority_per_epoch_store.rs" panic.line=903 panic.column=13 13: assertion failed: s.randomness_state_enabled() stack backtrace: 0: 0x557aa552c375 - ::fmt::h1b9dad2a88e955ff 1: 0x557aa555a07b - core::fmt::write::h4b5a1270214bc4a7 2: 0x557aa55282df - std::io::Write::write_fmt::hd04af345a50c312d 3: 0x557aa552d831 - std::panicking::default_hook::{{closure}}::h96ab15e9936be7ed 4: 0x557aa552d50c - std::panicking::default_hook::h3cacb9c27561ad33 5: 0x557aa338de3c - telemetry_subscribers::set_panic_hook::{{closure}}::hf23417b43f726af0 6: 0x557aa552e0cf - std::panicking::rust_panic_with_hook::hfe205f6954b2c97b 7: 0x557aa552dcc3 - std::panicking::begin_panic_handler::{{closure}}::h6cb44b3a50f28c44 8: 0x557aa552c839 - std::sys::backtrace::__rust_end_short_backtrace::hf1c1f2a92799bb0e 9: 0x557aa552d984 - rust_begin_unwind 10: 0x557aa2031ce3 - core::panicking::panic_fmt::h3d8fc78294164da7 11: 0x557aa2031d6c - core::panicking::panic::hec978767ec2d35ff 12: 0x557aa29e5aec - sui_core::authority::authority_per_epoch_store::AuthorityPerEpochStore::new::h5cae570cce507c2f 13: 0x557aa20f0da4 - sui_node::SuiNode::start_async::{{closure}}::hd50c2ff992c18b3c 14: 0x557aa2118c62 - sui_node::main::{{closure}}::h43138b264ff25e18 15: 0x557aa2148a25 - tokio::runtime::task::harness::Harness<T,S>::poll::h9d16e3d8afcc7b2c 16: 0x557aa54a5a92 - tokio::runtime::scheduler::multi_thread::worker::Context::run_task::h4e1500d559c922d7 17: 0x557aa54a4d2b - tokio::runtime::scheduler::multi_thread::worker::Context::run::h5aeb48907b1057f6 18: 0x557aa54a2e4b - tokio::runtime::context::scoped::Scoped::set::hf1ab9c0a5dffcdc3 19: 0x557aa549ab8c - tokio::runtime::context::runtime::enter_runtime::hf1482e86d2baf2e1 20: 0x557aa5493ff0 - tokio::runtime::task::core::Core<T,S>::poll::h683671ea95b9ba2d 21: 0x557aa548bc48 - tokio::runtime::task::harness::Harness<T,S>::poll::hcbbb51e3abd7498c 22: 0x557aa549f054 - tokio::runtime::blocking::pool::Inner::run::h458bf7b6efb9f280 23: 0x557aa5492739 - std::sys::backtrace::__rust_begin_short_backtrace::hb3c7e098c6f820f4 24: 0x557aa5492c41 - core::ops::function::FnOnce::call_once{{vtable.shim}}::h9e0e446d9e9aa512 25: 0x557aa5533e7b - std::sys::pal::unix::thread::Thread::new::thread_start::ha8af9c992ef0b208 26: 0x7f5943828ac3 - 27: 0x7f59438ba850 - 28: 0x0 - Aborted

[zilongliang]

Hi @zilongliang

Thanks for the report. Could you provide a few more details about your setup? Which sui-node version are you using?

how can i get？

[stefan-mysten]

sui-node -V should work. Thanks!

[zilongliang]

sui-node -V

sui-node -V should work. Thanks!

I haven't run it yet, so this command doesn't exist.