> Hi, > I'm using uwsgi 1.9.20 on Ubuntu 12.04 in Emperor mode to manage some > web apps (Pyramid and Pylons) > > uwsgi is started with > > /usr/local/bin/uwsgi --emperor /etc/uwsgi.d/*.ini > > Each .ini as the following structure > > [uwsgi] > instance_dir = /var/www/appname > chdir = %(instance_dir) > master = true > http = 127.0.0.1:$PORT > post-buffering = 1024 > processes = 3 > cheaper = 1 > lazy = true > reload-on-rss = 128 > uid = uid > gid = gid > vacuum = true > no-orphan = true > single-interpreter = true > pyhome = /opt/virtualenvs/application_virtualenv > logto = /var/log/uwsgi/appname.log > log-5xx = true > ini-paste-logged = /var/www/appname/production.ini > touch-reload = /var/www/appname/production.ini > > Everything is working well except for app reloading: if I update files > and touch the .ini, all apps stop to work, and I have to kill them > > A similar scenario on another server with uWsgi 1.4 works as expected, > so maybe I'm missing something with the new version of uwsgi. Any hint? > > Thank you > > -- > Andrea Cappelli >
Change lazy to lazy-apps, the first one simply reload workers on "reload message" from the Emperor, while you need to reload the whole instance -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
