3 ms·
It's theoretically rock solid. In practice there are many common scenarios where uwsgi goes wrong. Here's one where a seemingly normal configuration of superv
by calpaterson 11y ago
It's theoretically rock solid. In practice there are many common scenarios where uwsgi goes wrong. Here's one where a seemingly normal configuration of supervisor and uwsgi doesn't work because uwsgi attached a special meaning to SIGTERM
https://github.com/unbit/uwsgi/issues/296 https://github.com/unbit/uwsgi/issues/296
Note that the bug is closed because it will be fixed in an as-yet unreleased version!
- teleyinex 11y agoYes, you are right. But, IMHO the solution is really simple. In your supervisor config you ony add this option and everything works as expected: stopsignal=QUIT We're using it and no problems so far. Simple!
- calpaterson 11y agoRead the thread I linked - multiple commenters say that using SIGQUIT does not solve the problem for them and eventually unbit states that he recommends using --die-on-term. You are using the wrong workaround, so if you haven't had problems yet, it could only be a matter of time. And this is only one aspect of uwsgi that is buggy/unclear
- teleyinex 11y agoThanks! I'll have a look again :-)