You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
each times i start/restart unbound i get this warning:
unbound[33389]: [XXXXXXX] unbound[XXXXX:0] warning: Systemd mandatory ENV variable is not defined: LISTEN_PID
this due to the absence of the line DefaultEnvironment in /usr/lib/systemd/system/unbound.service
if am correct what should i have to add at DefaultEnvironment= ????
regards
The text was updated successfully, but these errors were encountered:
This happens because you have the option 'use-systemd: yes' enabled. This uses socket activation, it is where traffic on a socket makes systemd spawn the server. But then unbound starts but can not find the socket passed.
So not with the option you cite, that sets environment variables, but won't pass the socket.
If you do not want to use socket activation, you can set use-systemd: no in unbound.conf (the default).
Unbound also supports the use of sd_notify, and this is controlled by a compile time option. You have this option enabled, compile with systemd support.
each times i start/restart unbound i get this warning:
unbound[33389]: [XXXXXXX] unbound[XXXXX:0] warning: Systemd mandatory ENV variable is not defined: LISTEN_PID
this due to the absence of the line
DefaultEnvironment
in /usr/lib/systemd/system/unbound.serviceif am correct what should i have to add at DefaultEnvironment= ????
regards
The text was updated successfully, but these errors were encountered: