From b24f6afe3cc97b6450c5abda92b3ea211b8770d0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Harald=20Jens=C3=A5s?= Date: Mon, 24 Feb 2025 16:09:44 +0100 Subject: [PATCH] OSPCIX-683 - Fix unbound.service startup error Unbound fails to start, error message: ``` unbound[1636]: [1636:0] 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. ``` Adding `chroot: ""` in the server section of unbound.conf fixes the issue. Jira: OSPCIX-683 --- .../files/elements/nat64-router/static/etc/unbound/unbound.conf | 1 + 1 file changed, 1 insertion(+) diff --git a/roles/nat64_appliance/files/elements/nat64-router/static/etc/unbound/unbound.conf b/roles/nat64_appliance/files/elements/nat64-router/static/etc/unbound/unbound.conf index b2ae4f5a72..5e23e3b2fb 100644 --- a/roles/nat64_appliance/files/elements/nat64-router/static/etc/unbound/unbound.conf +++ b/roles/nat64_appliance/files/elements/nat64-router/static/etc/unbound/unbound.conf @@ -2,6 +2,7 @@ include: "/etc/unbound/conf.d/*.conf" server: use-systemd: yes do-daemonize: no + chroot: "" do-not-query-localhost: no module-config: "dns64 validator iterator" interface: ::1