On a host where journalctl shows nothing from before the last reboot, which change makes the journal persist across reboots?
LPIC-1 Exam 102-500, objective 108. Essential system services medium
Machine-checked — no person has signed for it. This question was read against the source cited below by an automated pass, which found no contradiction. That is a weaker claim than it sounds: the same kind of process wrote the question, so it can confirm its own mistake.
Treat it as a good draft rather than as settled fact, and read the source below before you rely on it. It is not used in mock exams here — only questions a person has signed for are.
How these questions are written — where each question comes from, what the verification ledger records, and what happens when one is found wrong.
The options
Not correct Set Storage=volatile in /etc/systemd/journald.conf.
Wrong, and the opposite. Storage=volatile forces the journal into /run/log/journal, which is a tmpfs and is discarded on every shutdown.
Not correct Add `journal /var/log/journal` to /etc/rsyslog.conf.
Wrong. rsyslog is a separate service with its own files; nothing in rsyslog.conf controls where journald stores its data, and that is not valid rsyslog syntax.
Not correct Run `journalctl --flush` once, which permanently reconfigures the storage location.
Wrong. --flush asks journald to move the entries currently held in /run/log/journal into /var/log/journal, and only does anything if that directory already exists. It is the one-off migration systemd-journal-flush.service performs at every boot, not a setting that changes where the journal is stored.
Correct Create the directory /var/log/journal, or set Storage=persistent in /etc/systemd/journald.conf, then restart systemd-journald.
Correct. With the default Storage=auto, journald writes persistently only when /var/log/journal exists; creating it is enough. Storage=persistent makes journald create the directory itself.
Why
journald's Storage= setting takes volatile (always /run/log/journal, lost at reboot), persistent (always /var/log/journal, created if missing), auto (the default: persistent if /var/log/journal exists, otherwise volatile) and none (drop everything). Because a persistent journal grows, journald caps it with SystemMaxUse= and friends, and `journalctl --disk-usage` and `journalctl --vacuum-size=500M` let you inspect and trim it by hand.
Where this comes from
- Cited
- LPI exam objective 108.2
- What it says
- Understand persistent and volatile journal storage under systemd-journald.
Practise this
Reading one question is not practice. The trainer will draw a short set from objective 108 and space the ones you get wrong.
More questions on this objective
- You corrected the running system's clock with `date -s`, but after the next power cycle the machine came back with the old wrong time. Which command copies the corrected system clock into the hardware (RTC) clock? machine-checked
- On a systemd-based distribution, which file determines the local time zone used by the C library when formatting times? machine-checked
- A host runs chrony as its NTP client. Which command shows the list of time sources chrony is currently talking to and how it rates each one? machine-checked
- In /etc/ntp.conf you find the line `server 0.pool.ntp.org iburst`. What does the `iburst` keyword do? machine-checked
- A minimal systemd host synchronises its clock with systemd-timesyncd. Which statement about that service is accurate? machine-checked
- On a systemd host, type the single command that turns on automatic network time synchronisation (do not include a path). machine-checked