Switching to logto did not resolve the issue. With further experimentation I've found that removing lazy mode does, but that opens a separate problem for me.
I have a python application running under uWSGI 0.9.9.1 under emperor mode. The application fails to respond after its config file is touched to trigger an application reload. If I touch a config file I get the following in the logs: touch emperor.ini Wed Sep 7 22:40:56 2011 - received message 1 from emperor ...gracefully killing workers... Gracefully killing worker 1 (pid: 3224)... Respawned uWSGI worker 1 (new pid: 3250) added /var/www/ERP/Application/ to pythonpath. mountpoint already configured. skip. <request from browser> DAMN ! worker 1 (pid: 3250) died :( trying respawn ... Respawned uWSGI worker 1 (new pid: 3251) added /var/www/ERP/Application/ to pythonpath. mountpoint already configured. skip. The config setup is available at https://gist.github.com/1202034 Do not daemonize in emperor mode. Use logto instead of daemonize -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
