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

Systemd limits issue #225

Closed
eliranbz opened this issue Feb 8, 2016 · 0 comments
Closed

Systemd limits issue #225

eliranbz opened this issue Feb 8, 2016 · 0 comments

Comments

@eliranbz
Copy link
Contributor

eliranbz commented Feb 8, 2016

Under systemd, the nofile and nproc should be set within the consul.service in order for them to take effect.
Under heavy installations, there are multiple errors such as:

[ERR] memberlist: Error accepting TCP connection: accept tcp [::]:8301: accept4: too many open files
[ERR] consul.rpc: failed to accept RPC conn: accept tcp [::]:8300: accept4: too many open files
[ERR] memberlist: Error accepting TCP connection: accept tcp [::]:8301: accept4: too many open files
[ERR] consul.rpc: failed to accept RPC conn: accept tcp [::]:8300: accept4: too many open files
[ERR] memberlist: Error accepting TCP connection: accept tcp [::]:8302: accept4: too many open files
[ERR] memberlist: Error accepting TCP connection: accept tcp [::]:8302: accept4: too many open files [ERR] memberlist: Error accepting TCP connection: accept tcp [::]:8301: accept4: too many open files
[ERR] memberlist: Error accepting TCP connection: accept tcp [::]:8301: accept4: too many open files
[ERR] consul.rpc: failed to accept RPC conn: accept tcp [::]:8300: accept4: too many open files

It's worth mentioning that systemd ignores the global/user limits configuration such as sysctl.conf and limits.conf
I think we should add this to the service, will open a pull request

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants