No buffer space available error

[MrSnuggles]

Sorry for bothering you again.
I got an Error when the jail had a bit of traffic.

found a few threads and edited the sysctl config file via ssh.

https://forums.freenas.org/index.php?threads/transmission-error-udp-failed-to-set-receive-buffer-please-help.15203/

I have done the changes on my sysctl in the root directory, but then i couldn't boot anymore.

there is another way but all the things i found where for the old FreeNAS build or plain BSD:

net.inet.tcp.recvbuf_max
net.inet.tcp.sendbuf_max

Do you know how to get rid of it?

Thanks as always for your great work. Maybe i will contribute a few lines of code for stability and the ipfw feature in the next month when there is time.

[verisgit]

In the freenas control panel under System>Tunables add a new tunable
kern.ipc.maxsockbuf
5242880
type: sysctl

and

net.inet.udp.recvspace
4194304
type: sysctl

save and reboot

[Asday]

For future googlers, my FreeNAS jails all decided to become completely unreachable to and from the outside world, with no obvious error messages, until I tried to ping the default gateway and got:

PING 192.168.1.1 (192.168.1.1): 56 data bytes
ping: sendto: No buffer space available
ping: sendto: No buffer space available
ping: sendto: No buffer space available

Adding the tunables above and rebooting the host machine was what fixed it.

Not sure what caused the issue, but hey, bigger buffers fixed it, so I'm happy for now.

[Asday]

Further - kern.ipc.maxsockbuf was being overwritten by autotune, which, according to the god of FreeNAS cyberjock, probably shouldn't be used.

I've disabled autotune (system -> advanced), re-set the tunable to what I wanted it to be, and rebooted. If I don't post again, consider this The Fix:tm:.