> Sure thing. I thought the last ones were current, but I guess things > changed in between. Also, I thought threads were disabled, but apparently > not. > > The emperor is managed with upstart on Ubuntu 8.04 LTS. File: > /etc/event.d/uwsgi > > # Emperor uWSGI script >> description "uWSGI Emperor" >> start on runlevel [2345] >> stop on runlevel [06] > > respawn >> exec uwsgi --master --die-on-term --emperor /etc/uwsgi/sites/ >> --logto=/var/log/uwsgi/uwsgi.log --log-date > > > File: /etc/sites/wol.ini > > [uwsgi] >> socket = 0.0.0.0:7654 >> socket = 0.0.0.0:7655 >> socket = 0.0.0.0:7656 >> stats = 0.0.0.0:7554 >> listen = 1000 >> protocol = http >> env = PYWOL_VOID_STDOUT=yes >> env = DJANGO_SETTINGS_MODULE=wol.settings >> virtualenv = /var/python/wol-env >> chdir = /var/python/wol/src/wol >> pythonpath = /var/python/wol/src >> module = django.core.handlers.wsgi:WSGIHandler() >> touch-reload = /var/python/wol/django.wsgi >> processes = 40 >> buffer-size = 65536 >> enable-threads = true >> max-requests = 5000 >> uid = www-data >> gid = www-data > > > > Django.wsgi isn't really used anymore, still exists for the backup Apache > 2 > mod_wsgi config and as the thing to touch after a code upgrade. uwsgi > works > tons better than mod_wsgi for us anyway, as the latter just stops > accepting > requests once in a while with everything stuck at unix socket accept > between Apache and the worker; I gave up on debugging that. > > >
The only "uncommon" thing is the usage of multiple sockets (it should not be a problem, but who knows... :P) Can you paste your webserver config too ? (maybe there is something breaking graceful reload there) -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
