Issue with upstream

Phil Bayfield phil at techlightenment.com
Tue Nov 16 17:27:38 MSK 2010


Problem solved, strangely enough the order in which my servers are loaded
seams to trigger this error, it's actually nothing to do with the upstream
settings but forcing one of my server configs to be loaded last resolved the
issue.

On 16 November 2010 13:16, Phil Bayfield <phil at techlightenment.com> 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?
>
> Cheers
> Phil.
>



-- 
Phil Bayfield
Developer
Techlightenment

3.08 Tea Building | 56 Shoreditch High St | London | E1 6JJ
t:   +44 (0) 8445814444
m: +44 (0) 7711117117
e:  phil at techlightenment.com
www.techlightenment.com

*Social Media Developer positions available. See http://bit.ly/afmRt4 for
info*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nginx.org/pipermail/nginx/attachments/20101116/8b7e2473/attachment.html>


More information about the nginx mailing list