Skip to content
This repository has been archived by the owner on Jan 22, 2025. It is now read-only.

validator: thread 'solana-listen' panicked #652

Closed
mvines opened this issue Jul 16, 2018 · 4 comments
Closed

validator: thread 'solana-listen' panicked #652

mvines opened this issue Jul 16, 2018 · 4 comments
Assignees
Milestone

Comments

@mvines
Copy link
Contributor

mvines commented Jul 16, 2018

I've seen this crash a couple times from testnet validator logs, first time was totally by accident
(cc: #651)

2018-07-16T23:32:54Z solana.daemon-validator[9389]: thread 'solana-listen' panicked at 'assertion failed: `(left != right)`
2018-07-16T23:32:54Z solana.daemon-validator[9389]:   left: `V4(35.231.86.32:9004)`,
2018-07-16T23:32:54Z solana.daemon-validator[9389]:  right: `V4(35.231.86.32:9004)`', src/crdt.rs:1003:17
2018-07-16T23:32:55Z solana.daemon-validator[9389]: note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
2018-07-16T23:32:55Z solana.daemon-validator[9389]: stack backtrace:
2018-07-16T23:32:55Z solana.daemon-validator[9389]:    0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
2018-07-16T23:32:55Z solana.daemon-validator[9389]:              at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
2018-07-16T23:32:55Z solana.daemon-validator[9389]:    1: std::sys_common::backtrace::print
2018-07-16T23:32:55Z solana.daemon-validator[9389]:              at libstd/sys_common/backtrace.rs:71
2018-07-16T23:32:55Z solana.daemon-validator[9389]:              at libstd/sys_common/backtrace.rs:59
2018-07-16T23:32:55Z solana.daemon-validator[9389]:    2: std::panicking::default_hook::{{closure}}
2018-07-16T23:32:55Z solana.daemon-validator[9389]:              at libstd/panicking.rs:211
2018-07-16T23:32:55Z solana.daemon-validator[9389]:    3: std::panicking::default_hook
2018-07-16T23:32:55Z solana.daemon-validator[9389]:              at libstd/panicking.rs:227
2018-07-16T23:32:55Z solana.daemon-validator[9389]:    4: std::panicking::rust_panic_with_hook
2018-07-16T23:32:55Z solana.daemon-validator[9389]:              at libstd/panicking.rs:463
2018-07-16T23:32:55Z solana.daemon-validator[9389]:    5: std::panicking::begin_panic_fmt
2018-07-16T23:32:55Z solana.daemon-validator[9389]:              at libstd/panicking.rs:350
2018-07-16T23:32:55Z solana.daemon-validator[9389]:    6: solana::crdt::Crdt::handle_blob
2018-07-16T23:32:55Z solana.daemon-validator[9389]:    7: <alloc::vec_deque::VecDeque<A> as core::iter::traits::FromIterator<A>>::from_iter
2018-07-16T23:32:55Z solana.daemon-validator[9389]:    8: solana::crdt::Crdt::run_listen
@mvines mvines added this to the v0.7.0 milestone Jul 16, 2018
@mvines
Copy link
Contributor Author

mvines commented Jul 16, 2018

We're hitting this assert:

assert_ne!(from.contact_info.tvu_window, me.contact_info.tvu_window);

@mvines
Copy link
Contributor Author

mvines commented Jul 16, 2018

In the above backtrace, 35.231.86.32 is the public IP address of the validator that the crash occurred on

@aeyakovenko
Copy link
Member

did a node restart under a different identity on the same port?

@mvines
Copy link
Contributor Author

mvines commented Jul 17, 2018

No I’m pretty sure that didn’t occur

@mvines mvines self-assigned this Jul 17, 2018
vkomenda pushed a commit to vkomenda/solana that referenced this issue Aug 29, 2021
Bumps [@babel/cli](https://github.com/babel/babel/tree/HEAD/packages/babel-cli) from 7.11.6 to 7.12.1.
- [Release notes](https://github.com/babel/babel/releases)
- [Changelog](https://github.com/babel/babel/blob/main/CHANGELOG.md)
- [Commits](https://github.com/babel/babel/commits/v7.12.1/packages/babel-cli)

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
buffalojoec pushed a commit to buffalojoec/solana that referenced this issue Apr 8, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants