On Sun, Jan 30, 2022 at 04:01:31AM -0500, unikron wrote:
Hi there,
> The error on a base dir is critical to all cache requests, so no request
> will succeed.
Yes. In your case, *all* requests are cache requests, so you want your
process to fail entirely. But in the general case, all of the non-c
The error on a base dir is critical to all cache requests, so no request
will succeed.
I know I can write a script to monitor it, but it seems like the wrong
approach.
I would like to have the option for nginx to stop if it can't do the job as
should, But I guess that if no one answered with that k
> I fail to see why it will keep on answering to new requests if it can't
fulfill any of them.
Because there might be other requests which can be answered without touching
the problematic cache directory?
While the error is critical (for the particular request) I don't think it
makes sense for ngi
I can't think of any edge case that will happen to my nginx instances,
that's why I want it to die.
I fail to see why it will keep on answering to new requests if it can't
fulfill any of them.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,293477,293484#msg-293484
___
> Cache config:
> proxy_cache_path /nginx/cache levels=1:2 keys_zone=bla:20m max_size=10g
inactive=20m use_temp_path=off;
>
> I had a problem while using tmpfs mount for nginx cache dir, my automation
mounted it over and over again(so each time nginx created a new set of base
dirs [a-z]), but afte
