Enable persistent journaling #763
Open
+64
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In the cloud images, /var/log/journal doesn't exist. When this directory does not exist, journald will not write any files to disk, and as such, logging data is lost accross reboots. Persistent logging is useful for debugging issues that caused the nodes to reboot (provided that the logs are flushed to disk).
sjpb
requested changes
Aug 27, 2025
|
There's no concerns re disk space here are there? |
I believe it will limit itself to 10% of the filesystem, or 4GB by default (whichever is smaller): https://www.freedesktop.org/software/systemd/man/latest/journald.conf.html#SystemMaxUse= |
jovial
commented
Sep 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the cloud images, /var/log/journal doesn't exist. When this directory does not exist, journald will not write any files to disk, and as such, logging data is lost accross reboots.
Persistent logging is useful for debugging issues that caused the nodes to reboot (provided that the logs are flushed to disk).