What buffer space is related to "sendto failed: No buffer space available" log entries?

nusenu nusenu-lists at riseup.net
Tue Jan 8 19:27:00 UTC 2019

Hi Wouter,

thanks for your reply.

Wouter Wijngaards via Unbound-users:
> What I think happens is that this is so-sndbuf for UDP packets, and the
> so-sndbuf option solves it.  But you already use that so I do not know
> any further.  

I increased so-sndbuf to as far as 12m but the issue persists.

> Where you could look further is in the sendto(2) system
> call documentation, for UDP packets, when it gives this ENOBUFS error
> code.  The FreeBSD documentation suggest two causes for this error code,
> one it that there was not enough memory for a buffer

is this exclusively about so-sndbuf or potentially also about other buffers?

>, and the second
> that the network interface has stopped sending and it is full.

since both cases have the same error message (ENOBUFS) I guess
there is no way to tell these cases apart, right?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.nlnetlabs.nl/pipermail/unbound-users/attachments/20190108/bee5989f/attachment.bin>

More information about the Unbound-users mailing list