Evaluate systemd logs using journalctl
Finely Filtered
The journal is the systemd component responsible for viewing and managing logfiles.
The systemd service journald creates very comprehensive logs, which allow you to analyze data in a variety of ways. Once you get used to the convenience this affords, you won't even miss the old-style logfiles.
Better structured
The journald daemon collects messages from the kernel, initrd, any running services and other available sources and collects them into one place. This results in a massive amount of data compared to the logfiles you're traditionally used to such as /var/log/messages or /var/log/syslog. You'll also find a huge amount of metadata is included, which can significantly improve your results when searching the journal.
This also results in a larger amount of data which is tricky to store in traditional text files. This is why the journald daemon stores this information in binary files. You can read this data, using the command journalctl
. If necessary, you can also convert the binary files to other formats for further analysis.
A little off the top
The huge amount of data being logged results in large files. While your system previously managed to trim these down using the Logrotate tool to compress and archive logfiles, the systemd journal allows you to set limits when files are changed.
Take a look at your own systemd [1] configuration file. For non-Debian based Linux distros, this is usually found in /etc/systemd/journald.conf
. You may also find it in /etc/systemd/journald.conf
. Look for the values SystemMaxUse
and SystemKeepFree
. The first of these determines how much space the journal files contain. The second value specifies how much free space to allocate (Figure 1).
Both values will determine the absolute limit on journal file sizes and available space. If you don't enter any values, the default amount of space permitted for journal files is 10 percent of your filesystem. The minimum amount of free space is 15 percent by default. The program caps both values at 4 GB for each.
Given the size of hard drives nowadays, it's perfectly feasible to set SystemMaxUse
to somewhere between 50 MB to 1 GB. In any case, the default values for the journal are sufficient for everyday use. Feel free to change the SystemMaxFileSize
to limit the size of individual files if you think it's necessary, however.
When setting size limits, use the values K
,G
and T
for kilobytes, gigabytes and terabytes respectively. If you want to alter the default values in journald.conf
, make sure to uncomment each line by removing the #
at the start, then restart the journald daemon.
Persistent or volatile?
Take a look at the line reading Storage=. While most Linux distributions are configured to store logs continuously, your logs will only be saved to var/log/journal
if you set this to Storage=persistent
. If you don't want to save the logs, change this to Storage=volatile
instead. Doing this means your logs will be stored in /run/log/journal
but will be deleted by the daemon once your active session ends.
For more options for controlling the journal size, pull up the man page for journald.conf
. If you want to reduce the journal size while it's running, you have two choices. Your first choice is to use the following command to reduce journal size, for instance to 100 MB. While running as root, enter:
# journalctl --vacuum-size=100M
The program will delete the oldest entries until the journal reaches the desired size (in this case 100 MB). Your second option is to remove all entries before a certain time:
# journalctl --vacuum-time=1month
The above command discards all messages older than one month (Figure 2), irrespective of how large or small this would make the logfile.
Buy Linux Magazine
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters
Support Our Work
Linux Magazine content is made possible with support from readers like you. Please consider contributing when you’ve found an article to be beneficial.
News
-
TUXEDO Computers Unveils Linux Laptop Featuring AMD Ryzen CPU
This latest release is the first laptop to include the new CPU from Ryzen and Linux preinstalled.
-
XZ Gets the All-Clear
The back door xz vulnerability has been officially reverted for Fedora 40 and versions 38 and 39 were never affected.
-
Canonical Collaborates with Qualcomm on New Venture
This new joint effort is geared toward bringing Ubuntu and Ubuntu Core to Qualcomm-powered devices.
-
Kodi 21.0 Open-Source Entertainment Hub Released
After a year of development, the award-winning Kodi cross-platform, media center software is now available with many new additions and improvements.
-
Linux Usage Increases in Two Key Areas
If market share is your thing, you'll be happy to know that Linux is on the rise in two areas that, if they keep climbing, could have serious meaning for Linux's future.
-
Vulnerability Discovered in xz Libraries
An urgent alert for Fedora 40 has been posted and users should pay attention.
-
Canonical Bumps LTS Support to 12 years
If you're worried that your Ubuntu LTS release won't be supported long enough to last, Canonical has a surprise for you in the form of 12 years of security coverage.
-
Fedora 40 Beta Released Soon
With the official release of Fedora 40 coming in April, it's almost time to download the beta and see what's new.
-
New Pentesting Distribution to Compete with Kali Linux
SnoopGod is now available for your testing needs
-
Juno Computers Launches Another Linux Laptop
If you're looking for a powerhouse laptop that runs Ubuntu, the Juno Computers Neptune 17 v6 should be on your radar.