Robert Edmonds wrote:
> Hi,
>
> After looking into this problem some more, I think the minimal fix for
> jessie is going to look something like a drop-in that overrides the bad
> values from systemd-sys-generator. Any chance anyone following this bug
> report could test the following drop-in?
There's a very important step missing in the text below, which is to
install the postfix package between steps 5 and 6. Sorry about that.
Robert Edmonds wrote:
> I've attached the unbound.service unit file that I've been working on
> that ports the functionality from the sysvinit script. I can
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
Control: found -1 1.5.8-1~bpo8+1
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 required, re:
Matthew Vernon wrote:
> Yep. Without that service file, service unbound restart fails to restart
> unbound.
>
> With that service file installed, service unbound restart behaves as
> expected.
>
> So I do think rolling this out to jessie would be good :)
Thanks for the confirmation.
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.
On 18.04.2016 13:07, 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.
> Is it plausible that this is caused by this bug? If so, a jessie
Hi,
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. daemon.log output:
Apr 18
9 matches
Mail list logo
