miabbott added a new comment to an issue you are following:
``
I booted up an F28AH in Digital Ocean and started to look around.
There's definitely a journal file present, but I'm not sure why the
`systemd-journald` service isn't reading it.
```
[root@fedoraatomic-s-1vcpu-1gb-nyc1-01 ~]# ls -latr
/var/log/journal/4eddc7982ffd4847a32ecd3f6d3170d7/
total 8192
drwxr-sr-x+ 3 root systemd-journal 46 May 11 14:40 ..
drwxr-sr-x+ 2 root systemd-journal 28 May 11 14:40 .
-rw-r-----+ 1 root systemd-journal 8388608 May 11 14:42 system.journal
[root@fedoraatomic-s-1vcpu-1gb-nyc1-01 ~]# file
/var/log/journal/4eddc7982ffd4847a32ecd3f6d3170d7/system.journal
/var/log/journal/4eddc7982ffd4847a32ecd3f6d3170d7/system.journal: Journal file, online
[root@fedoraatomic-s-1vcpu-1gb-nyc1-01 ~]# journalctl -n 10
--file=/var/log/journal/4eddc7982ffd4847a32ecd3f6d3170d7/system.journal
-- Logs begin at Fri 2018-05-11 14:40:34 UTC, end at Fri 2018-05-11 14:42:03 UTC. --
May 11 14:41:00 fedoraatomic-s-1vcpu-1gb-nyc1-01 systemd[1]: Startup finished in 1.716s
(kernel) + 2.671s (initrd) + 23.610s (userspace) = 27.998s.
May 11 14:41:00 fedoraatomic-s-1vcpu-1gb-nyc1-01 rpm-ostree[1287]: In idle state; will
auto-exit in 60 seconds
May 11 14:41:00 fedoraatomic-s-1vcpu-1gb-nyc1-01 rpm-ostree[1287]: Allowing active client
:1.21 (uid 0)
May 11 14:41:00 fedoraatomic-s-1vcpu-1gb-nyc1-01 rpm-ostree[1287]: client :1.21 (uid 0)
added; new total=1
May 11 14:41:00 fedoraatomic-s-1vcpu-1gb-nyc1-01 rpm-ostree[1287]: client :1.21 (uid 0)
vanished; remaining=0
May 11 14:41:00 fedoraatomic-s-1vcpu-1gb-nyc1-01 rpm-ostree[1287]: In idle state; will
auto-exit in 63 seconds
May 11 14:41:05 fedoraatomic-s-1vcpu-1gb-nyc1-01 audit[1]: SERVICE_STOP pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/l>
May 11 14:41:21 fedoraatomic-s-1vcpu-1gb-nyc1-01 audit[1]: SERVICE_STOP pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/syste>
May 11 14:42:03 fedoraatomic-s-1vcpu-1gb-nyc1-01 rpm-ostree[1287]: In idle state; will
auto-exit in 61 seconds
May 11 14:42:03 fedoraatomic-s-1vcpu-1gb-nyc1-01 audit[1]: SERVICE_STOP pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=rpm-ostreed
comm="systemd" exe="/usr/lib/systemd/sys
[root@fedoraatomic-s-1vcpu-1gb-nyc1-01 ~]# journalctl -u systemd-journald
--file=/var/log/journal/4eddc7982ffd4847a32ecd3f6d3170d7/system.journal
-- Logs begin at Fri 2018-05-11 14:40:34 UTC, end at Fri 2018-05-11 14:42:03 UTC. --
May 11 14:40:34 localhost systemd-journald[185]: Journal started
May 11 14:40:34 localhost systemd-journald[185]: Runtime journal
(/run/log/journal/4eddc7982ffd4847a32ecd3f6d3170d7) is 6.1M, max 49.2M, 43.0M free.
May 11 14:40:37 localhost systemd-journald[185]: Journal stopped
May 11 14:40:38 localhost.localdomain systemd-journald[612]: Journal started
May 11 14:40:38 localhost.localdomain systemd-journald[612]: Runtime journal
(/run/log/journal/4eddc7982ffd4847a32ecd3f6d3170d7) is 6.1M, max 49.2M, 43.0M free.
May 11 14:40:39 localhost.localdomain systemd-journald[612]: Runtime journal
(/run/log/journal/4eddc7982ffd4847a32ecd3f6d3170d7) is 6.1M, max 49.2M, 43.0M free.
May 11 14:40:40 localhost.localdomain systemd-journald[612]: Time spent on flushing to
/var is 46.350ms for 768 entries.
```
When the `systemd-journald` service is restarted, it creates a new directory under
`/var/log/journal`
```
[root@fedoraatomic-s-1vcpu-1gb-nyc1-01 ~]# systemctl restart systemd-journald
[root@fedoraatomic-s-1vcpu-1gb-nyc1-01 ~]# journalctl --list-boots
0 619b79e423a8400bbc348657c5c641d9 Fri 2018-05-11 15:07:24 UTC—Fri 2018-05-11 15:07:24
UTC
[root@fedoraatomic-s-1vcpu-1gb-nyc1-01 ~]# ls -la /var/log/journal/
total 0
drwxr-sr-x+ 4 root systemd-journal 86 May 11 15:07 .
drwxr-xr-x. 8 root root 199 May 11 14:40 ..
drwxr-sr-x+ 2 root systemd-journal 28 May 11 14:40 4eddc7982ffd4847a32ecd3f6d3170d7
drwxr-sr-x+ 2 root systemd-journal 28 May 11 15:07 821032e961bc6d04ca1012bc5af5ab7c
[root@fedoraatomic-s-1vcpu-1gb-nyc1-01 ~]# ls -la
/var/log/journal/821032e961bc6d04ca1012bc5af5ab7c/
total 8192
drwxr-sr-x+ 2 root systemd-journal 28 May 11 15:07 .
drwxr-sr-x+ 4 root systemd-journal 86 May 11 15:07 ..
-rw-r-----+ 1 root systemd-journal 8388608 May 11 15:07 system.journal
[root@fedoraatomic-s-1vcpu-1gb-nyc1-01 ~]# journalctl -b
-- Logs begin at Fri 2018-05-11 15:07:24 UTC, end at Fri 2018-05-11 15:07:24 UTC. --
May 11 15:07:24 fedoraatomic-s-1vcpu-1gb-nyc1-01 systemd-journald[612]: Received SIGTERM
from PID 1 (systemd).
May 11 15:07:24 fedoraatomic-s-1vcpu-1gb-nyc1-01 systemd[1]: Stopping Journal Service...
May 11 15:07:24 fedoraatomic-s-1vcpu-1gb-nyc1-01 systemd[1]: Stopped Journal Service.
May 11 15:07:24 fedoraatomic-s-1vcpu-1gb-nyc1-01 systemd[1]: Starting Journal Service...
May 11 15:07:24 fedoraatomic-s-1vcpu-1gb-nyc1-01 systemd-journald[1655]: Journal started
May 11 15:07:24 fedoraatomic-s-1vcpu-1gb-nyc1-01 systemd-journald[1655]: System journal
(/var/log/journal/821032e961bc6d04ca1012bc5af5ab7c) is 8.0M, max 2.3G, 2.3G free.
May 11 15:07:24 fedoraatomic-s-1vcpu-1gb-nyc1-01 audit[1]: SERVICE_STOP pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=systemd-journald comm="systemd" exe="/usr/lib/system>
May 11 15:07:24 fedoraatomic-s-1vcpu-1gb-nyc1-01 systemd[1]: Started Journal Service.
May 11 15:07:24 fedoraatomic-s-1vcpu-1gb-nyc1-01 audit: CONFIG_CHANGE audit_enabled=1
old=1 auid=4294967295 ses=4294967295 subj=system_u:system_r:syslogd_t:s0 res=1
May 11 15:07:24 fedoraatomic-s-1vcpu-1gb-nyc1-01 audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=systemd-journald comm="systemd" exe="/usr/lib/syste>
May 11 15:07:24 fedoraatomic-s-1vcpu-1gb-nyc1-01 systemd[1]: Starting Flush Journal to
Persistent Storage...
May 11 15:07:24 fedoraatomic-s-1vcpu-1gb-nyc1-01 audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=systemd-journal-flush comm="systemd" exe="/usr/lib/>
May 11 15:07:24 fedoraatomic-s-1vcpu-1gb-nyc1-01 systemd[1]: Started Flush Journal to
Persistent Storage.
```
I booted the corresponding qcow2 locally on my workstation and did not observe the same
issue.
Hmm...this might get us closer to the answer. On the local VM which did not observe the
problem, the value of `/etc/machine-id` matches the value of the directory where the
journal is stored on disk:
```
# cat /etc/machine-id
ecb200d1e3564c7f86ec7d31dc967204
# ls -l /var/log/journal/
total 0
drwxr-sr-x+ 2 root systemd-journal 28 May 11 15:21 ecb200d1e3564c7f86ec7d31dc967204
```
But on the Digital Ocean droplet, those values are out of sync:
```
[root@fedoraatomic-s-1vcpu-1gb-nyc1-01 ~]# cat /etc/machine-id
821032e961bc6d04ca1012bc5af5ab7c
[root@fedoraatomic-s-1vcpu-1gb-nyc1-01 ~]# ls -l /var/log/journal/
total 0
drwxr-sr-x+ 2 root systemd-journal 28 May 11 14:40 4eddc7982ffd4847a32ecd3f6d3170d7
```
Only after the `systemd-journald` service is restarted, does the matching entry show up.
I'm unable to find any smoking gun in the journal file as to where that early
machine-id is coming from, though.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/468