Thanks, Maxim, for correcting my misunderstanding.
With what frequency is the cache manger run?
Roger
> On Apr 3, 2020, at 9:26 AM, Maxim Dounin wrote:
>
> Hello!
>
> On Fri, Apr 03, 2020 at 08:33:43AM -0700, Roger Fischer wrote:
>
>>> You can just set the inactive time longer than your poss
Hello!
On Fri, Apr 03, 2020 at 08:33:43AM -0700, Roger Fischer wrote:
> > You can just set the inactive time longer than your possible maximum expire
> > time for the objects then the cache manager won't purge the cache files
> > even the object is still valid but not accessed.
>
> That may o
> You can just set the inactive time longer than your possible maximum expire
> time for the objects then the cache manager won't purge the cache files even
> the object is still valid but not accessed.
That may only have a small impact.
As far as I understand:
NGINX will remove an item only
It seems to related to apache set ups on the origin that were running openssl
1.1.1e since the upgrade to 1.1.1f it seems better and the SSL_read errors are
gone.
https://github.com/openssl/openssl/issues/11381#issuecomment-607732081
Liam
Sent from ProtonMail mobile
Original Message
Hi Konstantin,
On Tue, Mar 10, 2020 at 3:31 PM Konstantin Pavlov wrote:
> Hello,
>
> 10.03.2020 15:50, Emilio Fernandes wrote:
> > Hi Konstantin,
> > Thanks for your interest in our packages!
> >
> > By CentOS, do you want/need packages built for 8? Asking because I
> > believe 7 is
Hello!
On Thu, Apr 02, 2020 at 01:26:02PM +, Liam Moncur wrote:
> Hey,
> I am seeing an issue where nginx seems to get stuck in a loop soon after the
> above error. From the debug I am seeing:
>
> 2020/04/02 14:09:10 [error] 12875#12875: *338 SSL_read() failed (SSL:
> error:1409441A:SSL ro
