Panic: called fail_with on already-failed connection state #1510
Assignees
Comments
|
I keep getting this even after trashing all database. Click triangle to reveal logs |
|
There was a stale zebrad process, which caused all the subsequent crashes. After I killed it, all is good. |
|
I am not totally sure but i think that if we do a port already in use check before starting any networking process as suggested at #1484 (comment) we can avoid this issue. |
This panic happens due to a bug in Fixing the misuse of |
|
We should also check the other assumptions made by the inbound and sync services. We know there's at least one other bug where the network code handles connection state incorrectly: #1435 - peer connection permanent failure. |
This was referenced Dec 16, 2020
|
Got this again. LogsClick triangle to reveal details PanicDetailed Backtrace
```
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1: backtrace::backtrace::libunwind::trace::h56b5b89d46ea18ee
at /Users/rex/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.54/src/backtrace/libunwind.rs:90
88 │ #[inline(always)]
89 │ pub unsafe fn trace(mut cb: &mut dyn FnMut(&super::Frame) -> bool) {
90 > uw::_Unwind_Backtrace(trace_fn, &mut cb as *mut _ as *mut _);
91 │
92 │ extern "C" fn trace_fn(
2: backtrace::backtrace::trace_unsynchronized::h35ba3908cf2057d6
at /Users/rex/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.54/src/backtrace/mod.rs:66
64 │ /// See information on `trace` for caveats on `cb` panicking.
65 │ pub unsafe fn trace_unsynchronized bool>(mut cb: F) {
66 > trace_imp(&mut cb)
67 │ }
68 │
3: backtrace::backtrace::trace::h0b6131d78bbf6f4f
at /Users/rex/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.54/src/backtrace/mod.rs:53
51 │ pub fn trace bool>(cb: F) {
52 │ let _guard = crate::lock::lock();
53 > unsafe { trace_unsynchronized(cb) }
54 │ }
55 │
4: backtrace::capture::Backtrace::create::h8d054d598eb8a93e
at /Users/rex/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.54/src/capture.rs:176
174 │ let mut frames = Vec::new();
175 │ let mut actual_start_index = None;
176 > trace(|frame| {
177 │ frames.push(BacktraceFrame {
178 │ frame: Frame::Raw(frame.clone()),
5: backtrace::capture::Backtrace::new::h89e80605e5dd4af5
at /Users/rex/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.54/src/capture.rs:140
138 │ #[inline(never)] // want to make sure there's a frame here to remove
139 │ pub fn new() -> Backtrace {
140 > let mut bt = Self::create(Self::new as usize);
141 │ bt.resolve();
142 │ bt
6: color_eyre::config::PanicHook::panic_report::ha2f85b9c0f7cb762
at /Users/rex/.cargo/registry/src/github.com-1ecc6299db9ec823/color-eyre-0.5.10/src/config.rs:982
980 │
981 │ let backtrace = if capture_bt {
982 > Some(backtrace::Backtrace::new())
983 │ } else {
984 │ None
The application panicked (crashed).
|
|
We're actively working on this code at the moment:
|
1 task
This was referenced Jan 15, 2021
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Suggested Solution
Stop calling
fail_withon already-failed connection states.Detailed Logs
Click triangle to reveal logs
Error
Metadata
SpanTrace
BackTrace
The text was updated successfully, but these errors were encountered: