> I cannot totally rule out the possibility that my processes are shutting
> down less cleanly that they should (maybe a race condition?), but in
> testing
> they seem to be shutting down ok, and so they should have finished sending
> the response. Also, may this actually be caused by nginx "losing"
> connection
> with the socket - receiving 0 bytes, rather than actually getting a
> partial
> response?

Yes, this may (and probably is) the cause.

> Is there some nginx config param I can tweak to try in order to get rid of
> those 502's ?? or either any suggestion on somewhere else to look for
> problems and solutions?

After such error nginx tries another backend in upstream {}, so this
shouldn't be an issue unless you restart all backends at the same time.

Best regards,
Piotr Sikora < piotr.sikora@frickle.com >


_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx