You are not logged in.
Hello Forums!
I patched my Arch systems the other night and discovered my unbound DNS would not start.
Error was: fatal error: sd_notify failed /run/systemd/notify: No such file or directory. Make sure that unbound has access/permission to use the socket presented by systemd (as seen with journcalctl -f)
Running unbound as root from the command line worked. systemctl start unbound did not.
I have reinstalled an old /lib/systemd/system/unbound.service file (shown below) and was able to get systemd to start unbound successfully. This one is quite a bit different than the new service file. I'm not done isolating the issue - but thought I would post this on the off chance it would help someone's DNS to get going.
my own /lib/systemd/system/unbound.service file ( must systemctl reload-daemon after editing)
[Unit]
Description=Unbound DNS Resolver
Wants=nss-lookup.target
Before=network-online.target nss-lookup.target
After=network.target
[Service]
ExecStart=/usr/bin/unbound
ExecReload=/bin/kill -HUP $MAINPID
Restart=always
[Install]
WantedBy=multi-user.targetLast edited by virtualperson72 (2019-09-18 04:52:03)
Arch | AMD Ryzen 5 1400 | AMD Radeon RX 480 | 8 GBytes RAM | XFCE | Zen Kernel
Offline
Goodevening,
I had the same problem.
When compare files in /etc/unbound, I saw new option absent in my unbound.conf.
$ diff unbound.conf.pacnew unbound.conf
2c2
< chroot: ""
...
I add this line in my unbound.conf and restart the service.
No problem anymore.
Regards,
Last edited by cqknard (2019-09-17 17:48:50)
Offline
Offline
CQ - your chroot method works perfectly (better than my old config) - and is of course hinted at by the unbound.conf.pacnew file which I should have seen anyway.
Thanks for your post.
Arch | AMD Ryzen 5 1400 | AMD Radeon RX 480 | 8 GBytes RAM | XFCE | Zen Kernel
Offline