[systemd-devel] Journal Log Persistence without restart of service

[Lennart Poettering]

On Sun, 24.04.16 21:54, Renjith Vijayan (renjithvjn at gmail.com) wrote:

> Hi All,
> 
> I am trying to make journal logs persistent across reboots in my platform.
> Currently /var/log is mounted on volatile partition in the platform.
> I have a non-volatile partition mounted at /var/diagnostics.
> So i made the following change in tmpfile.d service config
> file(volatile.conf) to create a symlink.
> 
> L+ /var/log/journal 0666 root root - /var/diagnostics/logs
> 
> Also, the following changes to make logs persistent is done in
> journald.conf file.
> Storage=persistent
> 
> But still when the system boots up it takes the run time journal path & no
> files are present in /var/log/journal directory..
> *systemd-journal[114]: Runtime journal is using 8.0M (max allowed 392.4M,
> trying to leave 588.6M free of 3.8G available â current limit 392.4M).*
> *Jan 09 05:18:58 ops-as5712 systemd-journal[114]: Runtime journal is using
> 8.0M (max allowed 392.4M, trying to leave 588.6M free of 3.8G available â
> current limit 392.4M).*
> *Jan 09 05:18:58 ops-as5712 systemd-journal[114]: Journal started*
> *Jan 09 05:18:58 ops-as5712 systemd-journal[114]: Runtime journal is using
> 8.0M*
> 
> After i restart the systemd-journald service, the logs are becoming
> persistent & getting stored in the permanent partition.
> 
> Could somebody point out what needs to be done to make it persistent
> without the restart of systemd-journald service?

Consider adding a RequiresMountsFor=/var/diagnostics/logs line in the
[Unit] section to systemd-journal-flush.service, so that the initial
flushing is delayed until your fs is mounted. (doe this via a .d
drop-in in /etc best)

Lennart

-- 
Lennart Poettering, Red Hat