On Friday 09 December 2016 22:16:42 Jonathan de Boyne Pollard wrote: > Rainer Dorsch: > > [ 20.704584] systemd[1]: Initializing machine ID from D-Bus machine ID. > > > > [ 20.916182] systemd-journald[2136]: Failed to open runtime journal: > > Invalid argument > > > > You need to look at at least two files, /var/lib/dbus/machine-id and > /etc/machine-id . They should contain only a 128-bit hexadecimal number > plus a newline, and this number must match the number used in the > directory names below /run/log/journal/ and /var/log/journal/ . >
Many thanks, Jonathan, I think that resolves the problem: root@scw:~# cat /var/lib/dbus/machine-id 26da2c29c6a545fd9af95d29ca9b5a5a root@scw:~# cat /etc/machine-id 26da2c29c6a545fd9af95d29ca9b5a5a 6df root@scw:~# Not sure how the 6df ended in /etc/machine-id, but after removing that things seem to have settled: root@scw:~# systemctl status ● scw State: degraded Jobs: 0 queued Failed: 1 units Since: Sat 2016-12-10 12:32:15 UTC; 1min 36s ago CGroup: / ├─user.slice │ └─user-0.slice │ ├─user@0.service │ │ └─init.scope │ │ ├─3816 /lib/systemd/systemd --user │ │ └─3824 (sd-pam) │ └─session-1.scope │ ├─3814 sshd: root@pts/0 │ ├─4508 -bash │ ├─4514 systemctl status │ └─4515 pager ├─init.scope │ └─1 /sbin/init └─system.slice ├─irqbalance.service │ └─3239 /usr/sbin/irqbalance --pid=/var/run/irqbalance.pid ├─dbus.service │ └─3161 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation ├─ssh.service │ └─3430 /usr/sbin/sshd -D ├─system-serial\x2dgetty.slice │ └─serial-getty@ttyS0.service │ └─3453 /sbin/agetty --keep-baud 115200,38400,9600 ttyS0 vt220 ├─ntp.service │ └─3804 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -c /run/ntp.conf.dhcp -u 104:108 ├─system-getty.slice │ └─getty@tty1.service │ └─3449 /sbin/agetty --noclear tty1 linux ├─systemd-logind.service │ └─3198 /lib/systemd/systemd-logind ├─cron.service │ └─3212 /usr/sbin/cron -f ├─apache2.service │ ├─3497 /usr/sbin/apache2 -k start │ ├─3505 /usr/sbin/apache2 -k start │ ├─3506 /usr/sbin/apache2 -k start │ ├─3507 /usr/sbin/apache2 -k start │ ├─3508 /usr/sbin/apache2 -k start │ └─3511 /usr/sbin/apache2 -k start ├─systemd-udevd.service │ └─2164 /lib/systemd/systemd-udevd ├─rsyslog.service │ └─3180 /usr/sbin/rsyslogd -n ├─networking.service │ └─3359 /sbin/dhclient -v -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases -I -df /var/lib/dhcp/dhclient6.eth0.leases eth0 ├─systemd-journald.service │ └─2142 /lib/systemd/systemd-journald ├─bind9.service │ └─3422 /usr/sbin/named -f -u bind └─exim4.service └─3801 /usr/sbin/exim4 -bd -q30m root@scw:~# systemctl status systemd-journald ● systemd-journald.service - Journal Service Loaded: loaded (/lib/systemd/system/systemd-journald.service; static; vendor preset: enabled) Active: active (running) since Sat 2016-12-10 12:32:16 UTC; 1min 47s ago Docs: man:systemd-journald.service(8) man:journald.conf(5) Main PID: 2142 (systemd-journal) Status: "Processing requests..." Tasks: 1 (limit: 4915) CGroup: /system.slice/systemd-journald.service └─2142 /lib/systemd/systemd-journald Dec 10 12:32:16 scw systemd-journald[2142]: Missed 152 kernel messages Dec 10 12:32:16 scw systemd-journald[2142]: Journal started Dec 10 12:32:16 scw systemd-journald[2142]: Runtime journal (/run/log/journal/26da2c29c6a545fd9af95d29ca9b5a5a) is 0B, max 0B, 0B free. Dec 10 12:32:16 scw systemd-journald[2142]: Runtime journal (/run/log/journal/26da2c29c6a545fd9af95d29ca9b5a5a) is 0B, max 0B, 0B free. Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable. root@scw:~# journalctl -u systemd-journald -e -b [...] -- Logs begin at Sat 2016-12-10 12:32:16 UTC, end at Sat 2016-12-10 12:34:07 UTC. -- Dec 10 12:32:16 scw systemd-journald[2142]: Missed 152 kernel messages Dec 10 12:32:16 scw systemd-journald[2142]: Journal started Dec 10 12:32:16 scw systemd-journald[2142]: Runtime journal (/run/log/journal/26da2c29c6a545fd9af95d29ca9b5a5a) is 0B, max 0B, 0B free. Dec 10 12:32:16 scw systemd-journald[2142]: Runtime journal (/run/log/journal/26da2c29c6a545fd9af95d29ca9b5a5a) is 0B, max 0B, 0B free. root@scw:~# I upgraded from a fresh jessie installation (image from scaleway, I did not install myself). Is it worthwhile to chase down the origin of the 6df or is this a known issue which should not affect the standard upgrade path from jessie to stretch? Kind regards Rainer -- Rainer Dorsch Lärchenstr. 6 72135 Dettenhausen 07157/734133