Nixpkgs: caddy: WARNING: File descriptor limit 1024 is too low for production servers. At least 8192 is recommended. Fix with "ulimit -n 8192".

[davidak]

Issue description

set ulimit -n 8192 for caddy user, if possible in systemd service

Steps to reproduce

run caddy with NixOS module

Technical details

• System: NixOS 16.09.1623.74f24c7 (Flounder)
• Nix version: 1.11.6
• Nixpkgs version: 16.09.1623.74f24c7

[joachifm]

Per systemd.exec(5), this sounds like a job for LimitNOFILE.

[grahamc]

I wonder where the balance lays of applying tuning to services by default vs. leaving it up to the user. Example, this could be easily tuned by the user via systemd.services.caddy.serviceConfig.LimitNOFILE = 8192; (for example.) That said, if the 8192 option really is a widely deployed default, perhaps it is appropriate to use it by default.

[davidak]

@grahamc sure, but in this case i think it is not optional. We should package the software so it is usable in production.

[grahamc]

Makes sense to me. Is this a patch you're willing to implement yourself, along the lines of using LimitNOFILE? Note: It would live in the serviceConfig and not unitConfig (I corrected my previous comment.)

[davidak]

@grahamc yes, i will do it.

[xay216216]

how to deal with it?

[davidak]

@xay216216 the issue should be fixed. do you still have any problem with caddy and file descriptor limit?

[eszeus]

Hello ;)

still getting the ulimit -n 8192 WARNING when starting caddy with rocket.chat-server.

How can I fix this? >-<

thanks!

[FRidh]

@eszeus do you still have this issue? If so, which nixpkgs version?

[stale[bot]]

Thank you for your contributions.

This has been automatically marked as stale because it has had no activity for 180 days.

If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.

Here are suggestions that might help resolve this more quickly:

1. Search for maintainers and people that previously touched the related code and @ mention them in a comment.
2. Ask on the NixOS Discourse.
3. Ask on the #nixos channel on irc.freenode.net.