supervisor que detiene los procesos secundarios

One of the problems, I face with supervisord is that when I have a command which in turn spawns another process, supervisord is not able to kill it.

For example I have a java process which when runs normally is like

 $ zkServer.sh start-foreground
 $ ps -eaf | grep zk
 user 30404 28280  0 09:21 pts/2    00:00:00 bash zkServer.sh start-foreground
 user 30413 30404 76 09:21 pts/2    00:00:10 java -Dzookeeper.something..something

The supervisord config file looks like:

[program:zookeeper]
command=zkServer.sh start-foreground
autorestart=true
stopsignal=KILL

These kind of processes which have multiple childs are not well handled by supervisord when it comes to stopping them from supervisorctl. So when I run this from the supervisord and try to stop it from supervisorctl, only the top level process gets killed but not the actual java process.

preguntado el 01 de febrero de 12 a las 04:02

Tengo entendido que el systemd init-replacement's use of cgroups allows for reliably tracking child processes. It might be suitable for your needs. -

6 Respuestas

The same problem was encountered by Rick Hanlon II here: https://coderwall.com/p/4tcw7w

Optión stopasgroup=true should be set in the program section for supervisord to stop not only the parent process but also the child processes.

The example is given as:

[program:some_django]
 command=python manage.py runserver
 directory=/dir/to/app
 stopasgroup=true

Also, have in mind that you may have an older package of supervisord that does not have "stopasgroup" functionality. I tried these Debian packages on Raspberry Pi:

  • supervisor_3.0a8 does not work.
  • supervisor_3.0b2-1 works as expected.

Respondido el 13 de diciembre de 13 a las 16:12

Also note that supervisord doesn't take configuration changes automatically. You'll need to run supervisorctl update to apply changes to your configuration, or restart the supervisord process. - jjmontes

This should really be the default option. - Shubham Chaudhary

This worked perfectly for me with supervisor 3.2. Thanks. - Cerin

Doing the following early in the main bash script called by supervisord fixed the problem for me:

trap "kill -- -$$" EXIT

This kills the entire process group when the main script exits, such as when it is killed by supervisord.

respondido 13 mar '14, 01:03

A feature was recently added to supervisord to send SIGKILL to the whole process group. It's in gitHub but not officially released yet.

If the process id is available in a file, you can use the pid-proxy program

Respondido 01 Feb 12, 23:02

try this supervisor program config:

stopasgroup=true
killasgroup=true
stopsignal=INT

Respondido el 28 de junio de 18 a las 09:06

The following article has an in-depth discussion of the problem:

http://veithen.github.io/2014/11/16/sigterm-propagation.html

Respondido el 11 de enero de 15 a las 22:01

exec ... solved it for me. The first option in the article. Thanks - Alon Catz

Thank you for teaching how to catch the fish instead of supplying it ;) - Gökçer Gökdal

You can also use priorities in /conf.d/your-configuration.conf file. For example, if you want to run zookeeper first and then kafka you can specify two programs.

Lower priority means that the program starts first and stops last.

respondido 05 nov., 16:05

No es la respuesta que estás buscando? Examinar otras preguntas etiquetadas or haz tu propia pregunta.