Unbound service fails with fatal error- "sd_notify failed /run/systemd/notify: No such file or directory. Make sure that unbound has access/permission to use the socket".
Issue
-
On
RHEL 9.6systems, after updating theUnboundpackage, the service fail to start with the following error:fatal error: sd_notify failed /run/systemd/notify: No such file or directory
Environment
- Red Hat Enterprise Linux 9.6
- unbound-1.16.2-17.el9
- unbound-libs-1.16.2-17.el9
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
