uWSGI Emperor 不会通过触摸 .ini 文件重新加载 Vassal

Question

I have multiple uWSGI vassals, all monitored by uwsgi emperor. I update the code for my app (Django) and I want the emperor to perform a clean reload of one of the vassals. To do that I

touch vassal-foo.ini

In the logs I see [emperor] reload the uwsgi instance vassal-foo.ini . This sounds promising, but the app is not reloaded. It continues to run the old version. Checking the process (PID) startup time, indeed, it has not been restarted.

Any hints what might cause this? Few things that might be uncommon:

• Neither the emperor nor the vassal run in master mode
• Emperor was installed with pip and runs under initctl
• kill -9 -ing the vassal triggers a correct reload (obviously)
• I use symlinks
• I have a secondary thread inside my python app ( threading.Thread(target).start() ) running with daemon=True

Things I tried and did not work:

• Run the process without any additional threads (remove threading.Thread(target).start() )
• Touching with touch --no-dereference vassal-foo.ini
• Starting emperor with --emperor-nofollow

vassal-foo.ini:

master         = false
processes      = 1
thunder-lock   = true
enable-threads = true
socket         = /tmp/%n.sock
chmod-socket    = 666
vacuum          = true

Emperor:

exec /tmp/uwsgi --emperor /tmp/configs/uwsgi/ --die-on-term --uid me --gid me --logto /tmp/logs/uwsgi-emperor.log

uWSGI version

$ uwsgi --version
2.0.17

Answer 1

The problem is that your vassal not run in master mode.

All the ways uwsgi reload a requires master process.

In emperor mode, when you touch the ini, the emperor send a sighup to the vassal and record in the log that the vassal is reload. But if the vassal doesn't has a master it just ignore the sighup. So that is why you see reload in log but nothing happened.