Unbound: fatal error: Could not read config file: /unbound.conf

[myman]

Hi there,
I have a problem where I sometimes wake up to unbound not running any more. I'm having that problem for some years now. I occures from once a month to once a week. When I then go to Status -> Services, I can see unbound being stopped. Clicking on Start Service makes it work for some days/weeks again.

Unbound log: unbound.txt

unbound-checkconf returns unbound-checkconf: no errors in /usr/local/etc/unbound/unbound.conf

What I don't understand is why unbound restarts every couple of minutes. My WAN interface is PPPoE and has it's custom reset a 5AM, maybe that triggers it.

Here's my config:

Generally I have quite a simple setup, so no VPN, no QoS, no pfblocker. Also I use Pihole as my main DNS server and unbound only resolves the local hosts

[fireodo]

@myman

Disable that and you'll be fine.

Regards,
fireodo

[myman]

@fireodo Thanks, I'll give it a try. I don't think I ever used that feature anyway

[Gertjan]

@myman said in Unbound: fatal error: Could not read config file: /unbound.conf:

unbound-checkconf returns unbound-checkconf: no errors in /usr/local/etc/unbound/unbound.conf

Runing " unbound-checkconf" will check the default /usr/local/etc/unbound/unbound.conf, a file that exists, but it is just a demo file.
The real "unbound.conf", the one unbound for pfSense is using, is here/var/unbound/

Your unbound is restating every couple of minutes.
If these restarts happen to often, then the start code can overlap with another startup. Then one of then can fail and you see the error shown.

Disabling "DHCP registration" is one of the first things to try.