AstarNetwork/Astar

shiden - Thread 'main' panicked at 'slot_duration is always present

CrazySurfBoy opened this issue ยท 2 comments

CrazySurfBoy commented

staketechnologies/astar-collator:v5.36.0

2024-04-24 07:37:18 [Parachain] ๐Ÿ’ป Target environment: gnu
โ”‚ 2024-04-24 07:37:18 [Parachain] ๐Ÿ’ป CPU: Intel(R) Xeon(R) CPU @ 2.20GHz
โ”‚ 2024-04-24 07:37:18 [Parachain] ๐Ÿ’ป CPU cores: 8
โ”‚ 2024-04-24 07:37:18 [Parachain] ๐Ÿ’ป Memory: 60263MB
โ”‚ 2024-04-24 07:37:18 [Parachain] ๐Ÿ’ป Kernel: 5.15.0-1038-gcp
โ”‚ 2024-04-24 07:37:18 [Parachain] ๐Ÿ’ป Linux distribution: Ubuntu 22.04.4 LTS
โ”‚ 2024-04-24 07:37:18 [Parachain] ๐Ÿ’ป Virtual machine: yes
โ”‚ 2024-04-24 07:37:18 [Parachain] ๐Ÿ“ฆ Highest known block at #0
โ”‚ 2024-04-24 07:37:18 [Parachain] ใ€ฝ๏ธ Prometheus exporter started at 127.0.0.1:9615
โ”‚ 2024-04-24 07:37:18 [Relaychain] Sending fatal alert BadCertificate
โ”‚ 2024-04-24 07:37:18 [Relaychain] ๐Ÿ”e Discovered new external address for our node: /ip4/34.141.109.95/tcp/21495/ws/p2p/12D3KooWKYZsWRKCXAMubxRwcTeafLBkXfeqj7wvj4kV1cFzqJpJ
โ”‚
โ”‚ ====================
โ”‚
โ”‚ Version: 5.36.0-e39c912f55f
โ”‚
โ”‚ 0: sp_panic_handler::set::{{closure}}
โ”‚ 1: <alloc::boxed::Box<F,A> as core::ops::function::Fn>::call
โ”‚ at rustc/90c541806f23a127002de5b4038be731ba1458ca/library/alloc/src/boxed.rs:1987:9
โ”‚ std::panicking::rust_panic_with_hook
โ”‚ at rustc/90c541806f23a127002de5b4038be731ba1458ca/library/std/src/panicking.rs:695:13
โ”‚ 2: std::panicking::begin_panic_handler::{{closure}}
โ”‚ at rustc/90c541806f23a127002de5b4038be731ba1458ca/library/std/src/panicking.rs:582:13
โ”‚ 3: std::sys_common::backtrace::__rust_end_short_backtrace
โ”‚ at rustc/90c541806f23a127002de5b4038be731ba1458ca/library/std/src/sys_common/backtrace.rs:150:18
โ”‚ 4: rust_begin_unwind
โ”‚ at rustc/90c541806f23a127002de5b4038be731ba1458ca/library/std/src/panicking.rs:578:5
โ”‚ 5: core::panicking::panic_fmt
โ”‚ at rustc/90c541806f23a127002de5b4038be731ba1458ca/library/core/src/panicking.rs:67:14
โ”‚ 6: core::result::unwrap_failed
โ”‚ at rustc/90c541806f23a127002de5b4038be731ba1458ca/library/core/src/result.rs:1687:5
โ”‚ 7: astar_collator::parachain::service::start_node_impl::{{closure}}::{{closure}}
โ”‚ 8: sc_service::builder::gen_rpc_module
โ”‚ 9: sc_service::builder::spawn_tasks::{{closure}}
โ”‚ 10: sc_service::builder::spawn_tasks
โ”‚ 11: astar_collator::parachain::service::start_node_impl::{{closure}}
โ”‚ 12: astar_collator::command::run::{{closure}}::{{closure}}
โ”‚ 13: sc_cli::runner::Runner::run_node_until_exit
โ”‚ 14: astar_collator::command::run
โ”‚ 15: astar_collator::main
โ”‚ 16: std::sys_common::backtrace::__rust_begin_short_backtrace
โ”‚ 17: main
โ”‚ 18:
โ”‚ 19: __libc_start_main
โ”‚ 20: _start
โ”‚
โ”‚
โ”‚ Thread 'main' panicked at 'slot_duration is always present; qed.: RuntimeApiError(Application(Execution(Other("Exported method AuraApi_slot_duration is not found"))))', /home/astar-admin/.cargo/git/checkouts/frontier-f8f9ba8bcc03a23e/8a5a81a/client/rpc/src/eth/pending.rs:193
โ”‚
โ”‚ This is a bug. Please report it at:
โ”‚
โ”‚ https://github.com/AstarNetwork/Astar/issues/new

ashutoshvarma commented

Thanks for the report!
Can you share the command you used to start node?

Dinonard commented

Can be reproduced with:

./astar-collator --name test --chain=shiden --state-cache-size 1 --unsafe-rpc-external --rpc-cors all --tmp --rpc-methods Unsafe --rpc-max-connections 2000 --enable-evm-rpc