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

[Windows] Presence notification fill OS socket queue #170

Closed
jstuczyn opened this issue Apr 2, 2020 · 3 comments · Fixed by #226
Closed

[Windows] Presence notification fill OS socket queue #170

jstuczyn opened this issue Apr 2, 2020 · 3 comments · Fixed by #226
Milestone

Comments

@jstuczyn
Copy link
Contributor

jstuczyn commented Apr 2, 2020

If you let your mixnode / provider running on Windows, eventually it will start failing to send presence with following errors:
2020-04-02T17:05:20.840 ERROR nym_sfw_provider::provider::presence > failed to send presence - Error(Hyper(Error(Connect, Os { code: 10055, kind: Other, message: "An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full." })), "http://localhost:8080/api/presence/mixproviders")

On top of that, establishing any other TCP connections on the host machine might fail until the mixnode process is killed.

A possible solution would be to perhaps introduce re-usable connections between nodes and the presence server.

@jstuczyn jstuczyn added this to Backlog in Core systems via automation Apr 2, 2020
@futurechimp
Copy link
Contributor

Somebody is eventually going to join the testnet with a Windows machine. Should we make Windows mixnodes commit suicide until this problem is figured out? The last thing we want is packets going missing sporadically because someone is running an unsupported OS? I would put Windows in that category for the moment, I consider Linux to be our only real supported OS for running mixnodes at the moment.

@jstuczyn
Copy link
Contributor Author

jstuczyn commented May 4, 2020

Seems to be related to seanmonstar/reqwest#284

@jstuczyn
Copy link
Contributor Author

jstuczyn commented May 4, 2020

Also seems to be fixed in reqwest 0.10

Core systems automation moved this from Backlog to Done May 12, 2020
@futurechimp futurechimp added this to the 0.7.0 milestone May 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Core systems
  
Done
Development

Successfully merging a pull request may close this issue.

2 participants