Skip to content

Use volatile storage for journal data #1004

Merged
merged 3 commits into from
Jan 15, 2019

Conversation

pmenzel
Copy link
Collaborator

@pmenzel pmenzel commented Jan 15, 2019

After the update, the commands below should be executed.

 systemctl daemon-reexec
 systemctl restart systemd-journald

Please note, that the journal data for the current boot will then also be lost.

The directory /var/log/journal can be deleted after restarting systemd-journald.

Tested on keineahnung.

If `/var/log/journal` is present, systemd-journald flushes the log to
the disk, which we do not want yet, as we still use syslog. Therefore,
remove the directory.

We probably had manually deleted it on all systems with systemd 237, and
didn’t update the bee file accordingly, so that the logs were kept when
updating to systemd 239.
From `man journald.conf`:

> Storage=
>     Controls where to store journal data. One of "volatile",
>     "persistent", "auto" and "none". If "volatile", journal log data
>      will be stored only in memory, i.e. below the /run/log/journal
>      hierarchy (which is created if needed). If "persistent", data will
>      be stored preferably on disk, i.e. below the /var/log/journal
>      hierarchy (which is created if needed), with a fallback to
>      /run/log/journal (which is created if needed), during early boot
>      and if the disk is not writable.  "auto" is similar to
>      "persistent" but the directory /var/log/journal is not created if
>      needed, so that its existence controls where log data goes.
>      "none" turns off all storage, all log data received will be
>      dropped. Forwarding to other targets, such as the console, the
>      kernel log buffer, or a syslog socket will still work however.
>      Defaults to "auto".
@donald donald merged commit 5e04f3b into master Jan 15, 2019
Sign in to join this conversation on GitHub.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants