From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: squid 5.1 gone stable Date: Fri, 06 Aug 2021 12:46:49 +0200 Message-ID: <991A5EE5-F2D6-4DC1-9A8A-D2DD7F2AA08C@ipfire.org> In-Reply-To: <3229c4dc-fa5a-6ebc-825b-3f8bb39b8109@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4267780644476651487==" List-Id: --===============4267780644476651487== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, > On 5 Aug 2021, at 19:12, Matthias Fischer w= rote: >=20 > Hi, >=20 > On 02.08.2021 18:39, Michael Tremer wrote: >> Hey, >>=20 >> That sounds good. >>=20 >> The change log lists a couple of changed and remove directives: >>=20 >> http://www.squid-cache.org/Versions/v5/squid-5.1-RELEASENOTES.html#s3 >>=20 >> Could you check if we are affected by any of this change? >=20 > Building was ok - installing was ok. I checked the release notes and on > the first glance didn't find anything we would need to worry about. Will > take a closer look on weekend. >=20 > But...: >=20 > 5.1 is permanently complaining about filedescriptors and I couldn't find > the reason for this so far. Even if I reduce the number during build to > 32768 (this is supposedly his maximum), it keeps complaining: >=20 > ... > 2021/08/03 19:19:03 kid1| NOTICE: Could not increase the number of > filedescriptors > 2021/08/03 19:19:03 kid1| With 4096 file descriptors available > ... That must be the system=E2=80=99s limit then. If the process is being launche= d as root, it should be able to change its own limits. > And - it seems that it doesn't like 'privoxy'. Everything seems to > work(!), no seen problems(!), but with 'squid 5.1' I'm getting these > sporadic messages in 'cache_log': We don=E2=80=99t have privoxy. Is that a custom thing that you are running? > ... > 2021/08/03 19:27:17 kid1| helperOpenServers: Starting 2/4 > 'redirect_wrapper' processes > current master transaction: master88 > 2021/08/03 19:27:33 kid1| TCP connection to 127.0.0.1/8118 failed > current master transaction: master53 > 2021/08/03 19:27:34 kid1| TCP connection to 127.0.0.1/8118 failed > current master transaction: master53 > 2021/08/03 19:27:56 kid1| TCP connection to 127.0.0.1/8118 failed > current master transaction: master53 > ... > 2021/08/03 19:59:34 kid1| TCP connection to 127.0.0.1/8118 failed > current master transaction: master53 > 2021/08/03 19:59:34 kid1| Detected DEAD Parent: privoxy > current master transaction: master53 > 2021/08/03 19:59:34 kid1| Detected REVIVED Parent: privoxy > current master transaction: master53 > 2021/08/03 19:59:34 kid1| TCP connection to 127.0.0.1/8118 failed > current master transaction: master53 > ... >=20 > Somehow I don't like this. Will report, if I find the reason. >=20 > Best, > Matthias >=20 >=20 >> -Michael >>=20 >>> On 2 Aug 2021, at 17:12, Matthias Fischer = wrote: >>>=20 >>> Hi, >>>=20 >>> for the records... >>>=20 >>> 5.1 has gone stable: >>>=20 >>> =3D> http://www.squid-cache.org/Versions/ >>>=20 >>> Excerpt from changelog: >>> "Changes in squid-5.1 (01 Aug 2021): >>>=20 >>> - Bug 4696: Fix leaky String move assignment operator >>> - Fix ACL-related reconfiguration memory leak >>> - Fix SSL-Bump reconfiguration leaking public key memory >>> - Fix build on RISC-V >>> - Fix build on Ubuntu 21.04 >>>=20 >>> Changes in squid-5.0.7 (04 Jul 2021): >>>=20 >>> - Fix a helper logging issues >>> - Fix some helper connection issues >>> - Cleanup: remove much unused code >>> - ... and all fixes from 4.16 >>> ..." >>>=20 >>> I'm at it. >>>=20 >>> Best, >>> Matthias >>>=20 >>=20 >=20 --===============4267780644476651487==--