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. Kind regards, Chi Ho Kwok On Wed, Jan 30, 2013 at 5:19 PM, Roberto De Ioris <[email protected]> wrote: > > > On Wed, Jan 30, 2013 at 4:27 PM, Roberto De Ioris <[email protected]> > > wrote: > >> > >> > >> Are you sure you are not using some old uWSGI version ? > >> > >> What you are trying to accomplish works by about 3 years without > >> emperor, > >> and from 1 year with the Emperor. > >> > >> > > It's not that old, we're not using the ancient version from the repo, but > > we haven't kept up with the latest ones. > > > > *** Starting uWSGI 1.3 (64bit) on [Wed Jan 30 16:52:00 2013] *** > > compiled with version: 4.2.4 (Ubuntu 4.2.4-1ubuntu4) on 11 October 2012 > > 13:06:26 > > os: Linux-2.6.24-29-server #1 SMP Tue Oct 11 15:57:27 UTC 2011 > > > > > > The weird thing is that they *are* gracefully reloaded. On one hand, in > > the > > uwsgi log: > > > > *** /var/python/<site>/django.wsgi has been touched... grace them all !!! > >> *** > >> ...gracefully killing workers... > >> Gracefully killing worker 1 (pid: 22028)... > >> Gracefully killing worker 3 (pid: 22030)... > >> Gracefully killing worker 13 (pid: 1430)... > >> Gracefully killing worker 17 (pid: 30238)... > >> Gracefully killing worker 14 (pid: 1402)... > >> Gracefully killing worker 2 (pid: 22029)... > >> Gracefully killing worker 37 (pid: 1617)... > >> Gracefully killing worker 5 (pid: 22032)... > >> <snip> > >> binary reloading uWSGI... > >> chdir() to /etc/uwsgi/sites > >> closing all non-uwsgi socket fds > 2 (max_fd = 1024)... > >> found fd 3 mapped to socket 0 (0.0.0.0:7654) > >> found fd 4 mapped to socket 1 (0.0.0.0:7655) > >> found fd 5 mapped to socket 2 (0.0.0.0:7656) > >> > > three sockets inherited ? > > There is something different from the config you reported in october. > > Can you report updated full configs for both the Emperor and the vassal ? > > > -- > 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
