On 2025/12/19 17:26, Otto Cooper wrote: > Side note... > > > doas unbound-checkconf > unbound-checkconf: no errors in /var/unbound/etc/unbound.conf > > Yeah, no errors in that file, nor in local.unbound, but why didn't > unbound-checkconf complain about file ownership instead of wasting my day > chasing the dog's tail?
Probably because you're running it as root. > > In all my openbsd servers, local.unbound has the same ownership and > > permissions. > > > > Setting this file's ownership to _unbound solved the problem with reloading. > > > > -rw-r----- 1 _unbound wheel 3484 Aug 11 2020 local.unbound That is not from OpenBSD, it's your own local configuration file. > > In summary, to solve this problem, I had to make the following two changes > > to openbsd's base installation of unbound: > > > > In /etc/login.conf > > > > > unbound:\ > > > :openfiles-max=8192:\ > > > :tc=daemon: optional; the default 512 is a bit low for anything more than a small forwarding for a machine or two but 8k probably a bit much; I usually go for 4k or so > > Dec 19 17:48:49 unbound[55896:0] warning: setsockopt(..., SO_SNDBUF, ...) > > was not granted: No buffer space available > > Dec 19 17:48:49 unbound[55896: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). that (sndbuf) is irrelevant on OpenBSD, we don't have a buffer for that, it just limits the size of a single packet. unbound on -current will no longer warn about that. you should be able to set "so-sndbuf: 0" if you want the warning to go away.
