Re: Buffering issues with nginx

2017-07-29 Thread Dan34
In nginx docs I see sndbuf option in listen directive. Is there something that I don't understand about it, or developers of nginx don't understand meaning of sndbuf... but I do not see a point to set sndbuf on a listening socket. It just does not make any sense! sndbuf/rcvbuf is needed perhaps for

Re: Buffering issues with nginx

2017-07-29 Thread Dan34
It looks like for localhost buffers are bigger, but even if it's not local host I do get 5MB stuck in socket buffers. I was only able to get perfect results by writing my own proxy in c and doing some obscure nodejs code to avoid buffering. In any case, if nginx does not provide a way to control s

Re: Identifying "Writing" connections in status stub

2017-07-29 Thread Maxim Dounin
Hello! On Wed, Jul 26, 2017 at 06:05:28PM +0200, Vlad K. wrote: > On 2017-07-26 13:36, Peter Booth wrote: > > Vlad, > > > > I'd suggest beginning by seeing whether or not this is real. If you > > create a cron job that invokes netstat -ant every hour, then summarize > > the connections and eithe

Re: Workers CPU leak [epoll_wait,epoll_ctl]

2017-07-29 Thread Maxim Dounin
Hello! On Sat, Jul 29, 2017 at 05:35:08AM -0400, lamsung wrote: > Hello, I have strange issuses with nginx workers. For some time after start > Nginx I notice that some process of workers cause high load to CPU ( > principally sys CPU). [...] > Nginx has such version and modules: > > nginx v

Re: Accessing Nginx Cache mappings

2017-07-29 Thread Maxim Dounin
Hello! On Fri, Jul 28, 2017 at 09:59:53AM +0300, Gryzli Bugbear wrote: > Hi guys, > > I'm trying to implement cache-purger, which is using lua and separate > VirtualHosts, to clean the cache for a certain site/location based on > URI regex (similar to Varnish). > > Is there some easy way (mod

Re: redirect related questions...

2017-07-29 Thread Francis Daly
On Fri, Jul 28, 2017 at 02:13:23PM +0300, ST wrote: Hi there, > server { > server_name www.example.org example.com; # and some more domains > return 301 $scheme://example.org$request_uri; > } > > server { > listen 80; > server_name example.org; > ... > if ($http_user_agent !~ facebookexter

Re: Problem with uWSGI and PATH_INFO

2017-07-29 Thread Etienne Robillard
Hi Francis, Le 2017-07-28 à 03:17, Francis Daly a écrit : What I meant there was that you could possibly use fastcgi_split_path_info to define how you want your $request_uri to be split into parts for your SCRIPT_NAME and PATH_INFO as uwsgi_param values. So your eventual config could include

Workers CPU leak [epoll_wait,epoll_ctl]

2017-07-29 Thread lamsung
Hello, I have strange issuses with nginx workers. For some time after start Nginx I notice that some process of workers cause high load to CPU ( principally sys CPU). At first I've got syscall traces from one of such process: futex(0x157d914, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x157d910, {FUTEX_OP_SE