Disabling threads doesn't seem to alter that behavior.
On Tue, Jun 21, 2011 at 10:09 AM, Roberto De Ioris <[email protected]> wrote: > >> I use XML to configure, it's easier for me to test with at the moment. >> >> <uwsgi> >> <vhost-host/> >> <master/> >> <gid>www-data</gid> >> <uid>www-data</uid> >> <catch-exceptions/> >> <chmod-socket/> >> <idle>600</idle> >> <max-requests>1000</max-requests> >> <processes>4</processes> >> <threads>50</threads> >> <no-orphans/> >> <enable-threads/> >> <reload-mercy>5</reload-mercy> >> <socket>/var/tmp/uwsgi.sock</socket> >> <pidfile>/var/run/uwsgi.pid</pidfile> >> <!-- <daemonize>/var/log/uwsgi.log</daemonize> --> >> <!-- <disable-logging/> --> >> <vacuum/> >> <!-- <no-default-app/> This option can return errors while an app >> is initializing. --> >> <!-- <reload-on-rss>128</reload-on-rss> Reload at 128MB of RSS >> (memory usage) --> >> </uwsgi> >> >> > > > Can you try removing <enable-threads> and <threads> ? > > It looks like something with threads is broken (about 3 bug reports in 24 > hours related to threads, so i am a bit suspicious) > -- > 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
