> > On Jun 13, 2012, at 9:26 AM, Roberto De Ioris wrote: >> I think i have answered some hours ago on the pyramid/pylons list. >> Are you sure you have not enabled some memory constraint ? >> >> You have not reported the uWSGI configuration, can you post it ? > > > Oh thank you for posting there. I see that message now. > > I spawn uwsgi like this ( i migrated everything from [uwsgi] section to > command line so i could test different flags faster ) > > uwsgi \ > --ini-paste-logged > /webserver/sites/MyApp/tags/current-production/web-pylons/MyApp/development.ini > \ > --socket /tmp/pyramid_myapp.sock \ > --master true \ > --processes 1 \ > --daemonize /var/log/uwsgi/pyramid_myapp-uwsgi.log \ > --pidfile /tmp/pyramid_myapp.pid \ > --virtualenv /webserver/environments/myapp-2.7/ \ > --uid jvanasco \ > --socket-timeout 20 \ > --http-timeout 20 > > there don't seem to be any memory limits in place, and this happens > getting a url of any size ( i tried ones that just have "1" , and others > that are 300k of html ). > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >
Do you redefine/use SIGUSR1 in your app ? The worker is killed by the delivery of SIGUSR1, and this is not triggered by uWSGI -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
