I may be out of line here, but the problem may lie in the fact that if you want to start a subprocess usually subprocess.call uses a thread to communicate with it..... uwsgi doesn't allow to spawn your own threads as long as you don't supply the --enable-threads parameter.
PS: spawning processes from a web-app poses always a lot of problems (concurrency, pipes, stderrs, inherited socket, and so on). Be sure of what you're doing. Il giorno martedì 15 gennaio 2013 06:30:14 UTC+1, Richard Penman ha scritto: > > hello, > > I set up a uwsgi / nginx server using > the setup-web2py-nginx-uwsgi-ubuntu.sh script. > However I find when the app tries to start a sub-process I get this error: > > Fatal Python error: Couldn't create autoTLSkey mapping > > I read around and apparently this can happen when lack of memory. > > Do you see any problems with these uwsgi settings: > <uwsgi> > <socket>/tmp/web2py.socket</socket> > <pythonpath>/var/www/web2py/</pythonpath> > <mount>/=wsgihandler:application</mount> > <master/> > <processes>4</processes> > <harakiri>60</harakiri> > <reload-mercy>8</reload-mercy> > <cpu-affinity>1</cpu-affinity> > <stats>/tmp/stats.socket</stats> > <max-requests>2000</max-requests> > <limit-as>512</limit-as> > <reload-on-as>256</reload-on-as> > <reload-on-rss>192</reload-on-rss> > <uid>www-data</uid> > <gid>www-data</gid> > <cron>0 0 -1 -1 -1 python /var/www/web2py/web2py.py -Q -S welcome -M > -R scripts/sessions2trash.py -A -o</cron> > <no-orphans/> > </uwsgi> > --
