FS#70429 - [unbound] sd_notify failed /run/systemd/notify: No such file or directory
Attached to Project:
Community Packages
Opened by Stefan Soellner (stesoell) - Tuesday, 13 April 2021, 14:06 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 04 May 2021, 06:33 GMT
Opened by Stefan Soellner (stesoell) - Tuesday, 13 April 2021, 14:06 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 04 May 2021, 06:33 GMT
|
Details
Description:
Startup fails when unbound is chrooted outside /etc/unbound. "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." due to settings in unbound.service It was fixed in: https://bugs.archlinux.org/task/63802 unbound -V Version 1.13.1 Thank you. |
This task depends upon
Comment by
Michel Koss (MichelKoss1) -
Tuesday, 13 April 2021, 18:49 GMT
Comment by
Stefan Soellner (stesoell) -
Tuesday, 13 April 2021, 19:35 GMT
Do you mean you changed chroot dir by yourself? You have to adjust
the systemd service then. The provided one works only with
/etc/unbound and it's not possible to support arbitrary chroot
path.
You're right. Thanks for your assistance.