Hey Drookie,
Can you let me know how you solved this issue?
We are facing a similar issue which results in 502 gateway error and I'm not
able to find a solution for it.
Below is the error log from /var/log/nginx/error.log
2018/03/22 01:34:49 [error] 8779#0: *13133 no live upstreams while
We have json parsing data in between via api's. Anybody here to advise???
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,269577,272345#msg-272345
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Oh, solved. Upstreams do respond with 500.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,269577,269584#msg-269584
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
(yup, it's still the author of the original post, but my other browser just
remembers another set of credentials).
If I increase verbosity of the error_log, I'm seeing additional messages in
log, like
upstream server temporarily disabled while reading response header from
but this message
Hi.
I've set up a multiple upstream configuration with nginx as a load balancer.
And yup, I'm getting 'no live upstreams' in the error log. Like in 1-3% of
requests. And yes, I know how this works: nginx is marking a backend in an
upstream as dead when he receives an error from it, and these
