I had actually prefixed upstream and localhost 000 and everything else 100 to force them to load in the correct order.<div>On 1 particular domain it would throw that error unless it was loaded last, hence just giving it a prefix 101 solved the issue.</div>
<div>Bit strange!<br><br><div class="gmail_quote">On 16 November 2010 14:49, Maxim Dounin <span dir="ltr"><<a href="mailto:mdounin@mdounin.ru">mdounin@mdounin.ru</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hello!<br>
<div><div></div><div class="h5"><br>
On Tue, Nov 16, 2010 at 01:16:25PM +0000, Phil Bayfield wrote:<br>
<br>
> I'm having some problems configuring upstream servers with localhost backup<br>
> (error page)<br>
><br>
> upstream backend1 {<br>
> server 1.2.3.4;<br>
> server 2.3.4.5;<br>
> server localhost backup;<br>
> }<br>
><br>
> upstream backend2 {<br>
> server 3.4.5.6;<br>
> server 4.5.6.7;<br>
> }<br>
><br>
> Works, but:<br>
><br>
> upstream backend1 {<br>
> server 1.2.3.4;<br>
> server 2.3.4.5;<br>
> server localhost backup;<br>
> }<br>
><br>
> upstream backend2 {<br>
> server 3.4.5.6;<br>
> server 4.5.6.7;<br>
> server localhost backup;<br>
> }<br>
><br>
> Causes:<br>
><br>
> Testing nginx configuration: [emerg]: invalid parameter "backup"<br>
><br>
> Is this a bug?<br>
<br>
</div></div>Most likely you used backend2 somewhere in proxy_pass before<br>
defining upstream backend2. This is not generally supported and<br>
and shouldn't be allowed, but happens to "work" (though with<br>
several unexpected side effects) for now.<br>
<br>
Attached patch makes sure such configuration like<br>
<br>
server {<br>
location / {<br>
proxy_pass backend;<br>
...<br>
}<br>
...<br>
}<br>
<br>
upstream backend {<br>
...<br>
}<br>
<br>
will generate "upstream "backend" defined too late" error during<br>
configuration parsing.<br>
<font color="#888888"><br>
Maxim Dounin<br>
</font><br>_______________________________________________<br>
nginx mailing list<br>
<a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
<a href="http://nginx.org/mailman/listinfo/nginx" target="_blank">http://nginx.org/mailman/listinfo/nginx</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><span style="font-family:arial, sans-serif;font-size:13px;border-collapse:collapse">Phil Bayfield</span><div><span style="font-family:arial, sans-serif;font-size:13px;border-collapse:collapse">Developer<br>
Techlightenment<br><br>3.08 Tea Building | 56 Shoreditch High St | London | E1 6JJ<br>t: +44 (0) 8445814444<br>m: +44 (0) 7711117117<br>e: <a href="mailto:phil@techlightenment.com" target="_blank">phil@techlightenment.com</a><br>
<span style="color:blue"><a href="http://www.techlightenment.com/" style="color:rgb(6, 88, 181)" target="_blank">www.techlightenment.com</a></span></span></div><div><span style="font-family:arial, sans-serif;font-size:13px;border-collapse:collapse"><br>
</span></div><div><span style="font-family:arial, sans-serif;font-size:13px;border-collapse:collapse"><span style="font-family:'Times New Roman', serif;font-size:16px"><i>Social Media Developer positions available. See <a href="http://bit.ly/afmRt4" style="color:rgb(6, 88, 181)" target="_blank">http://bit.ly/afmRt4</a> for info</i></span></span></div>
<br>
</div>