Thanks Maxim I'll see what voodoo i can come up with for our deployment... or maybe submit a patch that would allow nginx to start even if the getbyhostname() is not returning the ip, then attempt to resolv it again later on as requests comes in.by masom - Nginx Mailing List - English
Thanks for the script.by masom - Nginx Mailing List - English
But shoulnd't nginx start anyway if the end point is not responding and just try to reach it anyway? I can't really see why it would need to stop or crash when either the endpoint (apache) or the dns system is unavailable. Yes it should display 5xx errors saying the endpoint is unreachable (dns or server failure / not-responding) but nginx should not "lock up" after 1 bad answer.by masom - Nginx Mailing List - English
Hi, I am currently planning to use nginx on several thousand devices as a reverse-proxy caching system. It currently work as expected (thanks Igor!), caches files as they are being requested by the devices. The only problem we hit is when nginx starts faster than the dns sytem is available on the units. Nginx will crash saying it is unable to connect to the remote host being proxied.by masom - Nginx Mailing List - English