Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

[Michael Biebl]

Am 28.07.2016 um 22:50 schrieb Rick Thomas:
> In the interest of having a working system, I reverted that machine to systemd version 230-7.  Unsurprisingly, the problem went away.
> 
> I’ll try re-installing 231-1 and commenting that line.  I’ll probably have a chance tonight.  I’ll report when I have something.
> 
> It may be worth noticing that other things failed as well when 231-1 was in.  I’m attaching a ‘grep -i fail -C20’ of the screen log.  Of particular note are “Failed to start Raise network interfaces” and “Failed to start Login Service.”
> 
> Are there other places where I should remove a “SystemCallFilter” ?
> 

Various units were locked down like e.g. in
https://github.com/systemd/systemd/commit/4e069746fe0de1f60bd1b75c113b0f40ffe86736

If the SystemCallFilter= is what causes journald to fail, it's likely it
also affects those other services.

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: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20160728/6d9893b6/attachment-0002.sig>