Caddy warning failed to sufficiently increase receive buffer size

[szaimen]

Info Failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Receive-Buffer-Size for details.

If you see a warning like this, you have to increase the maximum buffer size on your host machine (outside docker).

Solution

• Increase net.core.rmem_max:
  • echo "net.core.rmem_max = 7500000" | sudo tee /etc/sysctl.d/nextcloud-aio-buffer-increase.conf should be set, to increase buffer size on reboot, change will apply after reboot or see the line below how to activate it temporary without reboot
  • sysctl "net.core.rmem_max=7500000" enables buffer size increase on-the-fly temporary, then restart Nextcloud AIO from the AIO Interface
• Increase net.core.wmem_max:
  • echo "net.core.wmem_max = 7500000" | sudo tee /etc/sysctl.d/nextcloud-aio-buffer-increase.conf should be set, to increase buffer size on reboot, change will apply after reboot or see the line below how to activate it temporary without reboot
  • sysctl "net.core.wmem_max=7500000" enables buffer size increase on-the-fly temporary, then restart Nextcloud AIO from the AIO Interface

Note for Docker Desktop instances: See https://stackoverflow.com/a/69294687 for how to apply sysctl config values.

Background

Due to the fact that (for good reasons) the Apache container does not run in privileged mode, there is no way that Nextcloud AIO or Caddy can enable this for you, i.e., /proc is read-only for containers.

See quic documentation.

[Zoey2936]

It seems that instead of rebooting the system, running sysctl -p is enough

[pacbidouandco]

hi, i have the same problem, despite the solution, it s always down

can you help me

my log

2023-02-27T04:10:48.420832553Z Waiting for Nextcloud to start...
2023-02-27T04:10:53.423180920Z Waiting for Nextcloud to start...
2023-02-27T04:10:58.425960574Z Waiting for Nextcloud to start...
2023-02-27T04:11:03.428358036Z Waiting for Nextcloud to start...
2023-02-27T04:11:08.430588905Z Waiting for Nextcloud to start...
2023-02-27T04:11:13.432951581Z Waiting for Nextcloud to start...
2023-02-27T04:11:18.435493703Z Waiting for Nextcloud to start...
2023-02-27T04:11:23.437815753Z Waiting for Nextcloud to start...
2023-02-27T04:11:28.440302208Z Waiting for Nextcloud to start...
2023-02-27T04:11:33.442724031Z Waiting for Nextcloud to start...
2023-02-27T04:11:38.445194180Z Waiting for Nextcloud to start...
2023-02-27T04:11:43.447550775Z Waiting for Nextcloud to start...
2023-02-27T04:11:48.450017417Z Waiting for Nextcloud to start...
2023-02-27T04:11:53.452409225Z Waiting for Nextcloud to start...
2023-02-27T04:11:58.454636921Z Waiting for Nextcloud to start...
2023-02-27T04:12:04.760351694Z [Mon Feb 27 04:12:04.759955 2023] [mpm_event:notice] [pid 415:tid 281473443692632] AH00489: Apache/2.4.55 (Unix) configured -- resuming normal operations
2023-02-27T04:12:04.761202812Z [Mon Feb 27 04:12:04.761046 2023] [core:notice] [pid 415:tid 281473443692632] AH00094: Command line: '/usr/local/apache2/bin/httpd -D FOREGROUND'
2023-02-27T04:12:04.764137322Z {"level":"info","ts":1677471124.7639444,"msg":"using provided configuration","config_file":"/Caddyfile","config_adapter":""}
2023-02-27T04:12:04.769498984Z {"level":"info","ts":1677471124.7693384,"msg":"failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Receive-Buffer-Size for details."}

im french boy, sorry for my bad english

[szaimen]

I think I might have made a typo. Can you try this and restart the AIO containers?
echo "net.core.rmem_max = 2500000" | sudo tee /etc/sysctl.d/nextcloud-aio-buffer-increase.conf

[Zoey2936]

Either a reboot or running sysctl -p is also required for this change to take effect

[pacbidouandco]

thanks for your help,

now, after reboot, aio master conteners only restarting with "you should be able to fix this by adding the '--dns="ip.adress.of.the.dns.server" option to the docker run command

but aio apache is healthy now

[szaimen]

Possibly see #2065

[pacbidouandco]

hi,
thanks very very much, it's work fine now with your solution

Great job, very very nice

[nuschpl]

Hello regarding `the Apache container does not run in privileged mode, there is no way that Nextcloud AIO or Caddy can enable this for you'
what's the problem with using sudo at installation time? Same way as docker?

[nerlins]

Note for Docker Desktop instances: See https://stackoverflow.com/a/69294687 for how to apply sysctl config values.

This is not working on WSL2 on my machine. I have followed exactly, but keep getting the error for resizing the buffer.