tech-net archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: squid on 9.2: No buffer space available



On Fri, 11 Feb 2022, Michael van Elst wrote:
netbsd%precedence.co.uk@localhost (Stephen Borrill) writes:

As an aside, I have seen similar messages when trying to do a UDP
bandwidth test with netio.

That's regular BSD behaviour. When you send packets faster than
you can emit on the wire, buffers of any size run full and you
get ENOBUFS.

On other systems, such packets may be silently dropped (they could
be dropped silently on the network path anyway).

The correct way to handle this is to rate limit UDP packets in the
application or even to implement some kind of flow control in the
application.

Squid implements 'delay pools' for rate limiting, I'm not sure
if that also applies to the UDP traffic between caches.

https://wiki.squid-cache.org/Features/DelayPools

Another way might be to move away from ICP (UDP based) to other
cache protocols.

Squid can also do logging via UDP, the configuration there seems
to have its own "buffer-size" option.

This isn't to do with neighbour caches, the messages suggest it is DNS:

comm_udp_sendto FD 22, (family=2) 127.0.0.1:53: (55) No buffer space available
idnsSendQuery FD 22: sendto: (55) No buffer space available

I think this is consistent with the symptoms I had reported to me (in a rather vague way) as I could not get an established connection (e.g. playing a YouTube video) to go wrong, but users were reporting "intermittent internet".

--
Stephen



Home | Main Index | Thread Index | Old Index