Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

State mismatch in libp2p: Expected alive incoming. Got None. #6112

Closed
tomaka opened this issue May 22, 2020 · 2 comments
Closed

State mismatch in libp2p: Expected alive incoming. Got None. #6112

tomaka opened this issue May 22, 2020 · 2 comments
Labels
I3-bug The node fails to follow expected behavior.

Comments

@tomaka
Copy link
Contributor

tomaka commented May 22, 2020 •
edited
Loading

This error seems to be printed once per hour on average on our nodes:

2020-05-22 01:18:55.134 tokio-runtime-worker ERROR sub-libp2p State mismatch in libp2p: Expected alive incoming. Got None.

This can either be caused by a bug in the peerset sending inconsistent messages or by a bug in the state machine that handles the peerset's messages.
@tomaka tomaka added the I3-bug The node fails to follow expected behavior. label May 22, 2020
@romanb romanb mentioned this issue Jun 10, 2020
Merged
@romanb
Copy link
Contributor

romanb commented Jun 22, 2020

For what it is worth, I don't see this error any more in the Kibana logs for the "logstash-kusama" index family since June 14th. Are there other places or log indices to check?

@tomaka
Copy link
Contributor Author

tomaka commented Jun 22, 2020

Let's assumed that it is fixed. We can always reopen if the error is seen in the logs again.

@tomaka tomaka closed this as completed Jun 22, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
I3-bug The node fails to follow expected behavior.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@romanb @tomaka