Description of problem: When journald.conf has Storage=volatile and the system is rebooted, systemd still reports flushing to persistent storage. Version-Release number of selected component (if applicable): systemd-206-11.fc20.x86_64 How reproducible: Always Steps to Reproduce: 1. /etc/systemd/journald.conf, set #Storage=volatile and remove #. 2. Reboot Actual results: [root@f20s journal]# journalctl -b | grep -i journal Sep 24 21:43:59 f20s.localdomain systemd-journal[82]: Runtime journal is using 708.0K (max 197.5M, leaving 296.3M of free 1.9G, current limit 197.5M). Sep 24 21:43:59 f20s.localdomain systemd-journal[82]: Runtime journal is using 712.0K (max 197.5M, leaving 296.3M of free 1.9G, current limit 197.5M). Sep 24 21:43:59 f20s.localdomain systemd[1]: Starting Journal Socket. Sep 24 21:43:59 f20s.localdomain systemd[1]: Listening on Journal Socket. Sep 24 21:43:59 f20s.localdomain systemd[1]: Starting Journal Service... Sep 24 21:43:59 f20s.localdomain systemd-journal[82]: Journal started Sep 24 21:43:59 f20s.localdomain systemd[1]: Started Journal Service. Sep 24 21:44:01 f20s.localdomain [82]: Journal stopped Sep 24 21:44:05 f20s.localdomain systemd-journal[211]: Runtime journal is using 1.5M (max 197.5M, leaving 296.3M of free 1.9G, current limit 197.5M). Sep 24 21:44:05 f20s.localdomain systemd-journald[82]: Received SIGTERM Sep 24 21:44:05 f20s.localdomain systemd-journal[211]: Journal started Sep 24 21:44:10 f20s.localdomain systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage... Sep 24 21:44:10 f20s.localdomain systemd[1]: Started Trigger Flushing of Journal to Persistent Storage. Expected results: Report flushing of journal to volatile storage Additional info: [root@f20s journal]# ll /var/log/journal/ total 0 [root@f20s journal]# journalctl --verify PASS: /run/log/journal/8e4cbfea404512ae70096c6202c9a3bf/system.journal The journal does appear to be in volatile storage, not persisent. Uncertain if this is a regression.
"Trigger Flushing of Journal to Persistent Storage" is the description of systemd-journal-flush.service. This service gets started regardless of what's in journald.conf. All it does is it sends SIGUSR1 to systemd-journald. systemd-journald will simply ignore this signal if "Storage=volatile" is configured. It is true that starting systemd-journal-flush.service is pointless when "Storage=volatile" is used, but it causes no harm. Possible solutions to clear up the confusion: 1. Rephrase the service's description somehow. "Notify journald About Availability Of Persistent Storage"? Would you consider that an improvement? 2. Add a generator to parse journald.conf and pull systemd-journald-flush.service into the boot transaction only if persistent storage is enabled. This would work, but I don't like this. It means additional code and the overhead of the generator is comparable to the overhead of starting the service needlessly.
Thanks for the response. This bug is more user confusion than an actual bug, and is more an RFE and figuring out what that would be. The suggestion is definitely an improvement. It makes it a true statement of fact. While troubleshooting something else, I needed to redirect the log elsewhere and this message seemed like a statement of fact, no matter what I changed in journald.conf, until I learned it wasn't saying what I thought it was saying. I also thought about journalctl having a way to show where the current logs are being written, reported by --disk-usage. Synonyms for this might be --usage and --status. So all of those would return what --disk-usage does now, but also includes the path to journals. To make it REALLY obvious, the returned information could even say persistent vs volatile. e.g. [root@local ~]# journalctl --usage/status/disk-usage Journals take up 12.0M on persistent storage at /var/log/journal
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
I can't come up with a wording that would be conside but avoid this ambiguity. If you have a good solution, please reopen.