[squid-users] [External] Re: Cache_peer breaks Squid 5.5

Thu Dec 14 01:30:01 UTC 2023

Old Good:
Name        : squid
Epoch       : 7
Version     : 5.5
Release     : 6.el9_3.1.0.1
Architecture: x86_64
Source RPM  : squid-5.5-6.el9_3.1.0.1.src.rpm
Build Date  : Fri 10 Nov 2023 11:47:19 PM EST

New Bad:
Name        : squid
Epoch       : 7
Version     : 5.5
Release     : 6.el9_3.2
Architecture: x86_64
Source RPM  : squid-5.5-6.el9_3.2.src.rpm
Build Date  : Wed 22 Nov 2023 05:13:20 PM EST

-----Original Message-----
From: HENDERSON, GAVEN L RTX
Sent: Wednesday, December 13, 2023 11:04 AM
To: squid-users at lists.squid-cache.org
Subject: RE: [External] Re: [squid-users] Cache_peer breaks Squid 5.5

Thanks for all the information.  I primarially deal with Windows so I'm dealing with a bit of a learning curve here.  Any suggestions on how to install Squid 6 on Rocky 9?  Can I do that with dnf/yum from a repo or an RPM?  I'm really hoping there's a way to do that without compiling.

-----Original Message-----
From: Alex Rousskov <rousskov at measurement-factory.com>
Sent: Wednesday, December 13, 2023 8:31 AM
To: HENDERSON, GAVEN L RTX <gaven.l.henderson at rtx.com>; squid-users at lists.squid-cache.org
Subject: Re: [External] Re: [squid-users] Cache_peer breaks Squid 5.5

On 2023-12-12 21:45, HENDERSON, GAVEN L RTX wrote:

> assertion failed: peer_digest.cc:419: "EX"

... which is one of the following assertions (quoted with their official Squid v5.5 line numbers, none of which is 419):

     412     assert(fetch->pd && receivedData.data);
     416     assert(fetch->buf + fetch->bufofs == receivedData.data);
     421     assert(fetch->bufofs <= SM_PAGE_SIZE);

FWIW, the latest Squid v5 branch code (and future v5.10 if it is released), fixes the bug that resulted in assertions logged as "EX"
instead of the actual assertion text. The same bug is fixed in all v6 releases.

This new bug report might be related:
https://urldefense.com/v3/__https://bugs.squid-cache.org/show_bug.cgi?id=5330__;!!MvWE!GWVUtWGdcsSlCpQnSreaelvBFVUzRBoz315_Hs-MfksgZgo0TW82oiY4HVlajT31-yti6h8AijE4eqKOQEPrRqk0IxEc-t_G$

> Any thoughts on how to fix this on Rocky 9?

Unfortunately, I failed to find good suspects for this v5 bug -- all obvious suspects came after v5.5 was released. However, I do not even know which version you were running before updating to v5.5. Please note that v5 is not officially supported by the Squid Project.

My recommendation is to update to v6.6 or later.

HTH,

Alex.

> -----Original Message-----
> From: squid-users <squid-users-bounces at lists.squid-cache.org> On
> Behalf Of Alex Rousskov
> Sent: Tuesday, December 12, 2023 10:22 AM
> To: squid-users at lists.squid-cache.org
> Subject: [External] Re: [squid-users] Cache_peer breaks Squid 5.5
>
> On 2023-12-12 11:25, HENDERSON, GAVEN L RTX wrote:
>> Sorry if this has already been answered.  I couldn't find anything online regarding the problem I am experiencing.  I have a Squid server acting as a proxy relay.  It listens on two ports and, depending on which port a request comes in, the request is forwarded to a specific upstream proxy.  Everything was working prior to the 5.5 update.  Now, Squid starts but crashes a few seconds later.  I have traced it down to the cache_peer directives.  If I comment them out, the service is stable.  I have also tried the stock configuration with only the cache_peer directive added and it still crashes so I don't think the problem is being triggered by some other part of my configuration.  I'm not seeing anything particularly helpful in the messages log:
>
> What do you see in Squid's cache.log? I would expect a message about Squid hitting an assertion or detecting another catastrophic problem before crashing. If there is nothing in cache.log, consider (enabling core dumps in your OS configuration and) getting a backtrace from the crashed Squid process.
>
>
> HTH,
>
> Alex.
>
>
>
>> Nov 24 15:17:30 svr-squid squid[2259]: Squid Parent: squid-1 process
>> 2290 exited due to signal 6 with status 0 Nov 24 15:17:30 svr-squid
>> squid[2259]: Squid Parent: squid-1 process 2290 will not be restarted
>> for 3600 seconds due to repeated, frequent failures Nov 24 15:17:30 svr-squid squid[2259]: Exiting due to repeated, frequent failures Nov 24 15:17:30 svr-squid systemd[1]: mailto:systemd-coredump at 21-2295-0.service: Deactivated successfully.
>> Nov 24 15:17:30 svr-squid systemd[1]: squid.service: Main process
>> exited, code=exited, status=1/FAILURE Nov 24 15:17:30 svr-squid systemd[1]: squid.service: Failed with result 'exit-code'.
>>
>> Here is my configuration:
>>
>> http_port 192.168.0.1:80 name=port80
>> http_port 192.168.0.1:81 name=port81
>>
>> acl port80_acl myportname port80
>> acl port81_acl myportname port81
>> acl bypass_parent dstdom_regex "/etc/squid/bypass_parent.txt"
>> acl domain_blacklist dstdomain "/etc/squid/domain_blacklist.txt"
>>
>> http_access deny all domain_blacklist always_direct allow
>> bypass_parent never_direct allow port80_acl never_direct allow
>> port81_acl
>>
>> cache_peer proxy1.domain.com parent 80 0 default name=proxy80
>> cache_peer_access proxy80 allow port80_acl cache_peer_access proxy80
>> deny all
>>
>> cache_peer proxy2.domain.com parent 80 0 default name=proxy81
>> cache_peer_access proxy81 allow port81_acl cache_peer_access proxy81
>> deny all
>>
>> http_access allow all
>>
>> logformat squid [%tl] %>a %>eui %Ss/%03>Hs %<st %rm %ru %[un %Sh/%<a
>> %mt _______________________________________________
>> squid-users mailing list
>> squid-users at lists.squid-cache.org
>> https://urldefense.com/v3/__https://lists.squid-cache.org/listinfo/sq
>> u
>> id-users__;!!MvWE!FEDTJs2pTa3njy74FPFejy1UEla67Tsxo5KMiUxhSdHn4--dUL_
>> t kUqmWCJ64l_RHB9_uSLhEWcTeWWRcO7R6E68TUQsCFE6$
>
> _______________________________________________
> squid-users mailing list
> squid-users at lists.squid-cache.org
> https://urldefense.com/v3/__https://lists.squid-cache.org/listinfo/squ
> id-users__;!!MvWE!FEDTJs2pTa3njy74FPFejy1UEla67Tsxo5KMiUxhSdHn4--dUL_t
> kUqmWCJ64l_RHB9_uSLhEWcTeWWRcO7R6E68TUQsCFE6$