> Hi, > > This is what I have in the script which starts uwsgi - > UWSGI_EMPEROR_MODE=true > UWSGI_VASSALS="/etc/uwsgi/" > UWSGI_OPTIONS=" --enable-threads --logto /var/log/uwsgi/uwsgi.log" > lockfile=/var/lock/subsys/uwsgi > if [ "$UWSGI_EMPEROR_MODE" = "true" ] ; then > UWSGI_OPTIONS="$UWSGI_OPTIONS --emperor $UWSGI_VASSALS" > fi > > case "$1" in > start) > echo -n "Starting uWSGI " > daemon $UWSGI_BIN $UWSGI_OPTIONS & > > > In the configuration file I have > (python2.7)[root@MyCentOS ~]# more /etc/uwsgi/web2py.ini > [uwsgi] > > socket = /var/www/web2py/logs/%n.socket > pythonpath = /var/www/web2py/ > mount = /=wsgihandler:application > processes = 1 > master = true > harakiri = 90 > reload-mercy = 80 > cpu-affinity = 1 > stats = /tmp/%n.stats.socket > max-requests = 2000 > limit-as = 512 > reload-on-as = 256 > reload-on-rss = 192 > uid = nginx > gid = nginx > no-orphans = true > chmod-socket = 666 > > But I see the following entries in the logfile - > > "*** Python threads support is disabled. You can enable it with > --enable-threads ***" > > Why is the enable-threads option not working? > > >
It is a common error (even if i do not know why) thinking that options added to the Emperor are inherited to vassals. It is not true, to automatically add options to each vassals there are specific options. Just add enable-threads = true in each vassal. Bt the way, adding --enable-threads in the Emperor is useless (unless you spawn workers in the Emperor instance) -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
