How to use supervisor fo start/stop uWSGI application?

Question

I use a supervisor to run uWSGI application. Why uWSGI application does not always stop after stop supervisor? supervisor config:

[program:test]
autostart = true
user=root
command=uwsgi --master --workers  5 --disable-logging --socket 127.0.0.1:8888
--module web --callable app
priority=1
redirect_stderr=true
stdout_logfile = /data/log

score 41 · Accepted Answer · answered Oct 22 '13 at 10:13

41

By default supervisor send SIGTERM on stop. SIGTERM in uWSGI means 'brutal reload'.

You have to change it to QUIT or INT:

stopsignal=QUIT

should be enough

Another approach (discouraged) is adding --die-on-term to uWSGI command line to change its default behaviour

answered Oct 22 '13 at 10:13

roberto

12,723
44
30

why it's discouraged ? – Guillaume Vincent Jan 14 '14 at 13:32
1

Because you need this option only if you use supervisor. It is better to fix supervisor's behaviour in supervisor's config. – Raz Apr 04 '14 at 11:42
2

I have little experience with either method but when I was looking for the right config to use I found a few examples of problems that were apparently only solved by using `die-on-term` eg http://stackoverflow.com/a/22213404/202168 https://github.com/unbit/uwsgi/issues/296 – Anentropic Dec 05 '14 at 13:37

Color · Answer 2 · 2015-12-28T06:58:16.153

4

project supervisor config file

add stopsignal=INT
project uwsgi config file

remove daemonize=xxx.log to disable daemon mode

edited Dec 28 '15 at 06:58

answered Dec 28 '15 at 06:52

Color

875
9
11

Great tip. With daemonize on in uwsgi, when controlled via sword i found the OS would run of memory and produce this error: [Errno 12] Cannot allocate memory – run_the_race Mar 15 '19 at 18:33

score 4 · Answer 3 · edited Apr 28 '17 at 05:27

4

If you use "processes = #" into your uwsgi configuration, you also must use "master = true". If not, supervisor only will kill one of workers.

Then:

/etc/supervisor/conf.d/app.conf

stopsignal = QUIT

/etc/uwsgi/app.ini

processes = 4
master = true

edited Apr 28 '17 at 05:27

nik_m

11,825
4
43
57

answered Jul 13 '16 at 21:46

estevo

941
11
11

I used `stopsignal = QUIT` but after stopped it in supervisorctl, some new uwsgi processes was created by pid 1. `stopsignal=INT` does the stop thing. – Kyan Nov 30 '17 at 06:59

score 1 · Answer 4 · answered Apr 24 '18 at 13:44

1

If you are running your UWSGI with master and workers you need to add in your /etc/supervisor/conf.d/app.conf file

stopasgroup=false
killasgroup=false

or else no matter what stopping uwsgi will spawn more master and so is workers.

answered Apr 24 '18 at 13:44

Kunal Mawar

11
1
3

This is the default config. I could only make the `supervisorctl restart process` work correctly by setting both options to `true`. – Maximiliano Guerra Aug 06 '20 at 15:33

How to use supervisor fo start/stop uWSGI application?

4 Answers4