No idea how the 491.5M limit was decided. I changed the below setting
and restarted the system
By default my system had about ~500MB max size which had about 1 month
Now the max journal size is 1.0G. Why is it not 25G?
ANSWER TOO THOSE QUESTIONS:
Reinout van Schouwen 2015-11-05 20:42:54 CET
Description of problem: I got warnings about disk space on my root
partition. The cause was /var/log/journal with gigabytes of logs.
All options in /etc/systemd/journald.conf are commented out so
journalctl doesn't keep a certain maximum size. We should be smarter
about this so that logs don't fill up the root partition.
David Walser 2015-11-06 15:18:21 CET
I thought systemd would only allow it to use a certain % of disk space
on its partition. If it's really unbounded, that's a problem.
Colin Guthrie 2015-11-09 10:44:45 CET
So in order to investigate this any further, I'll need information
about your system. What is your partition size, what is the free space
etc. A listing of the files and folders inside /var/log/journal would
also be useful (including their full path, dates and sizes). Also the
output from "journalctl --disk-usage" (as root) and the output from
"journalctl -b MESSAGE_ID=ec387f577b844b8fa948f33cad9a75e6" (also as
How to increase max journal size even further?
Systemd Journals Logging with Persistent Storage
Configuring the systemd journal for persistence in RHEL7
Configuring the systemd journal for persistence in RHEL7 By default,
the journal doesn't store log files on disk, only in memory or the
/run/log/journal directory. This is sufficient for the recent log
history (with the journal) but not for long-term log retention should
you decide to go with journal only and not with any other syslog
Managing Journal Size
systemd-journald ensures older journal records or journal files are deleted in order to keep a certain amount of disk space free. In the Linux Logging with Systemd section, we explain how to control the thresholds for deleting old log data with configuration parameters. We can also use
journalctl to manage the size of the
journal, which we’ll explain in more detail in this section.
To check how much disk space is currently taken up by the journal, use the –disk-usage parameter:
$ journalctl --disk-usage
Depending on the version of
journalctl, the output can be similar to this:
Archived and active journals take up 96.0M on disk.
Journals take up 248.0M on disk.
You can also manage disk space taken up by
systemd journal by fine-tuning these configuration parameters: