Forum: NGINX Server won't start AND Nginx as reverse proxy

Posted by pieter@lxnex.com (Guest)
on 2013-01-03 14:49
(Received via mailing list)
Hi guys,

I have two issues on which I can not seem to find decent help:

1- See the configuration below. If the  https://some.site.com  site is 
down,
Nginx won't start. I still want Nginx to start whether this site is down 
or
not:

server {
  listen 8000;
  location / {
    proxy_pass https://some.site.com;
  }
}


2- We have set up Nginx as a reverse proxy server to send users to a few
backend Swazoo web servers. If a particular Swazoo web server is 
currently
busy handling a request, Nginx does not reverse proxy new incoming 
requests
to one of the other Swazoo web servers and the site appears to be 
'hanging'.
 Any help on this?

Thanks!

Posted at Nginx Forum: 
http://forum.nginx.org/read.php?2,234664,234664#msg-234664
Posted by pieter@lxnex.com (Guest)
on 2013-01-24 13:31
(Received via mailing list)
Hi guys,

Concerning the first issue I had, I managed to get Nginx to now startup 
when
I reboot the system, but the only way I could get it to work was by 
adding a
sleep of a couple of seconds to the /etc/init.d/nginx startup script.

Is this acceptable practice?

Thanks,
Pieter

Posted at Nginx Forum: 
http://forum.nginx.org/read.php?2,234664,235536#msg-235536
Posted by "António P. P. Almeida" <appa@perusio.net> (Guest)
on 2013-01-24 13:56
(Received via mailing list)
On 24 Jan 2013 13h31 CET, nginx-forum@nginx.us wrote:

> Hi guys,
>
> Concerning the first issue I had, I managed to get Nginx to now
> startup when I reboot the system, but the only way I could get it to
> work was by adding a sleep of a couple of seconds to the
> /etc/init.d/nginx startup script.
>
> Is this acceptable practice?

No.

Something is wrong with your setup.
--- appa
Posted by Reinis Rozitis (Guest)
on 2013-01-24 18:28
(Received via mailing list)
> 2- Nginx does not reverse proxy new incoming requests to one of the other
> Swazoo web servers and the site appears to be 'hanging'. Any help on this?

The default proxy module timeouts are pretty high (like 60s)

http://nginx.org/en/docs/http/ngx_http_proxy_modul...
http://nginx.org/en/docs/http/ngx_http_proxy_modul...

.. so naturally if the backend doesnt respond in timely matter it can 
take
up to a minute for nginx to decide what to do next.


I would also rather than using (with dns resolve):

location / {
   proxy_pass https://some.site.com;
}


choose the upstream module (
http://nginx.org/en/docs/http/ngx_http_upstream_module.html ) and define 
all
the backends in the upstream {} block:

upstream someservers {
    server your.backend1.ip:80;
    server your.backend2.ip:80;
    server your.backend2.ip:80;
}

location / {
   proxy_pass http://someservers;
}



rr
Please log in before posting. Registration is free and takes only a minute.
Existing account (Switch to SSL-encrypted connection)
NEW: Do you have a Google/GoogleMail or Yahoo account? No registration required!
Log in with Google account | Log in with Yahoo account
No account? Register here.