Supervisor open file limit won't change when using Chef

Question

I am modifying /etc/security/limits.conf on the machine, and then installing Supervisor in a Chef recipe. After the recipe run finishes, if I run cat /proc/<process id>/limits I see:

Limit                     Soft Limit           Hard Limit           Units     
Max cpu time              unlimited            unlimited            seconds   
Max open files            1024                 4096                 files

If I log into the machine and run service supervisor restart, the max open files is then set correctly. However, if I run this command in the recipe (right after installing supervisor, at the very end of the recipe, anything) the limit does not change. It is not until I log in and manually run that command that the limit changes.

How can I get the open file limit for supervisor to change using the chef recipe? Operating system is Ubuntu 12.04.

Mathews

Answer 1

To any weary googlers: you might be looking for the minfds setting in the supervisor config. This setting seems to take effect for both the supervisord process as well as the children. I had a number of other strategies, including launching a shell script that set the limits before executing the actual program, but this was the only thing that worked.

Benioff

minfds only defines the minimum of file descriptors the supervisord process has access to. If less then the specified value, supervisord will not startup. it will not set the allowed files to open for the children ... – Mezereon

so in the config file for the program set minfds = 100000 or what not? – Crush

@Mezereon "A call to setrlimit will be made to attempt to raise the soft and hard limits of the supervisord process to satisfy minfds. The hard limit may only be raised if supervisord is run as root." – Rosa

Stack is amazing, you are amazing, the comments are amazing ! – Multitude

don't forget to sudo service supervisor restart – Hypoplasia

Answer 2

Supervisor relies at its service config. So to raise limit you need to do it at service level.

This scenario works perfect for ubuntu 20.04

1. systemctl edit supervisor.service

2. Enter and save

[Service]
LimitNOFILE=20000

3. systemctl daemon-reload

4. systemctl restart supervisor

Then, just to check, cat /proc/pgrep supervisor/limits | grep open

You will se something like

Max open files            20000                20000                files

It works :)

Monteria

Answer 3

I did not test on my pc because I cannot stop supervisord now. But if you reorder the /etc/rc directory?

# find /etc/rc* -iname "*super*"
/etc/rc0.d/K01supervisor
/etc/rc1.d/K01supervisor
/etc/rc2.d/S16supervisor
/etc/rc3.d/S16supervisor
/etc/rc4.d/S16supervisor
/etc/rc5.d/S16supervisor
/etc/rc6.d/K01supervisor

I have the same problem Supervisord and ulimit to java app

Imponderabilia

Answer 4

The implementation of supervisor is such that a process can be started as a non-root user, with more privileges than that user is allowed - bypassing pam, limits.conf, etc. So I doubt that this problem will be fixed. Have a look at https://github.com/Supervisor/supervisor/pull/229

Frieda