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
-
New Steam Client Ups the Ante for Linux
The latest release from Steam has some pretty cool tricks up its sleeve.
-
Gnome OS Transitioning Toward a General-Purpose Distro
If you're looking for the perfectly vanilla take on the Gnome desktop, Gnome OS might be for you.
-
Fedora 41 Released with New Features
If you're a Fedora fan or just looking for a Linux distribution to help you migrate from Windows, Fedora 41 might be just the ticket.
-
AlmaLinux OS Kitten 10 Gives Power Users a Sneak Preview
If you're looking to kick the tires of AlmaLinux's upstream version, the developers have a purrfect solution.
-
Gnome 47.1 Released with a Few Fixes
The latest release of the Gnome desktop is all about fixing a few nagging issues and not about bringing new features into the mix.
-
System76 Unveils an Ampere-Powered Thelio Desktop
If you're looking for a new desktop system for developing autonomous driving and software-defined vehicle solutions. System76 has you covered.
-
VirtualBox 7.1.4 Includes Initial Support for Linux kernel 6.12
The latest version of VirtualBox has arrived and it not only adds initial support for kernel 6.12 but another feature that will make using the virtual machine tool much easier.
-
New Slimbook EVO with Raw AMD Ryzen Power
If you're looking for serious power in a 14" ultrabook that is powered by Linux, Slimbook has just the thing for you.
-
The Gnome Foundation Struggling to Stay Afloat
The foundation behind the Gnome desktop environment is having to go through some serious belt-tightening due to continued financial problems.
-
Thousands of Linux Servers Infected with Stealth Malware Since 2021
Perfctl is capable of remaining undetected, which makes it dangerous and hard to mitigate.