Thomas Klausner <tk%giga.or.at@localhost> writes: > On Tue, Apr 24, 2018 at 08:56:48AM +0100, Roy Marples wrote: >> Saying this, from what I'm hearing this only happens at boot time, so we >> could potentially shrink the buffer back down again if we need to consider >> dynamically growing it in the kernel as well. No idea if that's even >> possible or what performance impact it would have. > > I had an application report an UDP error with "no buffer space > available". I don't remember the exact error, sorry. But it was > definitely some time after system start. > Thomas I keep getting those, and have been for a long, long time: Apr 24 02:44:27 barsoom openvpn[301]: write UDPv4: No buffer space available (code=55) Apr 24 05:54:47 barsoom openvpn[292]: write UDPv4: No buffer space available (code=55) Apr 24 07:24:54 barsoom openvpn[292]: write UDPv4: No buffer space available (code=55) Apr 24 07:24:54 barsoom openvpn[292]: write UDPv4: No buffer space available (code=55) Apr 24 08:53:08 barsoom openvpn[292]: write UDPv4: No buffer space available (code=55) Apr 24 08:53:09 barsoom openvpn[292]: write UDPv4: No buffer space available (code=55) Apr 24 10:15:09 barsoom openvpn[305]: write UDPv4: No buffer space available (code=55) Apr 24 10:45:14 barsoom openvpn[305]: write UDPv4: No buffer space available (code=55) Apr 24 11:35:18 barsoom openvpn[305]: write UDPv4: No buffer space available (code=55) Apr 24 13:15:12 barsoom openvpn[305]: write UDPv4: No buffer space available (code=55) -tih -- Most people who graduate with CS degrees don't understand the significance of Lisp. Lisp is the most important idea in computer science. --Alan Kay
Attachment:
signature.asc
Description: PGP signature