I upgraded one of my test systems (an armhf Cubox-i4Pro) to Sid. After rebooting, I saw the same symptoms as on the SheevaPlug.
I commented the line in question in /lib/systemd/system/systemd-logind.service and /lib/systemd/system/systemd-journald.service There was no corresponding line in /lib/systemd/system/networking.service so I did nothing there. I then did ‘update-initramfs -u’. Then I rebooted. Symptoms still persist, so that doesn’t seem to be it. I still have root@cube:~# systemctl status systemd-journald.service * systemd-journald.service - Journal Service Loaded: loaded (/lib/systemd/system/systemd-journald.service; static; vendor preset: enabled) Active: failed (Result: start-limit-hit) since Thu 2016-07-28 17:05:29 PDT; 8min ago Docs: man:systemd-journald.service(8) man:journald.conf(5) Main PID: 608 (code=exited, status=228/SECCOMP) Any other thoughts? Rick On Jul 28, 2016, at 2:04 PM, Michael Biebl <bi...@debian.org> wrote: > 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? >