atom feed11 messages in ru.sysoev.nginxRe: Issue with upstream
FromSent OnAttachments
Phil BayfieldNov 16, 2010 5:16 am 
Phil BayfieldNov 16, 2010 6:27 am 
Maxim DouninNov 16, 2010 6:48 am.txt
Phil BayfieldNov 16, 2010 7:01 am 
Maxim DouninNov 16, 2010 10:24 am 
António P. P. AlmeidaNov 16, 2010 10:31 am 
Maxim DouninNov 16, 2010 11:01 am 
Phil BayfieldNov 16, 2010 12:14 pm 
Maxim DouninNov 16, 2010 12:32 pm 
Phil BayfieldNov 17, 2010 4:36 am 
Maxim DouninJan 5, 2011 11:59 pm.txt
Subject:Re: Issue with upstream
From:Phil Bayfield (ph@techlightenment.com)
Date:Nov 16, 2010 7:01:23 am
List:ru.sysoev.nginx

I had actually prefixed upstream and localhost 000 and everything else 100 to force them to load in the correct order. On 1 particular domain it would throw that error unless it was loaded last, hence just giving it a prefix 101 solved the issue. Bit strange!

On 16 November 2010 14:49, Maxim Dounin <mdou@mdounin.ru> wrote:

Hello!

On Tue, Nov 16, 2010 at 01:16:25PM +0000, Phil Bayfield wrote:

I'm having some problems configuring upstream servers with localhost backup (error page)

upstream backend1 { server 1.2.3.4; server 2.3.4.5; server localhost backup; }

upstream backend2 { server 3.4.5.6; server 4.5.6.7; }

Works, but:

upstream backend1 { server 1.2.3.4; server 2.3.4.5; server localhost backup; }

upstream backend2 { server 3.4.5.6; server 4.5.6.7; server localhost backup; }

Causes:

Testing nginx configuration: [emerg]: invalid parameter "backup"

Is this a bug?

Most likely you used backend2 somewhere in proxy_pass before defining upstream backend2. This is not generally supported and and shouldn't be allowed, but happens to "work" (though with several unexpected side effects) for now.

Attached patch makes sure such configuration like

server { location / { proxy_pass backend; ... } ... }

upstream backend { ... }

will generate "upstream "backend" defined too late" error during configuration parsing.

*Social Media Developer positions available. See http://bit.ly/afmRt4 for info*