dghubble reported a new issue against the project: `atomic-wg` that you are following:
``
systemd-journald is missing logs on fresh droplets. journalctl shows nothing for any
unit.
```
$ journalctl
No journal files were found.
-- No entries --
```
That's not right. There should at least be some system logs there. Check any unit and
find no entries.
It seems like restarting `systemd-journald` or rebooting works around the issue, so its
present only on fresh droplets. Originally observed on DigitalOcean's `20180424.4`
image and doing a rolling upgrade to `28.20180425.0` addressed the issue - but that
probably only worked because of the reboot. Since fresh `28.20180425.0` droplets now also
have the systemd-journald issue.
```
● ostree://fedora-atomic:fedora/28/x86_64/atomic-host
Version: 28.20180425.0 (2018-04-25 19:14:57)
Commit:
94a9d06eef34aa6774c056356d3d2e024e57a0013b6f8048dbae392a84a137ca
GPGSignature: Valid signature by 128CF232A9371991C8A65695E08E7E629DB62FB1
```
https://twitter.com/dghubble/status/993277668828168192
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/468