Nicolas Braud-Santoni wrote:
> Hi,
>
> I can confirm that this issue prevents systemd from detecting Unbound failing
> - either at startup (for instance due to bad configuration);
> - while running;
> - because it was stopped with unbound-control.
>
>
> Could you expand a bit on what is
Hi,
> Thank you for this follow-up, up until now I had thought this behavior
> could only be triggered when using "unbound-control" to stop unbound.
>
> Could you try using the "very basic native unbound.service unit file"
> from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807132#10 as a
>
Matthew Vernon wrote:
> I have unbound & systemd on a jessie system, and every time there's an
> update to unbound, it ends up not running. I /think/ it's this bug
> biting us, but I'm not entirely sure.
>
> For instance, we recent upgraded to 1.4.22-3+deb8u1 and unbound was no
> longer running.
3 matches
Mail list logo
