Maxim Dounin
September 29, 2021 01:22PM
Hello!

On Wed, Sep 29, 2021 at 10:41:20AM -0400, rjvbzeoibvpzie wrote:

> You are right, those lines are logged (i've forced upstreams to fail by
> stopping them).
>
> But i can't see such problem using "proxy_pass http://127.0.0.1:81" instead
> of "proxy_pass http://http_backend" (no more 502 errors).
>
> Strange...

That's because max_fails/fail_timeout are not used when only one
server is available in an upstream group, and "no live upstreams"
errors cannot happen.

--
Maxim Dounin
http://mdounin.ru/
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

Nginx upstream return name instead of server ip

rjvbzeoibvpzie September 29, 2021 09:20AM

Re: Nginx upstream return name instead of server ip

Maxim Dounin September 29, 2021 09:30AM

Re: Nginx upstream return name instead of server ip

rjvbzeoibvpzie September 29, 2021 09:43AM

Re: Nginx upstream return name instead of server ip

Maxim Dounin September 29, 2021 10:02AM

Re: Nginx upstream return name instead of server ip

rjvbzeoibvpzie September 29, 2021 10:41AM

Re: Nginx upstream return name instead of server ip

Maxim Dounin September 29, 2021 01:22PM

Re: Nginx upstream return name instead of server ip

rjvbzeoibvpzie September 29, 2021 01:34PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 281
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready