Transmission error UDP failed to set receive buffer.. please help

Lightperfect

Dabbler
Joined
Sep 16, 2013
Messages
49
Dear all:
been researching for the answers on this error

UDP failed to set receive buffer: No buffer space available (tr-udp.c:58)
UDP failed to set receive buffer: requested 4194304, got 42080 (tr-udp.c77)

and below is the earlier post from freenas forum in year 2011

i dont know if works or not... dont really know how to mess with the shell..
could someone please give a step by step guide?


The buffer errors seem to be a problem caused by Transmission.
Transmission requires 4MB UDP buffer, whereas FreeNAS's default UDP buffer is small like 42080.

To fix this problem,

mount -uw /
vi /conf/base/etc/sysctl.conf

Append two lines below to the end of the file.

Code (text):
  1. kern.ipc.maxsockbuf=5242880
  2. net.inet.udp.recvspace=4194304
You won't see the buffer errors anymore.

Done!

I forgot to mention this, reboot your NAS. :)


Edited /base/conf/etc/sysctl.conf -> /conf/base/etc/sysctl.conf
Thanks jfr!
 
D

dlavigne

Guest
You can now set these in the GUI using Sysctls. For example, to set the first one, input kern.ipc.maxsockbuf into the variable field and 5242880 in the value field.
 

Lightperfect

Dabbler
Joined
Sep 16, 2013
Messages
49
You can now set these in the GUI using Sysctls. For example, to set the first one, input kern.ipc.maxsockbuf into the variable field and 5242880 in the value field.
thanks so much for the instruction. the error is gone.
 

fizassist

Cadet
Joined
Aug 20, 2017
Messages
5
Sorry to bump an old thread, but I thought it was worth noting that this error still occurred for me in 11.0-U2, and can be fixed by putting the variables in the original post in "System/Tunables" as sysctls.
 

PDM

Dabbler
Joined
Dec 17, 2011
Messages
24
Sorry to bump an old thread, but I thought it was worth noting that this error still occurred for me in 11.3-U3.1, and can be fixed by putting the variables in the original post in "System/Tunables" as sysctls.

#Apologies for Copying and Pasting the post above.

I believe I had always had this issue. Only due to another issue had I looked at the log files.
 
Top