> This is still bug #5055. I hope we will post an official pull request > properly addressing it soon. > > 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 I applied your renewed patch to squid-6.0.0-20200811-r983fab6e9 -- and so far the resulting binary seems to be much more stable than with the previous patch to #5055. We're currently giving that instance 10% of the connections for testing (in contrast to the usual 25%) 5.0.2 (running on the other 3 nodes) gives us about 21.7h average uptime with a median uptime of 28.6h -- 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@xxxxxxxxxx https://www.charite.de _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
