Re: Files still on disc after inactive time

After this inactive logs I have anther logs: [alert] 11371#0: worker process 24870 exited on signal 9 Can you explain whats happend when I have logs like this: [error] 9045#0: *1138267 readv() failed (104: Connection reset by peer) while reading upstream... I have problem like

Re: Files still on disc after inactive time

100GB of cached files sounds enormous. What kinds of files are you caching? How large are they? How many do you have? If you look at your access log what hit rate is your cache seeing? Sent from my iPad > On Feb 16, 2018, at 3:16 AM, Andrzej Walas > wrote: > >

Re: Files still on disc after inactive time

Can you answer on this: > Can you tell me what happend with downloaded part of files when I have: > [error] 16082#0: *1264804 upstream prematurely closed connection while > reading upstream > [crit] 16082#0: *1264770 pwritev() has written only 49152 of 151552 > while reading upstream > This part

Re: Files still on disc after inactive time

Hello! On Fri, Feb 16, 2018 at 03:16:27AM -0500, Andrzej Walas wrote: > After this inactive logs I have anther logs: > [alert] 11371#0: worker process 24870 exited on signal 9 Signal 9 is SIGKILL sent to the nginx worker process. Killing nginx worker processes will obviously result in various

Re: Files still on disc after inactive time

For me 40-50 GB cache is ok, because I have multiple files like 2-5GB. Problem in my mind is this that I have settings: proxy_cache_path /ephemeral/nginx/cache levels=1:2 keys_zone=proxy-cache:4000m max_size=40g inactive=1d; but I have over 40GB on disc and files older than 1 day

Re: Response Header IF statement problem

On Thu, Feb 15, 2018 at 01:22:04PM +, Friscia, Michael wrote: Hi there, > To add one more thing. I mentioned that my testing failed. Exactly what was > failing is that the map{} block that worked and then stopped working was the > problem, the $nocache variable would always return the

Re: Response Header IF statement problem

On Fri, Feb 16, 2018 at 01:49:59PM +, Friscia, Michael wrote: Hi there, > Thank you, this was incredibly useful and helped me think this through in > Nginx terms and I have everything working now. Thank you again! You're welcome. Good to hear that you have things working the way you want

Re: Response Header IF statement problem

Thank you, this was incredibly useful and helped me think this through in Nginx terms and I have everything working now. Thank you again! Minor side question, is there a variable I can use to post to a debug header to indicate if a page was newly written to the cache versus a page that was read

Re: PID file

Добрый день, читайте этот тред: http://mailman.nginx.org/pipermail/nginx-ru/2017-November/060604.html https://forum.nginx.org/read.php?21,277438 ___ nginx-ru mailing list nginx-ru@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx-ru

Некорректная работа при выведении сервера из апстрима за timeout

Добрый день. nginx version: nginx/1.12.2 Кслассическая схема: nginx - apache (10 серверов) - mysql В случае перегрузки базы данных апач отвечает медленно, что логично. Перестаёт отвечать nginx'у. И как следствие nginx выводит сервер с апачом из работы. Соответственно сервер начинает то

Re: Некорректная работа при выведении сервера из апстрима за timeout

Hello! On Fri, Feb 16, 2018 at 01:12:43PM +0300, kpoxa wrote: > Добрый день. > > nginx version: nginx/1.12.2 > > Кслассическая схема: > > nginx - apache (10 серверов) - mysql > > В случае перегрузки базы данных апач отвечает медленно, что логично. > Перестаёт отвечать nginx'у. > И как

Re: [PATCH] Limit req: r/h and r/d support

Hello! On Fri, Feb 16, 2018 at 03:57:05PM +0100, Bernhard Reutner-Fischer wrote: > Attached is a patch to add r/h and r/d limit_req support. > > There are at least two feature requests that i found asking for this: > - https://trac.nginx.org/nginx/ticket/68 > -

Re: [PATCH] Limit req: r/h and r/d support

On 16 February 2018 at 15:57, Bernhard Reutner-Fischer wrote: > Hi! > > Attached is a patch to add r/h and r/d limit_req support. > > There are at least two feature requests that i found asking for this: > - https://trac.nginx.org/nginx/ticket/68 > -

[PATCH] Limit req: r/h and r/d support

Hi! Attached is a patch to add r/h and r/d limit_req support. There are at least two feature requests that i found asking for this: - https://trac.nginx.org/nginx/ticket/68 - https://trac.nginx.org/nginx/ticket/1060 Ok? Please consider applying. thanks and cheers, # HG changeset patch # User