From 14.3 to 15.0

I had no problems with updates sequentially from version 10.0 to 11.0 to 12.0 to 13.0, but problems started when updating from 13.0 to 14.0 and continue to this day.
 
sudo service unbound onestart
Password:
Obtaining a trust anchor...
Starting unbound.
[1764670749] unbound[2584:0] warning: setsockopt(..., SO_SNDBUF, ...) was not granted: No buffer space available
[1764670749] unbound[2584:0] warning: so-sndbuf 4194304 was not granted. Got 9216. To fix: start with root permissions(linux) or sysctl bigger net.core.wmem_max(linux) or kern.ipc.maxsockbuf(bsd) values. or set so-sndbuf: 0 (use system value).
[1764670749] unbound[2584:0] warning: setsockopt(..., SO_SNDBUF, ...) was not granted: No buffer space available
[1764670749] unbound[2584:0] warning: so-sndbuf 4194304 was not granted. Got 9216. To fix: start with root permissions(linux) or sysctl bigger net.core.wmem_max(linux) or kern.ipc.maxsockbuf(bsd) values. or set so-sndbuf: 0 (use system value).



service unbound status
unbound is running as pid 2585.
I'm getting the same problem or similar:
Code:
sudo service local_unbound restart
Password:
Stopping local_unbound.
Waiting for PIDS: 19704.
Starting local_unbound.
[1776146297] local-unbound[69940:0] warning: setsockopt(..., SO_SNDBUF, ...) was not granted: No buffer space available
[1776146297] local-unbound[69940:0] warning: so-sndbuf 4194304 was not granted. Got 9216. To fix: start with root permissions(linux) or sysctl bigger net.core.wmem_max(linux) or kern.ipc.maxsockbuf(bsd) values. or set so-sndbuf: 0 (use system value).
Waiting for nameserver to start... good
I don't know how this even arose. I was updating from 14.3p7 incrementally till 14.4p1. I did not upgrade any packages, but unbound package is not in the list of packages to be upgraded. How can I surgically resolve this?
 
Back
Top