59ce1d902e
Currently we only export the devstack@ services, and then separately export the kernel & sudo logs to syslog.txt. This leaves a lot of logs potentially behind in the journal for various daemons. Just export the whole lot. Using this output is currently very opaque and makes use of systemd export tools that are very un-discoverable. Add a README that will appear alongside the journal explaining how to actually use it. This is a template as it would be nice to put into things like the list of services that are in the journal, or maybe other magic. Also make sure we export the logs since the start timestamp; currently during a full run we drop the initial logs. Change-Id: Id2626f9113d82c6d524039acda8a8ec74afb2081
33 lines
1.0 KiB
Django/Jinja
33 lines
1.0 KiB
Django/Jinja
Devstack systemd journal
|
|
========================
|
|
|
|
The devstack.journal file is a copy of the systemd journal during the
|
|
devstack run.
|
|
|
|
To use it, you will need to convert it so journalctl can read it
|
|
locally. After downloading the file:
|
|
|
|
$ /lib/systemd/systemd-journal-remote <(xzcat ./devstack.journal.xz) -o output.journal
|
|
|
|
Note this binary is not in the regular path. On Debian/Ubuntu
|
|
platforms, you will need to have the "sytemd-journal-remote" package
|
|
installed.
|
|
|
|
It should result in something like:
|
|
|
|
Finishing after writing <large number> entries
|
|
|
|
You can then use journalctl to examine this file. For example, to see
|
|
all devstack services try:
|
|
|
|
$ journalctl --file ./output.journal -u 'devstack@*'
|
|
|
|
To see just cinder API server logs restrict the match with
|
|
|
|
$ journalctl --file ./output.journal -u 'devstack@c-api'
|
|
|
|
There may be many types of logs available in the journal, a command like
|
|
|
|
$ journalctl --file ./output.journal --output=json-pretty | grep "_SYSTEMD_UNIT" | sort -u
|
|
|
|
can help you find interesting things to filter on. |