Re: nginx core dump explodes

I tested now the second patch as well. There are no more socket leaks with both fixes. Thanks! Posted at Nginx Forum: https://forum.nginx.org/read.php?2,267669,267928#msg-267928 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/l

Re: nginx core dump explodes

Thanks a lot for the detailed explanation. The first patch reduced the socket leaks by >99%. I will run tests with second patch beginning next week and check if it goes down to 0 leaks. Are does 2 fixes integrated in the next release 1.11.2? Thanks! Posted at Nginx Forum: https://forum.nginx.or

Re: nginx core dump explodes

Wow, that was fast, thanks :) I'm doing tests now with the h2 fix. It looks promising so far. I will continue to run various test to see if there are scenarios that trigger an open socket leak. - At which point in the debug log did you know there is something going wrong? - Is there an explanatio

Re: nginx core dump explodes

Here you go: https://tempfile.me/dl/ES9tWLqjnFozdx/ Thanks! Posted at Nginx Forum: https://forum.nginx.org/read.php?2,267669,267783#msg-267783 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: nginx core dump explodes

Here more of the debug log. I had to shorten it as I did get this message "Please shorten your messages, the body is too large". Thanks! 2016/06/19 19:53:09 [debug] 8724#0: *19047 accept: :54691 fd:236 2016/06/19 19:53:09 [debug] 8724#0: *19047 event timer add: 236: 6:1466358849721 2016/06/1

Re: nginx core dump explodes

I already did. Is there something specific I should look after in that debug log? Here a little extract (note: I replaced the request with ): ... 2016/06/19 19:53:11 [debug] 8724#0: *19047 event timer: 63, old: 1466358851127, new: 1466358851267 2016/06/19 19:53:11 [debug] 8724#0: *19047 http upst

Re: nginx core dump explodes

The dump was 550GB large. So I guess the only explanation for this are the accumulated keys_zone sizes. There are no third-party modules. We only see the leaks for specific HTTP/2 traffic at every reload. Posted at Nginx Forum: https://forum.nginx.org/read.php?2,267669,267748#msg-267748 ___

Re: nginx core dump explodes

Thanks, setting the value to 600G made it possible to get a dump. But it took ages and the system became quite unstable. What can cause the dump to become that large? There is almost no traffic (<10Mbps) on this server with 32G memory. Posted at Nginx Forum: https://forum.nginx.org/read.php?2,26

nginx core dump explodes

nginx version: nginx/1.11.1 built with OpenSSL 1.0.2h 3 May 2016 I try to debug those alerts currently, which only appear after a reload: 2016/06/17 13:10:49 [alert] 14624#0: *15709 open socket #626 left in connection 628 I compiled nginx with --with-debug and set the flags CFLAGS="-g -O0" ./co

Prevent cache from storing files multiple times in the proxy_temp dir

Our nginx reverse proxy creates a temporary entry in the proxy_temp directory if that file does not yet exists in the cache. So far so good but if the file does not exists and the file will be requested 10 times at the same time it creates 10 temporary files in the proxy_temp and fetches the data 1

Re: Max File Size Allowed In Cache

Thanks Martin! That works. Posted at Nginx Forum: http://forum.nginx.org/read.php?2,253260,253687#msg-253687 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: Max File Size Allowed In Cache

Thanks Maxim. Is it possible the filter on a value "larger than" or "smaller than"? How would the regex in the map block look like? e.g. smaller than 100? I tried something like this, which is not working: map $upstream_http_content_length $docache { default 0; "~*([1-9

Re: Max File Size Allowed In Cache

would be interesting to know the answer to this questions as I was wondering as well if that is possible. Thanks for the response! Posted at Nginx Forum: http://forum.nginx.org/read.php?2,253260,253608#msg-253608 ___ nginx mailing list nginx@nginx.org