# Nginx fastcgi\_next\_upstream off doesn't work

**URL:** <https://www.ruby-forum.com/t/nginx-fastcgi-next-upstream-off-doesnt-work/237784>\
**Category:** NGINX\
**Created:** [November 29, 2013, 12:51pm UTC](https://www.ruby-forum.com/t/nginx-fastcgi-next-upstream-off-doesnt-work/237784 "2013-11-29T12:51:27Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![musicdenotation](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/ea666f/32.png) [@musicdenotation](https://www.ruby-forum.com/u/musicdenotation)\
**Post date:** [November 29, 2013, 12:51pm UTC](https://www.ruby-forum.com/t/nginx-fastcgi-next-upstream-off-doesnt-work/237784/1 "2013-11-29T12:51:27Z")

</div>

nginx/1.5.4  
location / {  
…  
fastcgi\_pass bg;  
fastcgi\_next\_upstream off;  
…  
}

upstream bg {

```
server unix:/tmp/dsp.1.sock;
server unix:/tmp/dsp.2.sock;
server unix:/tmp/dsp.3.sock;
server unix:/tmp/dsp.4.sock;
server unix:/tmp/dsp.5.sock;
server unix:/tmp/dsp.6.sock;
server unix:/tmp/dsp.7.sock;
server unix:/tmp/dsp.8.sock;
server unix:/tmp/dsp.9.sock;
server unix:/tmp/dsp.10.sock;
server unix:/tmp/dsp.11.sock;
server unix:/tmp/dsp.12.sock;
server unix:/tmp/dsp.13.sock;

```

}

log\_format combined-r ‘$time\_local: upstream $upstream\_addr responded  
$upstream\_status in $upstream\_response\_time ms, request status $status  
is  
in $request\_time ms’;

29/Nov/2013:13:57:51 +0400: upstream unix:/tmp/dsp.4.sock :  
unix:/tmp/dsp.9.sock responded 504 : 504 in 0.148 : 0.050 ms, request  
status 504 is in 0.198 ms

So nginx still pass request to next upstream dsp.4 -\> dsp.9

What can be wrong with this config?

Thanks,  
OK

---

<div class="post-metadata">

**Author:** ![Oleg\_VSKhrustov](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/o/85f322/32.png) [@Oleg\_VSKhrustov](https://www.ruby-forum.com/u/Oleg_VSKhrustov)\
**Post date:** [November 29, 2013, 2:06pm UTC](https://www.ruby-forum.com/t/nginx-fastcgi-next-upstream-off-doesnt-work/237784/2 "2013-11-29T14:06:51Z")

</div>

Hello!

On Fri, Nov 29, 2013 at 03:50:52PM +0400, Oleg V. Khrustov wrote:

> ```
> server unix:/tmp/dsp.1.sock;
> server unix:/tmp/dsp.12.sock;
> 
> ```
> 
> unix:/tmp/dsp.9.sock responded 504 : 504 in 0.148 : 0.050 ms, request  
> status 504 is in 0.198 ms
> 
> So nginx still pass request to next upstream dsp.4 → dsp.9
> 
> What can be wrong with this config?

The “504 : 504” in $upstream\_status indicate that there were two  
requests to the upstream, with an internal redirect between them  
(note “:”). See here for the variable format description:

[http://nginx.org/en/docs/http/ngx\_http\_upstream\_module.html#variables](http://nginx.org/en/docs/http/ngx_http_upstream_module.html#variables)

That is, everything works as expected, you just have an error\_page  
redirection which does an additional request and confuses you.

–  
Maxim D.  
[http://nginx.org/en/donation.html](http://nginx.org/en/donation.html)

---

<div class="post-metadata">

**Author:** ![Oleg\_VSKhrustov](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/o/85f322/32.png) [@Oleg\_VSKhrustov](https://www.ruby-forum.com/u/Oleg_VSKhrustov)\
**Post date:** [November 29, 2013, 2:36pm UTC](https://www.ruby-forum.com/t/nginx-fastcgi-next-upstream-off-doesnt-work/237784/3 "2013-11-29T14:36:05Z")

</div>

Yes, you are absolutely right. Thanks again!