Re: squid 5.1 gone stable

[Matthias Fischer <matthias.fischer@ipfire.org>]

[-- Attachment #1: Type: text/plain, Size: 3969 bytes --]

Hi,

On 06.08.2021 12:46, Michael Tremer wrote:
> Hi,
> 
>> On 5 Aug 2021, at 19:12, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>> 
>> Hi,
>> 
>> On 02.08.2021 18:39, Michael Tremer wrote:
>>> Hey,
>>> 
>>> That sounds good.
>>> 
>>> The change log lists a couple of changed and remove directives:
>>> 
>>>  http://www.squid-cache.org/Versions/v5/squid-5.1-RELEASENOTES.html#s3
>>> 
>>> Could you check if we are affected by any of this change?
>> 
>> 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.
>> 
>> But...:
>> 
>> 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:
>> 
>> ...
>> 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’s limit then. If the process is being launched as root, it should be able to change its own limits.

Yes. I think so. Its weird. 'squid 4.16' - running with *exactly* the
same configuration (under Core 158) - doesn't complain. Only '5.1'
won't. I'm searching.

>> 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’t have privoxy. Is that a custom thing that you are running?

Yes.
That one leftover from the old copfilter, ported to IFire. We once
talked about this... I rewrote it as an addon for IPFire. Its running
without any problems with the last 'squid 4.*' versions so far. But as
above, 'squid 5.1' somehow doesn't like it anymore. 'privoxy' is still
filtering and working, but I'm getting these complains from 'squid'. Hm.

Best,
Matthias

>> ...
>> 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
>> ...
>> 
>> Somehow I don't like this. Will report, if I find the reason.
>> 
>> Best,
>> Matthias
>> 
>> 
>>> -Michael
>>> 
>>>> On 2 Aug 2021, at 17:12, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> for the records...
>>>> 
>>>> 5.1 has gone stable:
>>>> 
>>>> => http://www.squid-cache.org/Versions/
>>>> 
>>>> Excerpt from changelog:
>>>> "Changes in squid-5.1 (01 Aug 2021):
>>>> 
>>>> 	- 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
>>>> 
>>>> Changes in squid-5.0.7 (04 Jul 2021):
>>>> 
>>>> 	- Fix a helper logging issues
>>>> 	- Fix some helper connection issues
>>>> 	- Cleanup: remove much unused code
>>>> 	- ... and all fixes from 4.16
>>>> ..."
>>>> 
>>>> I'm at it.
>>>> 
>>>> Best,
>>>> Matthias
>>>> 
>>> 
>> 
>