> Hi Roberto, > > There are several signs that make me think I'm not facing client > aborts in this case: > > 1) haproxy logs mention status flags of prematurely closed > connections, and in all cases I see sH which means server never > completed the http headers. Stating the haproxy configuration > manual[1]: >
Sorry, i have re-read your first post, and i think the problem is different. If you do not see error in uwsgi log (and having disabled non-error you should see them) the problem is with the upper layer. If you do not see error in nginx log then probably the response time is so high that haproxy timed out. In this case you have to increase the number of workers (i think that a +2 should be enough for your load). Remember that flup spawn workers dinamically (so it could take down your machine ;) P.S. do not try increasing backlog queue as you can have more problems and longer response time. -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
