[systemd-bugs] [Bug 86034] journalctl cannot be used when systems is not started

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=86034

Lennart Poettering <lennart at poettering.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |NOTABUG

--- Comment #7 from Lennart Poettering <lennart at poettering.net> ---
journalctl looks for the journal files in /var/log/journal/<machine-id>/. If
you boot up with a rescue OS that has a different machine ID or a different
root it hence won't find any data there.

Hence, make sure:

a) to either chroot to the host OS, and then use journalctl
--directory=/var/log/journal/<machine-id>

b) or chroot to the host OS, and then use journalctl -m

b) or to run journalctl
--directory=<pathtorootdir>/var/log/journal/<machine-id>

c) or to run journalctl --root=<pathtorootdir> -m

The "-m" swicth merges the journals of all directories in /var/log/journal/*,
hence makes it unnecessary to figure out the machine id of the host.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20141110/afcb9aee/attachment.html>