Linux, "failed to sufficiently increase receive buffer size"

Just noting a following observation. I’ve got a following warning in the logs after restarting a node:

2021-03-27T13:37:10.784Z        INFO    failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/lucas-clemente/quic-go/wiki/UDP-Receive-Buffer-Size for details. 

The linked webpage suggests:

It is recommended to increase the maximum buffer size by running:

sysctl -w net.core.rmem_max=2500000

This command would increase the maximum receive buffer size to roughly 2.5 MB.

I suspect that the impact of not changing this setting is minimal, but SNOs might want to take attention.

this is part of a new feature that afaik isn’t implemented yet.
so it can be safely ignored.

Yes, at the moment it’s not required, but you can fix this issue as recommended. It will not hurt your system or storagenode. But when the time is to come - your setup will be ready.

1 Like

Does sysctl -w net.core.rmem_max=2500000 survive a reboot?

You need to put line into /etc/sysctl.conf
net.core.rmem_max=2500000

Now it will apply setting after every reboot.

Edit: -w option should make it permanently.
Source https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/managing_monitoring_and_updating_the_kernel/configuring-kernel-parameters-at-runtime_managing-monitoring-and-updating-the-kernel

I have done this, but the error is still there.

1 Like

did you also open a udp port on the same port number as the storj node tcp port …

you will need that also.

and ofc routed to the same ip …

Добрый день! Открыл порт UDP… выполнил команду под root доступом sysctl -w net.core.rmem_max=2500000 на Synology RS 2416+. Тест - ОК. (Ошибка : INFO failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB) - отсутствует).
:wink: