killed child process

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:

Re: DTLS patches

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: proxy_pass uri

On Friday 19 May 2017 00:32:33 Vasil Mikhalenya wrote: > Всем привет, > > вопрос по proxy_pass в случае указания uri. В документации не нашел > описания данного поведения, пытаюсь понять, что не так. > > map $scheme $o_upstream { > "http" "http://o_up;; > "https" "https://o_up_ssl;; > }

Re: releasing memory.

My module has c++ code which instantiates a class. I am driving most of my c++ from one ptr which I am saving in the context. I tried changing my code to use pool cleanup, it behaving worse than request->cleanup. Of the four requests I send, the cleanup handler is only getting called for two. I

proxy_pass uri

Всем привет, вопрос по proxy_pass в случае указания uri. В документации не нашел описания данного поведения, пытаюсь понять, что не так. map $scheme $o_upstream { "http" "http://o_up;; "https" "https://o_up_ssl;; } в случае location / { proxy_pass $o_upstream/pp/; на origin

Re: Http: make ngx_http_init_listening a public api

Thank you for your reply. As a client oriented proxy server, nginx will boot several worker process to listen on the same port. If a tcp connection is initiated, this connection will be processed by one worker. This model is simple yet efficient. However this model makes it impossible to let

RE: [PATCH] Proxy: support configuration of socket buffer sizes

Greetings, I just wanted to follow up on this patch and make sure that the fraud detection notice or confidentiality notice added by my company wasn't precluding it from consideration. Thanks! Nate -Original Message- From: nginx-devel [mailto:nginx-devel-boun...@nginx.org] On Behalf

Re: releasing memory.

Hello! On Thu, May 18, 2017 at 10:23:18AM -0700, Dk Jack wrote: > I just want to release memory l've allocated. One more question, > is the context memory automatically removed or is the module > responsible for freeing it. Anything you allocate from request pool (r->pool) using

Re: Http: make ngx_http_init_listening a public api

Hello! On Fri, May 19, 2017 at 01:12:29AM +0800, 0...@lvht.net wrote: > Is there any maintainer who could review this patch? Thanks. I don't think this change is needed. Listening sockets are to be created using the "listen" directive of the core module, they are not expected to be added by

Re: releasing memory.

Thank you Maxim, I just want to release memory l've allocated. One more question, is the context memory automatically removed or is the module responsible for freeing it. > On May 18, 2017, at 6:32 AM, Maxim Dounin wrote: > > Hello! > >> On Wed, May 17, 2017 at

Re: Http: make ngx_http_init_listening a public api

Hello, Is there any maintainer who could review this patch? Thanks. > 在 2017年5月1日，08:31，nginx-devel-boun...@nginx.org 写道： > > # HG changeset patch > # User 吕海涛 <0...@lvht.net> > # Date 1493595577 -28800 > # Mon May 01 07:39:37 2017 +0800 > # Node ID 2ddd0894c1a6c7efe45310b874a5b4091b58bb81

[nginx] Cache: ignore long locked entries during forced expire.

details: http://hg.nginx.org/nginx/rev/ab199f0eb8e8 branches: changeset: 7002:ab199f0eb8e8 user: Dmitry Volyntsev date: Thu May 18 18:39:16 2017 +0300 description: Cache: ignore long locked entries during forced expire. Abnormally exited workers may leave locked

Re: DTLS patches

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

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?

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

Re: releasing memory.

Hello! On Wed, May 17, 2017 at 05:53:40PM -0700, Dk Jack wrote: > Hi, > In my module, I registered a NGX_HTTP_POST_READ_PHASE handler. When this > handler is invoked, I allocate my module context and attach it to the > request. I also allocate some other memory and save the pointers to that >

Re: Auto refresh for expired content?

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

[nginx] Upstream: fixed u->headers_in.headers allocation error handling.

details: http://hg.nginx.org/nginx/rev/08537eab4f23 branches: changeset: 7001:08537eab4f23 user: Sergey Kandaurov date: Thu May 18 14:17:00 2017 +0300 description: Upstream: fixed u->headers_in.headers allocation error handling. Previously, an allocation error

Re: upstream - behavior on pool exhaustion

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

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 патчи

Привет, Для заинтересованных в тестировании поддержки DTLS, теперь доступен экспериментальный патч: http://nginx.org/patches/dtls/ Подробности в README.txt По результатам можно отписаться в этом треде (а лучше сразу в аналогичном в английской рассылке, чтобы не дублировать)

DTLS patches

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