[squid-users] [ext] Re: Change of server hardware (?) resulted in massive increase of crashes

Ralf Hildebrandt Ralf.Hildebrandt at charite.de
Tue Sep 22 14:03:43 UTC 2020

> > 2020/09/22 09:34:07| FATAL: check failed: opening()
> >     exception location: tunnel.cc(1305) noteDestinationsEnd
> >     current master transaction: master359979
> This is still bug #5055. I hope we will post an official pull request
> properly addressing it soon.

I can easily test it here :)

> In my environment, Squid v5 is hardly usable without those fixes but, as
> you know, YMMV.


> Your OS upgrade could trigger different DNS resolution
> timings, the new cluster may have different IPv6 connectivity profile,
> or there can be similar minor/innocent changes that result in slightly
> different Squid state and more exceptions. I would not spend time trying
> to pinpoint the exact trigger.
> I updated bug #5055 with a patch that covers the tunneling case:
> https://bugs.squid-cache.org/show_bug.cgi?id=5055#c5

Thanks, I'll try that once the dust has settled.

Ralf Hildebrandt
Charité - Universitätsmedizin Berlin
Geschäftsbereich IT | Abteilung Netzwerk

Campus Benjamin Franklin (CBF)
Haus I | 1. OG | Raum 105
Hindenburgdamm 30 | D-12203 Berlin

Tel. +49 30 450 570 155
ralf.hildebrandt at charite.de

More information about the squid-users mailing list