Bug#854814: Fails to start systemd-resolved

[Martin Pitt]

Control: tag -1 pending

Michael Biebl [2017-02-10 19:20 +0100]:
> Am 10.02.2017 um 17:49 schrieb Yuri D'Elia:
> > 
> > With the update to 232-17, systemd-resolved fails to start with the
> > following error:
> > 
> 
> > -- The error number returned by this process is 2.
> > Feb 10 17:46:31 test systemd[1]: systemd-resolved.service: Main process
> > exited, code=exited, status=226/NAMESPACE
> > Feb 10 17:46:31 test systemd[1]: Failed to start Network Name Resolution.
> > -- Subject: Unit systemd-resolved.service has failed
> 
> This is caused by the addition of ReadWritePaths= in
> 
> /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf
> 
> I guess this should only be used in addition with ProtectSystem=, which
> is a recent upstream change but the Debian version does not use that yet.

No, I did test it with our current systemd package and it worked. However, I
apparently only tested it with resolvconf installed, but not without
resolvconf. Trivial fix, pushed:

  https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=030866cf7d3

Sorry for the trouble!

Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20170211/e4bb90a8/attachment.sig>