Bug#854814: Fails to start systemd-resolved

[Michael Biebl]

Am 10.02.2017 um 17:49 schrieb Yuri D'Elia:
> Package: systemd
> Version: 232-17
> Severity: normal
> 
> 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 

Slightly related:

Martin, what do you think about adding an autopkgtest which starts all
daemons (manually) that are shipped by systemd, no matter whether it is
enabled or not, and simply checks the return code of the start attempt.
(we can of course add more elaborate checks to test whether the service
is functional, but a successful start is the baseline)

With the recent changes upstream to enable more sandboxing features,
this could be helpful, I guess.

Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20170210/33f60c4a/attachment-0002.sig>