[squid-users] logging: TCP connection to x.x.x.x/3128 failed

[Alex Rousskov]

On 4/25/23 03:07, Waldemar Brodkorb wrote:
> Alex Rousskov wrote,
>> On 4/14/23 05:29, Waldemar Brodkorb wrote:
>>>> On 4/6/23 06:41, Waldemar Brodkorb wrote:
>>>>
>>>>> There is still one assertion which happens sometimes:
>>>>> cache.log:2023/04/06 07:24:48 kid1| assertion failed: ../src/base/CbcPointer.h:181: "EX"
>>>>>
>>>>> Have you ever seen this in the wild? What does it mean?
>>>>
>>>> This low-level assertion (where "EX" is usually spelled as "c") corresponds
>>>> to many high-level Squid bugs, most of them fixed. Please see
>>>> https://bugs.squid-cache.org/show_bug.cgi?id=5265#c1 for the suggested next
>>>> steps.
>>
>>> We have a core dump now. Ubuntu 22.04 with Squid 5.8.
>>
>>> Do you can see where the bug is?
>>
>> On the surface, the stack trace looks like bug #4981 to me. That bug has a
>> workaround for v4. I do not know whether that workaround patch still applies
>> to v5, but it is worth trying:
>> https://bugs.squid-cache.org/show_bug.cgi?id=4981
>>
>> Please keep us posted.
> 
> The patch is still usable. I applied it, rebuild Squid and now I get
> the messages instead of a crash. So for me the workaround works 

Thank you very much for this information! I have updated the bug report 
accordingly.

Alex.