sudo -i if not already.
- Try running
journalctl -b to see messages from the current boot.
- If you still get
-- No entries --, run
- If you get
No journal files were found, something is corrupted with the journal service itself. Run
systemctl status systemd-journald*
- If the services are all "green" (active/running), something is borked with the log files in
/var/log/journal/<hash>. Try running the following to recreate them:
systemctl restart systemd-journald.service
The previous command will restart
journald with a new hash under
/var/log/journal. Now if you run
journalctl -b you should see messages about the service itself starting.
Unfortunately the files under
/var/log/journal are not parseable so figuring out the initial problem may be difficult, but at least logs going forward will work again.