-
Notifications
You must be signed in to change notification settings - Fork 11.1k
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
How to increase file descriptors in Caddy service within Snap? #6979
Comments
Currently not possible to make persist between updates. You found the solution I would have suggested for short term. However I don't think this warning is critical with just rocket.chat behind caddy. I've added it to the short term roadmap to get this addressed though. |
Thank you! |
You should be able to do this:
|
Your solution work fine! tnx |
Beware that doing this might go away with snap updates. As I know snap does generate the unit file. Maybe it doesn’t touch the folder but beware just in case |
This seems to be the relevant code (also see around line 394). It does not seem to touch the directories... |
👍 agreed! Looks like a good workaround that isn’t currently in risk of overwrite. They might change it in the future though. So would still recommend to beware. |
@geekgonecrazy @LuluGO has this been fixed by #12351 ? or is this still relevant? |
Still relevant. We added support to set environment variables for Rocket.chat primarily as well as a few config things in that PR. So this is still something we need to look at |
Rocket.Chat Version: 0.55.1
Running Instances: 1
DB Replicaset OpLog: Enabled
Node Version: v4.8.0
On startup of caddy service I get:
WARNING: File descriptor limit 1024 is too low for production servers. At least 8192 is recommended. Fix with "ulimit -n 8192
I can modify /etc/systemd/system/snap.rocketchat-server.rocketchat-caddy.service with LimitNOFILE=8192 but I'm assuming that's not recommended.
Can someone please advise what the proper way to increase file descriptors is within the snap?
The text was updated successfully, but these errors were encountered: