On 4/13/22 16:24, Eliezer Croitoru wrote:
Can you please verify if the next is a workaround to your issue:
cache_mem 16 MB
cache deny all
Just to avoid misunderstanding, bug #5055 and virtually any other bug
that manifests itself in FATAL messages from noteDestinationsEnd code is
unrelated to HTTP caching and is unlikely to be mitigated by changing
the cache memory size and/or denying HTTP caching.
Alex.
-----Original Message-----
From: squid-users <squid-users-boun...@lists.squid-cache.org> On Behalf Of pvs
Sent: Wednesday, April 13, 2022 19:23
To: squid-users@lists.squid-cache.org
Subject: Re: [squid-users] Fine tuning of Squid and OS configuration for
handling more loads
Thanks Alex.
We will upgrade the squid and see if the problem recurs
O 12-04-2022 19:57, Alex Rousskov wrote:
On 4/11/22 07:26, pvs wrote:
cache.log file is attached with contents narrowed down to the time
just before squid process oscillating (going up and down), ultimately
dying.
Your Squid v5.2 is probably suffering from bug #5055:
https://bugs.squid-cache.org/show_bug.cgi?id=5055
Upgrade your Squid to v5.4.1 or later.
We tried to analyze the syslog file, squid access/cache log files,
not got any concrete clues.
FWIW, look for messages mentioning words "FATAL":
2022/03/02 09:05:42 kid1| FATAL: check failed: opening()
exception location: tunnel.cc(1300) noteDestinationsEnd
HTH,
Alex.
_______________________________________________
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users
_______________________________________________
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users
