[Pkg-dns-devel] Bug#826241: Bug#826241: Bug#826241: unbound: Provide $named facility under systemd

[Robert Edmonds]

Michael Biebl wrote:
> Am 03.06.2016 um 18:00 schrieb Robert Edmonds:
> > biebl at debian.org wrote:
> 
> > Basically, the combination of unbound (with a native .service file),
> > resolvconf, and postfix (and probably other packages that ship a
> > resolvconf update-libc.d hook) causes "systemctl start unbound.service"
> > to hang somehow.
> > 
> > Can the pkg-systemd team take a look at this interaction and recommend a
> > fix?
> > 
> 
> Honestly, that whole resolvconf shell glue looks quite aweful to me :-/

Yes :-(

> I wonder whether it would make sense to split that out into a separate
> service unit.

I also tried it with a separate unbound-resolvconf.service unit, but I
ran into the exact same situation, and importing the resolvconf stuff as
Exec{Start,Stop}Post= hooks in the main unbound.service was my attempt
at a workaround. Unfortunately I don't have good notes from the earlier
attempt, but I can try to re-create the situation.

(IIRC, I started by adapting the bind9-resolvconf.service from the bind9
package, but with the fix in #744304.)

> That said, could you try restarting postfix via
> "systemctl --no-block" in the resolvconf hook?

I *think* I did try this, and it did work. But this file is shipped by
postfix. Is this a bug in postfix (or resolvconf)? Do we need to audit
all the resolvconf hooks?

> Which version of systemd do you have installed?

This was a few weeks ago on testing VM that was up-to-date at the time.
It has the following versions:

    postfix     3.1.0-3
    resolvconf  1.78
    systemd     229-6
    unbound     1.5.8-1

> It's certainly possible that you run into a deadlock here if postfix
> depends on $named and $named indirectly via the resolvconf hook depends
> on postfix.

-- 
Robert Edmonds
edmonds at debian.org