Mastering journalctl: Powerful Techniques to Query systemd Logs
This guide explains how to use the journalctl command to view, filter, and manage systemd-journald logs on Linux, covering help options, match expressions, persistent storage, disk usage, vacuuming, time ranges, unit filtering, priority levels, real‑time streaming, output formatting, and kernel log access.
Introduction
journalctl is used to query the logs collected by the systemd-journald service, which is part of the systemd init system.
Command syntax: journalctl [OPTIONS…] [MATCHES…] Executable path:
/bin/journalctlHelp
Use the manual page or the -h option for quick help:
man journalctljournalctl -hOutput All Log Records
Running journalctl without options prints all log entries, which can be overwhelming.
sudo journalctlMatch (Filtering by Field)
Filter logs using the FIELD=VALUE format, e.g.: _SYSTEMD_UNIT=cron.service Multiple fields can be combined (logical AND):
journalctl _SYSTEMD_UNIT=cron.service PRIORITY=6Use the + operator for logical OR between matches:
journalctl _SYSTEMD_UNIT=cron.service + _PID=28097Persist Logs to Files
By default logs are stored in /run/log and lost on reboot. To keep them persistently:
Create /var/log/journal and restart the service.
Or edit /etc/systemd/journald.conf, set Storage=persistent, and restart.
Example (method 1):
sudo mkdir /var/log/journalsudo chown root:systemd-journal /var/log/journalsudo chmod 2775 /var/log/journalsudo systemctl restart systemd-journald.serviceCheck Disk Usage
sudo journalctl --disk-usageClean Log Data
Use --vacuum-size to limit total size.
Use --vacuum-time to delete entries older than a given time.
sudo journalctl --vacuum-size=1Gsudo journalctl --vacuum-time=1yearsLimit Maximum Log Capacity
Configure /etc/systemd/journald.conf with options such as: SystemMaxUse= – maximum persistent storage. SystemKeepFree= – free space to keep. SystemMaxFileSize= – max size of a single journal file. RuntimeMaxUse= – max size in volatile storage. RuntimeKeepFree= – free space in volatile storage. RuntimeMaxFileSize= – max size of a volatile journal file.
View Logs After a Specific Boot
journalctl --list-bootssudo journalctl -b -1sudo journalctl -b 9eaabbc25fe343999ef1024e6a16fb58View Logs Within a Time Range
Use --since and --until with various date formats:
journalctl --since "2018-03-26 20:20:00"journalctl --since "2018-03-26" --until "2018-03-26 03:00"journalctl --since yesterdayjournalctl --since 09:00 --until "1 hour ago"Combine Match and Time Filters
sudo journalctl _SYSTEMD_UNIT=cron.service --since "2018-03-27" --until "2018-03-27 01:00"Filter by Unit
sudo journalctl -u nginx.servicesudo journalctl -u nginx.service --since todayjournalctl -u nginx.service -u php-fpm.service --since todayFilter by Log Level (Priority)
Use -p or PRIORITY= with numeric values (0 = emerg … 7 = debug) or names:
sudo journalctl -p errReal‑Time Log Updates
sudo journalctl -fsudo journalctl -f -u prometheus.serviceShow Only the Latest N Lines
sudo journalctl -nsudo journalctl -n 20journalctl -u cron.service -n 3Control Output
Redirect output to standard output (disable pager): sudo journalctl --no-pager Format output with -o (e.g., short, json, json-pretty, cat etc.):
sudo journalctl -u cron.service -n 1 --no-pager -o jsonFilter by Executable Path
sudo journalctl /usr/lib/systemd/systemdsudo journalctl /usr/bin/bashView Kernel Logs
sudo journalctl -kSummary
With systemd, log viewing has shifted to the unified journalctl tool, eliminating the need for many disparate commands and providing powerful filtering, formatting, and persistence options.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
