From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: squid 5.1 gone stable
Date: Fri, 06 Aug 2021 12:46:49 +0200 [thread overview]
Message-ID: <991A5EE5-F2D6-4DC1-9A8A-D2DD7F2AA08C@ipfire.org> (raw)
In-Reply-To: <3229c4dc-fa5a-6ebc-825b-3f8bb39b8109@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 3258 bytes --]
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.
> 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?
> ...
> 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
>>>
>>
>
next prev parent reply other threads:[~2021-08-06 10:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 16:12 Matthias Fischer
2021-08-02 16:39 ` Michael Tremer
2021-08-05 17:12 ` Matthias Fischer
2021-08-06 10:46 ` Michael Tremer [this message]
2021-08-06 17:55 ` Matthias Fischer
2021-08-07 8:40 ` Matthias Fischer
2021-08-07 16:13 Matthias Fischer
2021-08-13 9:22 ` Michael Tremer
2021-08-15 7:53 ` Matthias Fischer
2021-08-16 9:40 ` Michael Tremer
2021-08-18 16:42 ` Matthias Fischer
2021-08-19 13:57 ` Michael Tremer
2021-08-19 16:32 ` Matthias Fischer
2021-08-23 13:29 ` Michael Tremer
2021-08-23 16:25 ` Matthias Fischer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=991A5EE5-F2D6-4DC1-9A8A-D2DD7F2AA08C@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox