Tuesday, April 29, 2025

Re: unbound EAGAIN sendto errors

On Tue, 29 Apr 2025 17:23:34 +0200,
Kapetanakis Giannis <bilias@edu.physics.uoc.gr> wrote:
>
> On 29/04/2025 18:11, Otto Moerbeek wrote:
> > On Tue, Apr 29, 2025 at 04:32:01PM +0300, Kapetanakis Giannis wrote:
> >
> >> Can it be related to this: dropped due to no socket?
> > IIRC OpenBSD does handle sending to a non-blocking socket in the
> > multi-threaded case very well. If multiple threads try to do that
> > simulteneously, some of them will get a EAGAIN. To test this
> > hypothesis, try running with a single thread and see if the errors
> > disappear.
> >
> > -Otto
>
> I did run one-thread and the errors where gone...
>
> ok, how I can we go to multiple threads now without the errors?
>
> Even with the one thread i still get dropped due to no socket on netstat
>

Keep in mind that unboud marks upstream as broken for a while.

See infra-keep-probing, and probably infra-cache-max-rtt and infra-host-ttl

Also, it has a maximal queue, see wait-limit, and it discards query if it in
the queue longer than discard-timeout.

Probably it has more options which may be needed to adjusted.


--
wbr, Kirill

No comments:

Post a Comment