On Fri, Aug 23, 2013 at 9:43 PM, yi huang <[email protected]> wrote: > I've found my wsgi application always get harakiri-ed, I've > investigated a little by adding some logs to all the places that will > set harakiri, and i found this: > > Fri Aug 23 21:40:49 2013 - set harakiri 2 > Fri Aug 23 21:40:49 2013 - set harakiri 4 > Fri Aug 23 21:40:49 2013 - set harakiri 3 > Fri Aug 23 21:40:49 2013 - clear harakiri [4] > Fri Aug 23 21:41:00 2013 - *** HARAKIRI ON WORKER 2 (pid: 27010, try: 1) *** > ... > Fri Aug 23 21:41:01 2013 - *** HARAKIRI ON WORKER 3 (pid: 27012, try: 1) *** > ... >
I should have been more clear, I only issue one http request, there are three set harakiri on three worker process, and only one is cleared, the other two process is recycled by harakiri. > > I'm using uwsgi-1.9.14, my config is follow: > > [uwsgi] > http = 127.0.0.1:8080 > socket = 127.0.0.1:3031 > master = true > workers = 4 > gevent = 100 > gevent-monkey-patch = 1 > reload-on-as = 1024 > harakiri = 10 > wsgi = main.wsgi > virtualenv = ../env > post-buffering = 8096 > py-tracebacker = /tmp/tbsocket > pidfile = /var/run/uwsgi.pid > uid = yunyue > gid = yunyue > > req-logger = file:/var/log/uwsgi/access.log > logger = file:/var/log/uwsgi/error.log > log-reopen = 1 > logdate = 1 -- http://yi-programmer.com/ _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
