> Hi, > > I'm using the emperor-on-demand setup. > Some time ago, I was not having any 502 errors from nginx on reloading. > > I have 134 vassals running under that emperor (though at a point in time, > usually about 20 is up, all the others are waiting for socket > connections). > > Recently, 502 errors started appearing for a few seconds on touching the > vassal's ini file. > > Before that, the first request was just taking a while, but not showing > any > 502 errors. > > I don't know what exactly is causing this, that might be the amount of > vassals, but it seems it's not, cause I can reproduce this on the dev > machine with only a couple of vassals. There were too many code changes, > and it's almost impossible to find a changelist, which possibly introduced > this (if it is in the python code). > > However, nothing at all about missed requests is found in the uwsgi logs. > Which makes me think the problem is somewhere within the uwsgi > integration. > > Here's the message from nginx logs. > > 2013/11/19 03:33:42 [error] 9158#0: *1337160 recv() failed (104: > Connection > reset by peer) while reading response header from upstream, client: > 144.76.72.178, server: , request: "GET ......... > > The error is only visible for a few seconds after the reload, if you > refresh the page instantly after the reload. If no requests are made at > all > after the reload, and the first request comes in e.g. 10 seconds after the > reload, there are no 502 errors. > > - uwsgi version is 1.9.18 > - config files are here https://gist.github.com/ikatson/7524404 > > What can be causing this behavior, and where can I dig to fix it? > > Also, the same happens for a much longer period of time on restarting the > emperor, though, I understand, that this probably cannot be handled. > > Thanks! > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >
Can you report the logs of a vassal when reloaded ? Generally when 502 happens on reload it means the vassal has been destroyed during reload (for some configuration/privileges problems) and the emperor suddenly restarted it. -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
