Re: TCP Connection

Giulio, On 3/5/16 1:25 AM, Giulio Loffreda wrote: > Here is my nginx.conf and site config. After calling tcp > connection and getting http 400, no log is generated. > > I’m following > Let me re-phrase: this is not your _full_ nginx config. There are probably other files in /etc/nginx or somewh

Re: TCP Connection

On Friday 04 March 2016 23:25:27 Giulio Loffreda wrote: > Here is my nginx.conf and site config. > After calling tcp connection and getting http 400, no log is generated. > > I’m following > > Thanks > > server { > listen 80; > server_name apidvc.sparkgo.cc; > access_log

Re: Nginx 1.9.11 and OpenSSL 1.0.2G - HTTP2, but no ALPN negotiated.

Hello, Great, thanks Andrew! Best Regards Posted at Nginx Forum: https://forum.nginx.org/read.php?2,265036,265115#msg-265115 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: TCP Connection

Here is my nginx.conf and site config. After calling tcp connection and getting http 400, no log is generated. I’m following Thanks server { listen 80; server_name apidvc.sparkgo.cc; access_log /var/log/nginx/myhost.com.access.log combined; root /home/spark/myho

Re: TCP Connection

On Friday 04 March 2016 19:12:56 Giulio Loffreda wrote: > Still having no luck. > No log is generated. > > TCP connection has any relation to web socket support configuration ? > > this is my site config. > > server { > listen 80; > server_name myhost.com; > access_log /v

Re: TCP Connection

does /var/log/nginx exist, and it is writeable by the web server user? On 03/05/2016 07:12 AM, Giulio Loffreda wrote: Still having no luck. No log is generated. TCP connection has any relation to web socket support configuration ? this is my site config. server { listen 80;

Re: TCP Connection

You have been told to use the info error_log level, which is not set (defaults to error). ​Make sure no other error_log directive might overwrite this one.​ --- *B. R.* On Fri, Mar 4, 2016 at 7:12 PM, Giulio Loffreda wrote: > Still having no luck. > No log is generated. > > TCP connection has an

Re: TCP Connection

Still having no luck. No log is generated. TCP connection has any relation to web socket support configuration ? this is my site config. server { listen 80; server_name myhost.com; access_log /var/log/nginx/myhost.com.log combined; error_log /var/log/nginx/myhost.

Re: TCP Connection

On Friday 04 March 2016 17:41:42 Giulio Loffreda wrote: > Thank you for your answer. > > Here is my log after the request, my request, my response and my nginx.conf > > root@vps190138:~# cat /var/log/nginx-error.log > 2016/03/04 15:49:02 [notice] 8990#0: using the "epoll" event method > 2016/03/0

Re: TCP Connection

Thank you for your answer. Here is my log after the request, my request, my response and my nginx.conf root@vps190138:~# cat /var/log/nginx-error.log 2016/03/04 15:49:02 [notice] 8990#0: using the "epoll" event method 2016/03/04 15:49:02 [notice] 8990#0: nginx/1.8.1 2016/03/04 15:49:02 [notice] 8

Re: TCP Connection

On Friday 04 March 2016 17:20:18 Giulio Loffreda wrote: > Hi All, > > If I’m sending this email to wrong list, apologies and give me the good one. > > I have one embedded application which needs to connect via TCP and send an > HTTP request. > We run Nginx on Ubuntu 14.04. > > I can connect and

TCP Connection

Hi All, If I’m sending this email to wrong list, apologies and give me the good one. I have one embedded application which needs to connect via TCP and send an HTTP request. We run Nginx on Ubuntu 14.04. I can connect and persist, but once the packet is sent, I get HTTP 400 without any log and

Re: Workers CPU leak [epoll_wait,epoll_ctl]

On Friday 04 March 2016 09:42:45 vizl wrote: > Sorry, my misprint. > > Config whithout aio on; > > only aio threads=default; > > > do you or some tool periodically change the files ? > no, files are unchanged, just periodically some new are added and some > expired are deleted > Could you

Re: Workers CPU leak [epoll_wait,epoll_ctl]

Sorry, my misprint. Config whithout aio on; only aio threads=default; > do you or some tool periodically change the files ? no, files are unchanged, just periodically some new are added and some expired are deleted Posted at Nginx Forum: https://forum.nginx.org/read.php?2,264764,265095#msg

Re: Workers CPU leak [epoll_wait,epoll_ctl]

On Friday 04 March 2016 08:25:43 vizl wrote: > user www; > worker_processes 16; > thread_pool default threads=128 max_queue=1024; > worker_rlimit_nofile 65536; > ###timer_resolution 100ms; > > #error_log /home/logs/error_log.nginx error; > error_log /home/logs/error_log.nginx.debug debug; > > eve

Re: upstream prematurely closes cnx => 502 Bad Gateway to client

I've also seen the issue when running plain nginx 1.9.11 sort like builting a new nginx, only the issue is that upstream closes cnxs, not nginx. Since I've discovered that our TCs had the Connector' keepAliveTimeout way low (10 msec), mistakenly thought the units were sec and not as actually msec.

Re: Workers CPU leak [epoll_wait,epoll_ctl]

user www; worker_processes 16; thread_pool default threads=128 max_queue=1024; worker_rlimit_nofile 65536; ###timer_resolution 100ms; #error_log /home/logs/error_log.nginx error; error_log /home/logs/error_log.nginx.debug debug; events { worker_connections 3; use epoll; } http { includ

Re: Workers CPU leak [epoll_wait,epoll_ctl]

On 3/4/16 3:20 PM, Valentin V. Bartenev wrote: > On Friday 04 March 2016 07:12:09 vizl wrote: >> Sorry for long answer, but we have doing some tests, and notice that probles >> is appear when thread_pool enabled. >> >> thread_pool default threads=128 max_queue=1024 >> >> We need to use thread_pool

Re: Workers CPU leak [epoll_wait,epoll_ctl]

On Friday 04 March 2016 07:12:09 vizl wrote: > Sorry for long answer, but we have doing some tests, and notice that probles > is appear when thread_pool enabled. > > thread_pool default threads=128 max_queue=1024 > > We need to use thread_pool, and can't permenent disable it unfortunately > [..

Re: Workers CPU leak [epoll_wait,epoll_ctl]

Sorry for long answer, but we have doing some tests, and notice that probles is appear when thread_pool enabled. thread_pool default threads=128 max_queue=1024 We need to use thread_pool, and can't permenent disable it unfortunately Posted at Nginx Forum: https://forum.nginx.org/read.php?2,264

Re: upstream prematurely closes cnx => 502 Bad Gateway to client

Hi. Am 04-03-2016 11:00, schrieb stefws: stefws Wrote: --- Seems I'm not alone w/TC issues ;) missed the link: http://permalink.gmane.org/gmane.comp.web.haproxy/26860 Well Maybe you have a completely different situation. Is it possible to b

Re: TLS session resumption (identifier)

On 04 Mar 2016, at 13:30, B.R. wrote: > On Fri, Mar 4, 2016 at 11:19 AM, Igor Sysoev wrote: > Sorry, I meant there is no performance difference between “none” and “off” > settings. > > ​Well, the client believes he should remember every session ID and store it > somewhere for nothing, reading

Re: TLS session resumption (identifier)

On Fri, Mar 4, 2016 at 11:19 AM, Igor Sysoev wrote: > Sorry, I meant there is no performance difference between “none” and “off” > settings. > ​Well, the client believes he should remember every session ID and store it somewhere for nothing, reading/resending/writing it on every connection. Smal

Re: TLS session resumption (identifier)

On 04 Mar 2016, at 12:55, B.R. wrote: > On Fri, Mar 4, 2016 at 10:33 AM, Igor Sysoev wrote: >> But still, advertising something without actually supporting it must lead to >> cases where sessions reuse is believed to take place without ever happening, >> harming performance... that was probabl

Re: upstream prematurely closes cnx => 502 Bad Gateway to client

stefws Wrote: --- > Seems I'm not alone w/TC issues ;) missed the link: http://permalink.gmane.org/gmane.comp.web.haproxy/26860 Posted at Nginx Forum: https://forum.nginx.org/read.php?2,265031,265079#msg-265079 _

Re: upstream prematurely closes cnx => 502 Bad Gateway to client

Seems I'm not alone w/TC issues ;) Posted at Nginx Forum: https://forum.nginx.org/read.php?2,265031,265078#msg-265078 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: TLS session resumption (identifier)

On Fri, Mar 4, 2016 at 10:33 AM, Igor Sysoev wrote: > But still, advertising something without actually supporting it must lead > to cases where sessions reuse is believed to take place without ever > happening, harming performance... that was probably happening in versions < > 1.5.9. > > > I do

Re: TLS session resumption (identifier)

On 04 Mar 2016, at 12:08, B.R. wrote: > Thanks Igor, that makes the whole thing crystal clear! > > What saves us there is the fact that, if I understand it well, the RFC 5077​ > states the server decides by itself on the use of tickets and those have > precedence over identifiers. Yes. > Bu

Re: TLS session resumption (identifier)

Thanks Igor, that makes the whole thing crystal clear! What saves us there is the fact that, if I understand it well, the RFC 5077 ​ states the server decides by itself on the use of tickets and those have precedence over identifiers. But still, adv