Okay. I have now gone through a dpkg -i install of all the (non dbgsym) .deb I see on your server, and also issued a reboot for good measure, but I still see the same problem with journald being failed, along with dependent services

---------------------------------------------------------------------
root@pi ~ # systemctl start systemd-journald.service
Job for systemd-journald.service failed because the control process exited with error code. See "systemctl status systemd-journald.service" and "journalctl -xe" for details.
root@pi ~ # 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 Fri 2016-08-12 17:17:12 IST; 5s ago
     Docs: man:systemd-journald.service(8)
           man:journald.conf(5)
Process: 1560 ExecStart=/lib/systemd/systemd-journald (code=exited, status=228/SECCOMP)
 Main PID: 1560 (code=exited, status=228/SECCOMP)
root@pi ~ # systemctl --failed
  UNIT                            LOAD   ACTIVE SUB    DESCRIPTION
● systemd-journald.service        loaded failed failed Journal Service
● systemd-logind.service          loaded failed failed Login Service
● systemd-networkd.service        loaded failed failed Network Service
● systemd-resolved.service loaded failed failed Network Name Resolution ● systemd-journald-dev-log.socket loaded failed failed Journal Socket (/dev/log)
● systemd-journald.socket         loaded failed failed Journal Socket
● systemd-networkd.socket loaded failed failed Network Service Netlink Socket

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.

7 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
---------------------------------------------------------------------

One thing I still notice on the download server is that there exists a 'systemd-journal-remote-dbgsym_231-2_armhf.deb' but no 'systemd-journal-remote_231-2_armhf.deb'. There's also no 'systemd-sysv' despite being listed in the .dsc. Maybe those .deb's are still missing?

Regards,

/Pete

Reply via email to