| Ian Wienand | 59ce1d9 | 2019-02-11 12:27:10 +1100 | [diff] [blame] | 1 | Devstack systemd journal |
| 2 | ======================== |
| 3 | |
| 4 | The devstack.journal file is a copy of the systemd journal during the |
| 5 | devstack run. |
| 6 | |
| 7 | To use it, you will need to convert it so journalctl can read it |
| 8 | locally. After downloading the file: |
| 9 | |
| 10 | $ /lib/systemd/systemd-journal-remote <(xzcat ./devstack.journal.xz) -o output.journal |
| 11 | |
| 12 | Note this binary is not in the regular path. On Debian/Ubuntu |
| Eyal | 56b2e7f | 2019-12-19 13:32:55 +0200 | [diff] [blame] | 13 | platforms, you will need to have the "systemd-journal-remote" package |
| Ian Wienand | 59ce1d9 | 2019-02-11 12:27:10 +1100 | [diff] [blame] | 14 | installed. |
| 15 | |
| 16 | It should result in something like: |
| 17 | |
| 18 | Finishing after writing <large number> entries |
| 19 | |
| 20 | You can then use journalctl to examine this file. For example, to see |
| 21 | all devstack services try: |
| 22 | |
| 23 | $ journalctl --file ./output.journal -u 'devstack@*' |
| 24 | |
| 25 | To see just cinder API server logs restrict the match with |
| 26 | |
| 27 | $ journalctl --file ./output.journal -u 'devstack@c-api' |
| 28 | |
| 29 | There may be many types of logs available in the journal, a command like |
| 30 | |
| 31 | $ journalctl --file ./output.journal --output=json-pretty | grep "_SYSTEMD_UNIT" | sort -u |
| 32 | |
| 33 | can help you find interesting things to filter on. |