-
Notifications
You must be signed in to change notification settings - Fork 224
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
Too many open files #366
Comments
This is due to the fact that the network has grown about 20x in the past few weeks to ~500 nodes, and we still have one centralized component left over from when we had 6 nodes - the directory server that provides an overview of what nodes exist. The directory server has now been merged into our new (decentralized) validators and we're working towards a release probably end of this week or beginning of next week which will start to fix this problem. The other part of the problem here is that a lot of people are running nodes which are misconfigured. So your node is probably trying to connect to other nodes which show up in the directory listing, but which are not actually accepting mixnet traffic Maybe they're firewalled off, maybe they node operator reported the wrong IP address during node init. This will be completely fixed over the next few weeks as we are currently building a system of mixnode staking, to reward people running properly configured nodes and penalize node operators with misconfigured nodes. Nodes that don't mix will be knocked out of the network as people won't stake on them, and the network should then only rarely have nodes that don't work. |
This is more a system configuration/Unix issue if I understand it correctly. Can be solved with I had the same issue, node was not accessible from the outside although it was still mixing somehow. |
Yeah you would see this kind of behaviour - previously established connections would continue to function, but new connections would be disallowed by the operating system. The new 0.9.1 release (out today) has fixes for ulimit-related networking problems. People should also set their default ulimits higher as noted at https://nymtech.net/docs/run-nym-nodes/mixnodes/ in order to stop the "too many connections" error and resume normal service. |
version: Nym 0.8.1
system: Ubuntu 18.04
running precompiled bin with systemd
log file show after few days:
failed to send presence - reqwest::Error { kind: Request, url: "https://directory.nymtech.net/api/presence/mixnodes", source: hyper::Error(Connect, ConnectError("dns error", Os { code: 24, kind: Other, message: "Too many open files" })) }
mixing is still working but dashboard.nymtech.net do not show node anymore
after restart node is again show on site
The text was updated successfully, but these errors were encountered: