Thank you, you've enlightened me;
I had the GlobalWhitelistDSTNet directive declared twice in two
different includes
This meant that an identical Acl declared in two different places would
contradict each other on the same addresses and generate mass warnings.
On 02/10/2023 22:01, Alex Rousskov wrote:
Since Squid 6.x we have this strange behavior on acl dst
Many warnings is generated
2023/10/02 20:18:50| WARNING: You should probably remove
'64.34.72.226' from the ACL named 'GlobalWhitelistDSTNet'
2023/10/02 20:18:50| WARNING: (B) '64.34.72.226' is a subnetwork of
(A) '64.34.72.226'
2023/10/02 20:18:50| WARNING: because of this '64.34.72.226' is
ignored to keep splay tree searching predictable
(B) '*64.34.72.226*' is a subnetwork of (A) '*64.34.72.226*' -->
Sure, this is the IP address.
Is it possible that you have two 64.34.72.226 entries in that
GlobalWhitelistDSTNet ACL? Perhaps in another included configuration
file or something like that?
You should probably remove '64.34.72.226' from the ACL named
'GlobalWhitelistDSTNet' --> Why this is only the IP address in the
acl ???
Squid thinks that there is more than one copy of 64.34.72.226 address
in GlobalWhitelistDSTNet ACL. It could be Squid bug, of course. Please
share a configuration that reproduces the issue or a pointer to
compressed "squid -N -X -d9 ..." output while reproducing the problem.
2023/10/02 20:20:09| FATAL: assertion failed: debug.cc:606:
"earlyMessages->size() < 1000"
Aborted
This assert is a side effect of the above ACL problem/bug - you
probably have many IPs in that ACL and the corresponding WARNINGs
exceed Squid hard-coded message accumulation limit. Now that we know
how a broken(*) configuration can produce so many early cache.log
messages, we should probably modify Squid to quit without asserting,
but let's focus on the root cause of your problems -- those WARNING
messages.
(*) I am not implying that _your_ configuration is broken.
Cheers,
Alex.
2023/10/02 20:18:50| WARNING: (B) '64.34.72.230' is a subnetwork of
(A) '64.34.72.230'
2023/10/02 20:18:50| WARNING: because of this '64.34.72.230' is
ignored to keep splay tree searching predictable
2023/10/02 20:18:50| WARNING: You should probably remove
'64.34.72.230' from the ACL named 'GlobalWhitelistDSTNet'
2023/10/02 20:18:50| WARNING: (B) '64.34.72.230' is a subnetwork of
(A) '64.34.72.230'
2023/10/02 20:18:50| WARNING: because of this '64.34.72.230' is
ignored to keep splay tree searching predictable
2023/10/02 20:18:50| WARNING: You should probably remove
'64.34.72.230' from the ACL named 'GlobalWhitelistDSTNet'
2023/10/02 20:18:50| WARNING: (B) '64.34.72.232' is a subnetwork of
(A) '64.34.72.232'
According to all warning, Squid won't start with this error
*2023/10/02 20:20:09| FATAL: assertion failed: debug.cc:606:
"earlyMessages->size() < 1000"**
**Aborted*
How to avoid this ??
--
David Touzeau - Artica Tech France
Development team, level 3 support
----------------------------------
P: +33 6 58 44 69 46
www:https://wiki.articatech.com
www:http://articatech.net
_______________________________________________
squid-users mailing list
squid-users@lists.squid-cache.org
https://lists.squid-cache.org/listinfo/squid-users
_______________________________________________
squid-users mailing list
squid-users@lists.squid-cache.org
https://lists.squid-cache.org/listinfo/squid-users
--
David Touzeau - Artica Tech France
Development team, level 3 support
----------------------------------
P: +33 6 58 44 69 46
www:https://wiki.articatech.com
www:http://articatech.net
_______________________________________________
squid-users mailing list
squid-users@lists.squid-cache.org
https://lists.squid-cache.org/listinfo/squid-users