4

For example:

┌─[10:50:38/hypership/root/~]
└─╼ journalctl -b
No journal files were found.
-- No entries --

┌─[10:50:46/hypership/root/~]
└─╼ journalctl --verify
No journal files were found.

/var/log is full of files though, and this was working before. Seems like an Arch Linux update may have caused this.

Any idea what the problem may be? What more info can I provide?

  • 1
    journalctl -k shows dmesg (kernel messages), you can get the same output by simple running the command "dmesg". To check if journalctl is working for non-kernel messages just type journalctl -b, if that doesn't give any logs then paste the output of systemctl status systemd-journald* – Hesham Ahmed Jun 7 '16 at 21:54
  • 1
    art thou root?? – Peter Turner Jun 8 '16 at 17:55
  • @HeshamAhmed Updated my output to show output from -b and --verify options. – trusktr Jun 8 '16 at 17:57
  • @PeterTurner Yeah, I'm root. – trusktr Jun 8 '16 at 17:57
  • 1
    You could also get this error message, if you query logs for a specific service, and just made a typo in the service name, as I just did. – bvdb Apr 19 at 16:21

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.