From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] squid: Update to 4.4 (stable)
Date: Fri, 21 Dec 2018 15:28:29 +0100 [thread overview]
Message-ID: <E43B07E1-DAA4-446B-A6EF-94AFE1E74691@ipfire.org> (raw)
In-Reply-To: <76d5c380-d4e5-f053-6d92-630affd8f4cc@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 3133 bytes --]
Hey,
> On 20 Dec 2018, at 21:05, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>
> Hi,
>
> On 19.12.2018 18:54, Matthias Fischer wrote:
>> On 19.12.2018 18:46, Michael Tremer wrote:
>>> Hi,
>>>
>>>> On 19 Dec 2018, at 17:45, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>>>>
>>>> Hi Michael,
>>>>
>>>> On 19.12.2018 17:10, Michael Tremer wrote:
>>>>> Sorry from me as well for overlooking that.
>>>>
>>>> No problem... ;-)
>>>>
>>>>> Merged and the nightly build ran through…
>>>>
>>>> Ok, thanks for the feedback - in between I thought there were still
>>>> mistakes in it. That d*** "binary blob" came from my installation
>>>> archive - I forgot to delete it *twice* before pushing! Duh! Now I'm
>>>> using a dedicated 'upload'-directory for these archives, so this won't
>>>> happen again…
>>>>
>>> No worries. Shit happens.
>>>
>>>> On my production machine this build is running without any errors since
>>>> then.
>>>
>>> Good. I will install this as soon as possible. I still don’t quite believe that nothing in the configuration has to be changed.
>>
>> 'squid - k parse' never showed any errors and the GUI didn't make any
>> problems until now. We'll see.
>>
>>> We still have Daniel’s patch that hasn’t been integrated. Do you have time to look into that again, too? I forget where that got stuck…
>>
>> I can do that - its running here - work in progress. ;-)
>
> I fear I've found ONE problem with Daniel's patch and the
> 'queue-size'-option, so I'd prefer to alter the 'queue-size'-value from
> '64' to '128’.
Hmm, 64 was just a guess. That’s definitely debatable.
> With 'queue-size=64' I got these errors again today:
>
> ...
> 2018/12/20 11:17:49 kid1| comm_udp_sendto FD 8, (family=2) 127.0.0.1:53:
> (1) Operation not permitted
> 2018/12/20 11:17:49 kid1| idnsSendQuery FD 8: sendto: (1) Operation not
> permitted
> 2018/12/20 11:17:54 kid1| comm_udp_sendto FD 8, (family=2) 127.0.0.1:53:
> (1) Operation not permitted
> 2018/12/20 11:17:54 kid1| idnsSendQuery FD 8: sendto: (1) Operation not
> permitted
> 2018/12/20 11:18:04 kid1| comm_udp_sendto FD 8, (family=2) 127.0.0.1:53:
> (1) Operation not permitted
> 2018/12/20 11:18:04 kid1| idnsSendQuery FD 8: sendto: (1) Operation not
> permitted
> ...
>
> They happen even without any DNS rules - perhaps the '64' is too small!?
This is just a problem resolving the hostname. Either that is because there is a firewall rule that blocks port 53 (unlikely) or unbound hits a limit of maximum number of requests per host. In that case we probably need to adjust that.
You should be able to trace that with tcpdump:
tcpdump -i lo port 53 -nn
There is probably TCP reset packets (with an R in the square brackets).
> With '128' I don't see them. Any thoughts?
If my theory above this true, this does not make much sense. So either I am wrong or this changes some other behaviour too. No matter how long the queue, the number of requests processed at a time should be the same.
Best,
-Michael
>
> Best,
> Matthias
next prev parent reply other threads:[~2018-12-21 14:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <36903BA6-7CA8-46E0-9670-304583696FA1@ipfire.org>
2018-12-19 17:54 ` Matthias Fischer
2018-12-20 20:05 ` Matthias Fischer
2018-12-21 14:28 ` Michael Tremer [this message]
[not found] <20181213173224.11553-1-matthias.fischer@ipfire.org>
2018-12-17 17:19 ` Michael Tremer
2018-12-17 18:52 ` Matthias Fischer
2018-12-19 16:10 ` Michael Tremer
2018-12-13 17:40 Matthias Fischer
-- strict thread matches above, loose matches on Subject: below --
2018-11-04 7:09 Matthias Fischer
2018-11-09 15:22 ` Michael Tremer
2018-11-09 18:56 ` 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=E43B07E1-DAA4-446B-A6EF-94AFE1E74691@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