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
[Bug]: too many open files #298
Comments
Yeah, so this will likely need a ulimit change. Not sure exactly how you're running the container but updating the ulimit at runtime would work. I actually didn't remember that I had set this on my own container that I'm running. I'm using |
Added ulimits to run examples and compose; fixes #298
Thank you for your quick reply and raising the ulimit. I think the docker default setting is still only 1024, which apparently isn't enough for today's applications. |
See mbentley/docker-omada-controller#298 for more info; example of issues Signed-off-by: Matt Bentley <mbentley@mbentley.net>
Updated ulimit on Unraid template that user may have been using to match @mbentley original suggestions in start up doc. This is what Unraid template looks like if interested: |
Thank you @benhedrington! |
Controller Version
v5.9.31
Describe the Bug
Every time I start the container, I get the following error and the container changes status to unhealthy.
ERROR [main] [] c.t.s.o.s.t.DeviceConnectorSeverTask(): Failed to start up net server because of
java.lang.IllegalStateException: failed to create a child event loop
Caused by: io.netty.channel.ChannelException: timerfd_create() failed: Too many open files
The controller is working, the website is working, I can adopt devices but I can't download firmware updates and this error message is filling up my logs.
Expected Behavior
I don't know if it's an issue with the container image, the omada software or the docker configuration, but it doesn't look ok.
I'm using standard settings like with every other container, and never had this problem before.
Steps to Reproduce
How You're Launching the Container
Container Logs
Additional Context
#docker inspect $container
The text was updated successfully, but these errors were encountered: