did you try running it without threads? On Wed, Sep 27, 2017 at 5:26 PM, Ernesto Revilla <erevi...@tangrambpm.es> wrote:
> Dear all. > > Could anyone please lend me a hand? > > From time to time, the respawned (--reload-on-rss=450) process is blocked > and does not accept any connections. I get a "Connection timed out" error > in Nginx. > > https://github.com/unbit/uwsgi/issues/1599 > > I did already strace it and find the process and all its threads waiting > on futex. > > I haven't read the "reload code", but it's like if the forked process > inherits some other futex (we can see it with strace). > > I've been able to reproduce the behaviour using Apache Bench (ab) on a > test server. I was not able to reproduce it on Ubuntu 16.04. > > Thanks in advance. > Best regards. > > > > Ernesto Revilla > Área Técnica > TangramBPM.es > Tlf: 630 244 136 > > > > _______________________________________________ > 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
