Skip to content
New issue

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

Nodes sometimes fail to connect #883

Closed
tomaka opened this issue Jan 22, 2019 · 2 comments
Closed

Nodes sometimes fail to connect #883

tomaka opened this issue Jan 22, 2019 · 2 comments
Assignees
Labels

Comments

@tomaka
Copy link
Member

tomaka commented Jan 22, 2019

Reproduction steps:

  • Open two terminals.
  • Run the chat example in both. There is chance that you get a "Connection reset by peer" error in one of them.
  • If you don't get the error, kill one of the chats and restart it until you get the error.

[2019-01-22T15:20:02Z ERROR libp2p_yamux] connection error: decode error: i/o error: I/O error: Connection reset by peer (os error 104)

I initially thought that it was an error about closing the previous connection (from before we restart the chat), but this can happen on first try even when both chat examples were closed.

This can also possibly be caused by the dialing priority system not working properly.

@tomaka tomaka added the bug label Jan 22, 2019
@tomaka
Copy link
Member Author

tomaka commented Jan 25, 2019

This may be the underlying cause of paritytech/substrate#1335

@tomaka
Copy link
Member Author

tomaka commented Mar 22, 2019

No longer happens. Probably got fixed at the same time as the simultaneous dialing.

@tomaka tomaka closed this as completed Mar 22, 2019
@ghost ghost removed the in progress label Mar 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant