bdmesh Wrote:
-------------------------------------------------------
> I did find the following logs (dns name and ip addresses modified):
> 2015/12/15 03:40:13 [warn] 10#0: *32460 upstream server temporarily
> disabled while connecting to upstream, client: 10.0.1.127, server: ,
This indicates a backend is causing this, not nginx, it may be going down (and marked as down) for some reason. There are a lot of reasons why this is happening still including a dns issue somewhere. Maybe curl-ing the backend rapidly may show something.
-------------------------------------------------------
> I did find the following logs (dns name and ip addresses modified):
> 2015/12/15 03:40:13 [warn] 10#0: *32460 upstream server temporarily
> disabled while connecting to upstream, client: 10.0.1.127, server: ,
This indicates a backend is causing this, not nginx, it may be going down (and marked as down) for some reason. There are a lot of reasons why this is happening still including a dns issue somewhere. Maybe curl-ing the backend rapidly may show something.