Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

7
  • 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* Commented Jun 7, 2016 at 21:54
  • 1
    art thou root?? Commented Jun 8, 2016 at 17:55
  • @HeshamAhmed Updated my output to show output from -b and --verify options. Commented Jun 8, 2016 at 17:57
  • @PeterTurner Yeah, I'm root. Commented Jun 8, 2016 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. Commented Apr 19, 2019 at 16:21