Thanks, Roberto, installed 2.1 How can I find out if things like this happen again, what exactly is blocking? Those stacktraces don't seem very useful. I would like to see some python-level stacktraces, but uwsgi intercepts all signals, so signal handlers registered in the app itself do not work.
On Tue, Jun 2, 2015 at 9:44 PM, Roberto De Ioris <robe...@unbit.it> wrote: > > > Hi, I need some help, > > > > this is a rare bug that is hard to reproduce, I have no idea where it > > comes > > from, and where to look at. > > > > There is a harakiri set in uwsgi.conf, but it does not help, i.e. when > > fetching URLs I get a 504 instead of harakiri restarting the process. > > > > here's all the info I collected before restarting (doing "touch > > config.ini" > > helped). > > > > uwsgi version is 2.0.8 > > https://gist.github.com/ikatson/5953d3cbcc2af2a48f11 > > > > Should I use 2.1 instead, which has per-core harakiri? > > > > Will be glad for any help, thanks! > > > > Yes, harakiri on gevent is fully reliable only in 2.1. > > Basically if a second request come in while another one is ready to block > soon, the harakiri is reset. Obviously the problem is the blocking app by > itself, but if you need to rely on harakiri you should upgrade to 2.1 > > -- > Roberto De Ioris > http://unbit.com > _______________________________________________ > uWSGI mailing list > uWSGI@lists.unbit.it > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >
_______________________________________________ uWSGI mailing list uWSGI@lists.unbit.it http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
