Got it!
Thanks.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,292491,292502#msg-292502
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
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
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...
Posted at Nginx Forum:
Hello!
On Wed, Sep 29, 2021 at 09:43:54AM -0400, rjvbzeoibvpzie wrote:
> Well, I was just assuming that no live upstreams were availbale, but this is
> not the case. At least, this is not logged (access or error).
The "no live upstreams" error is expected to be logged to the
error log at the
Well, I was just assuming that no live upstreams were availbale, but this is
not the case. At least, this is not logged (access or error).
Here are the lines from access_log i'm talking about (see the difference on
$upstream_addr):
log_format main '$remote_addr - $remote_user
Hello!
On Wed, Sep 29, 2021 at 09:20:20AM -0400, rjvbzeoibvpzie wrote:
> Here is my config:
>
> -
> upstream http_backend {
> server 127.0.0.1:81;
> server 10.1.1.2 backup;
> }
>
> server {
> ...
>
> location /http/ {
> proxy_pass http://http_backend;
> ...
