We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Panic crash after upgrade to 5.3.0 from 5.1.3
5.3.0 downloaded from GitHub (https://github.com/sigp/lighthouse/releases/download/v5.3.0/lighthouse-v5.3.0-x86_64-unknown-linux-gnu.tar.gz)
Here is the log:
Sep 16 12:51:37.406 INFO New block received root: 0xd4910fa20440352007fdd32d647d98d710c3247478aa731364058c68111fe364, slot: 9972256 Sep 16 12:51:42.654 INFO Synced slot: 9972256, block: … empty, epoch: 311633, finalized_epoch: 311631, finalized_root: 0xd4d8…931e, exec_hash: 0x8721…3b8a (verified), peers: 109, service: slot_notifier Sep 16 12:51:48.631 INFO New block received root: 0xcfed5f1ac607f32c761b0c324c3d110e27a72ecf5ec9f454d5e355d03c8bc505, slot: 9972257 Sep 16 12:51:50.497 CRIT Task panic. This is a bug! advice: Please check above for a backtrace and notify the developers, backtrace: 0: lighthouse::run::{{closure}} 1: std::panicking::rust_panic_with_hook 2: std::panicking::begin_panic_handler::{{closure}} 3: std::sys_common::backtrace::__rust_end_short_backtrace 4: rust_begin_unwind 5: core::panicking::panic_fmt 6: core::panicking::panic 7: <libp2p_upnp::behaviour::Behaviour as libp2p_swarm::behaviour::NetworkBehaviour>::poll 8: <lighthouse_network::service::behaviour::Behaviour<E> as libp2p_swarm::behaviour::NetworkBehaviour>::poll 9: libp2p_swarm::Swarm<TBehaviour>::poll_next_event 10: lighthouse_network::service::Network<E>::poll_network 11: network::service::NetworkService<T>::spawn_service::{{closure}} 12: task_executor::TaskExecutor::spawn_handle::{{closure}} 13: tokio::runtime::task::raw::poll 14: tokio::runtime::scheduler::multi_thread::worker::Context::run_task 15: tokio::runtime::task::raw::poll 16: std::sys_common::backtrace::__rust_begin_short_backtrace 17: core::ops::function::FnOnce::call_once{{vtable.shim}} 18: std::sys::pal::unix::thread::Thread::new::thread_start 19: <unknown> 20: <unknown> , message: None, location: /cargo/registry/src/index.crates.io-6f17d22bba15001f/libp2p-upnp-0.2.2/src/behaviour.rs:475:41 Sep 16 12:51:50.501 INFO Saved DHT state service: network Sep 16 12:51:50.502 INFO Network service shutdown service: network Sep 16 12:51:50.570 INFO Internal shutdown received reason: Panic (fatal error) Sep 16 12:51:50.571 INFO Shutting down.. reason: Failure("Panic (fatal error)") Sep 16 12:51:54.673 INFO Saved beacon chain to disk service: beacon
Upgrade smoothly.
None
The text was updated successfully, but these errors were encountered:
Looks like a (another) UPnP bug. Try running with --disable-upnp
--disable-upnp
Sorry, something went wrong.
Sorry about that, I thought we'd already fixed all the issues in UPnP.
jxs
No branches or pull requests
Description
Panic crash after upgrade to 5.3.0 from 5.1.3
Version
5.3.0 downloaded from GitHub (https://github.com/sigp/lighthouse/releases/download/v5.3.0/lighthouse-v5.3.0-x86_64-unknown-linux-gnu.tar.gz)
Present Behaviour
Here is the log:
Expected Behaviour
Upgrade smoothly.
Steps to resolve
None
The text was updated successfully, but these errors were encountered: