killed child process

2017-05-18 Thread Alex Samad
Hi so I have lots of clients on long lived tcp connections , getting rp into 2 back end app servers I had a line in my error log, saying one of the upstream was failed caused it timeout - then I got this 2017/05/18 13:30:42 [notice] 2662#2662: exiting 2017/05/18 13:30:42 [notice] 2662#2662: ex

Re: DTLS patches

2017-05-18 Thread George
thanks Vladimir :) Posted at Nginx Forum: https://forum.nginx.org/read.php?2,274289,274312#msg-274312 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: DTLS patches

2017-05-18 Thread Vladimir Homutov
On Thu, May 18, 2017 at 10:29:16AM -0400, George wrote: > thanks for sharing. Is it necessary to compile with --with-debug ? > no, it will work without debug as well ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: DTLS patches

2017-05-18 Thread George
thanks for sharing. Is it necessary to compile with --with-debug ? Posted at Nginx Forum: https://forum.nginx.org/read.php?2,274289,274299#msg-274299 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: Auto refresh for expired content?

2017-05-18 Thread mkuehn
Hi Roman, hi Francis, here comes my production config - i made a few tests the last hours, it always come to the same point - if proxy_cache_background_update is on, nginx devilvers only the cached content and is not able to fetch a fresh copy (dont know why) - i tried local files, i tried my prod

Re: Auto refresh for expired content?

2017-05-18 Thread Roman Arutyunyan
On Wed, May 17, 2017 at 09:07:30AM -0400, mkuehn wrote: > Hi Roman, > > thanks for your reply - with proxy_cache_background_update is OFF, the > correct testfile "test.js"is requested: > > "GET /test.js HTTP/1.0" 200 199503 "-" "Mozilla/5.0 (Windows NT 6.1; Win64; > x64) AppleWebKit/537.36 (KHTML

Re: upstream - behavior on pool exhaustion

2017-05-18 Thread Ruslan Ermilov
Did you have a chance to try my patch yet? On Tue, Apr 25, 2017 at 05:44:37PM +0300, Ruslan Ermilov wrote: > On Sat, Apr 22, 2017 at 01:52:48AM +0200, B.R. via nginx wrote: > > I do not know if your detailed explanation was aimed to me, or to the list > > in general, but I got all that already as

Re: Upstream block: backup with max_fails=0 does not appear to work as expected

2017-05-18 Thread Roman Arutyunyan
Hi Jonathan, On Wed, May 17, 2017 at 05:05:51PM -0400, Jonathan Simowitz via nginx wrote: > Hello, > > I have an upstream block with two servers as follows: > > upstream { > server foo.com; > server bar.com max_fails=0 backup; > } > > My desired use case would be that the foo.com server is

DTLS patches

2017-05-18 Thread Vladimir Homutov
Hello all, For all those interested in testing DTLS support, experimental patch is now available at http://nginx.org/patches/dtls/ Check the README.txt for details . If you have any feedback, please report to this thread. ___ nginx mailing list nginx@n