[squid-users] [ext] Re: Squid 6.4 assertion errors: FATAL: assertion failed: stmem.cc:98: "lowestOffset () <= target_offset" current master transaction: master655 (backtrace)]
If it is not possible to revert the commits, what should be done? Should I go back to Squid 6.3 (6.4 was pulled from the site)? http://www.squid-cache.org/Versions/v6/ I have clients where Squid cannot be easily disabled and are now without internet connection. ___ squid-users mailing list squid-users@lists.squid-cache.org https://lists.squid-cache.org/listinfo/squid-users
Re: [squid-users] [ext] Re: Squid 6.4 assertion errors: FATAL: assertion failed: stmem.cc:98: "lowestOffset () <= target_offset" current master transaction: master655 (backtrace)]
On 2023-10-24, Amos Jeffries wrote: > On 24/10/23 22:26, Ralf Hildebrandt wrote: >>> I'll add a "me too" to this. 6.3 reliable, 6.4 crashes and this is under >>> _very_ low load. NetBSD 9.3_STABLE. >> >> You can check the debugging recommendation in >> https://bugs.squid-cache.org/show_bug.cgi?id=5309 >> >> I'll try 6.4 on my test proxy now (with very low to no load at all), >> and will also try 7.0/master >> > > FTR; current workaround is to reverse this patch from 6.4: > > https://github.com/squid-cache/squid/commit/a27bf4b84da23594150c7a86a23435df0b35b988 Unfortunately other commits on top touch some of the same files so the simple methods of applying the above with patch -R, or 'git revert', need more fix-up. ___ squid-users mailing list squid-users@lists.squid-cache.org https://lists.squid-cache.org/listinfo/squid-users
Re: [squid-users] [ext] Re: Squid 6.4 assertion errors: FATAL: assertion failed: stmem.cc:98: "lowestOffset () <= target_offset" current master transaction: master655 (backtrace)]
On 24/10/23 22:26, Ralf Hildebrandt wrote: I'll add a "me too" to this. 6.3 reliable, 6.4 crashes and this is under _very_ low load. NetBSD 9.3_STABLE. You can check the debugging recommendation in https://bugs.squid-cache.org/show_bug.cgi?id=5309 I'll try 6.4 on my test proxy now (with very low to no load at all), and will also try 7.0/master FTR; current workaround is to reverse this patch from 6.4: https://github.com/squid-cache/squid/commit/a27bf4b84da23594150c7a86a23435df0b35b988 That is a partial removal of the SQUID-2003:2 vulnerability fix. I hope we can have this corrected and an updated fix in the scheduled 6.5 release on Nov 5. HTH Amos ___ squid-users mailing list squid-users@lists.squid-cache.org https://lists.squid-cache.org/listinfo/squid-users
Re: [squid-users] [ext] Re: Squid 6.4 assertion errors: FATAL: assertion failed: stmem.cc:98: "lowestOffset () <= target_offset" current master transaction: master655 (backtrace)]
> I'll add a "me too" to this. 6.3 reliable, 6.4 crashes and this is under > _very_ low load. NetBSD 9.3_STABLE. You can check the debugging recommendation in https://bugs.squid-cache.org/show_bug.cgi?id=5309 I'll try 6.4 on my test proxy now (with very low to no load at all), and will also try 7.0/master -- Ralf Hildebrandt Charité - Universitätsmedizin Berlin Geschäftsbereich IT | Abteilung Netz | Netzwerk-Administration Invalidenstraße 120/121 | D-10115 Berlin Tel. +49 30 450 570 155 ralf.hildebra...@charite.de https://www.charite.de ___ squid-users mailing list squid-users@lists.squid-cache.org https://lists.squid-cache.org/listinfo/squid-users
