Re: php not working from aliased subdir

2017-01-30 Thread Nikolaos Milas
On 19/1/2016 10:58 μμ, Francis Daly wrote: Good luck with it, Thank you Francis and everyone for your feedback. I have tried various things with the aliased directories, but I am still having the problem. I hope someone can help me with my current config, which I attach, together with the

Re: fail_timeout in upstream not rescpeted?

2017-01-30 Thread Ruslan Ermilov
On Mon, Jan 30, 2017 at 03:41:24AM -0500, plrunner wrote: > Thank you very much for the quick reply. > > OK, it's pretty clear now. > > I've read the "zone" directive is available since nginx v1.9. > For sake of other readers as well, does this mean that what am addressing > here is not possible

Re: fail_timeout in upstream not rescpeted?

2017-01-30 Thread Maxim Dounin
Hello! On Mon, Jan 30, 2017 at 02:41:06AM -0500, plrunner wrote: > Hi everybody, > > I am running nginx v1.11 and I noticed something pretty weird in my > error.log. > > I have fail_timeout=1800s along with max_fails=1 in my upstream and > proxy_next_upstream is set to "error timeout", so I exp

Re: fail_timeout in upstream not rescpeted?

2017-01-30 Thread plrunner
Thank you very much for the quick reply. OK, it's pretty clear now. I've read the "zone" directive is available since nginx v1.9. For sake of other readers as well, does this mean that what am addressing here is not possible to be solved in previous versions, isn't it? Paolo Posted at Nginx Fo

Re: fail_timeout in upstream not rescpeted?

2017-01-30 Thread Ruslan Ermilov
On Mon, Jan 30, 2017 at 02:41:06AM -0500, plrunner wrote: > Hi everybody, > > I am running nginx v1.11 and I noticed something pretty weird in my > error.log. > > I have fail_timeout=1800s along with max_fails=1 in my upstream and > proxy_next_upstream is set to "error timeout", so I expect an up