On Tue, Dec 22, 2009 at 4:29 PM, Piotr Sikora <piotr.sikora@frickle.com>wrote:

>
> 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.
>
>
Currently I have a single backend with n processes listening on the same
unix socket, in order to use multiple ones I may consider switching to
something like mongrel_cluster, but I fear that they would probably still be
terminated at the same time.

I'm going to give it a try anyway, thanks!
_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx