I'm experiencing a bug in the vacuum option with socket/pid files under Upstart on Ubuntu 11.10. Stopping uwsgi via Upstart correctly cleans up the socket and pid files created by workers. If I issue the Upstart restart command to uwsgi the socket and pid files are removed and never recreated.
I experience this with both 1.0.3 and the latest tip. It worked correctly under 0.9.8.6. Upstart config file: description "uWSGI Emperor" start on runlevel [2345] stop on runlevel [!2345] respawn env BINPATH=/usr/sbin/uwsgi env DIR=/var/run/uwsgi env USER=web env GROUP=web env PERMS=0755 pre-start script mkdir $DIR || true chmod $PERMS $DIR || true chown $USER:$GROUP $DIR || true end script exec $BINPATH --emperor "/var/www/*/Application/emperor.ini" --binary-path $BINPATH --logto /var/log/uwsgi.log --uid web --gid web ----------------------------- uwsgi config file: [uwsgi] lazy = true master = true processes = 2 buffer-size = 3200 pythonpath = /var/www/Portal-Site/Application virtualenv = /var/www/Portal-Site/Environment/ log-syslog = PORTALUWSGI pidfile2 = /var/run/uwsgi/portal.pid socket = /tmp/uwsgi-portal.sock chmod-socket = 660 vacuum = true uid = web gid = web wsgi-file = /var/www/Portal-Site/Application/app.wsgi Thank you Brad Wells _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
