systemd/Journal

systemd has its own logging system called the journal; running a separate logging daemon is not required.

systemd journal classifies messages by Priority level and Facility. Logging classification corresponds to classic Syslog protocol (RFC 5424).

Accessing the journal

The journal is read using journalctl(1), typically in one of two ways: inspecting previous logs, or watching new entries as they are logged. For the former, the -e/--pager-end option is typically useful; the latter is enabled by the -f/--follow option.

Note Both of these options imply some form of -n/--lines, unless that option is also specified somewhere else on the command line.

Filtering output

journalctl allows its output to be filtered in many ways. This is useful to make logs easier to sift through, because journalctl can struggle displaying logs in real-time if there are too many of them...

Non-option arguments enable filtering by journal fields (e.g. _PID=1, see systemd.journal-fields(7)), executable path, or kernel device, as described in journalctl(1) § DESCRIPTION. See Lennart Poettering's blog post for some examples.

A full list of additional options, and the short form of the following, is available at journalctl(1) § FILTERING OPTIONS, but here are the most common ones:

Show all messages matching PATTERN:
```
# journalctl --grep=PATTERN
```
This should be preferred over journalctl | grep, as it avoids journalctl performing more work only for it to be discarded.
Include explanations of log messages from the message catalog where available:
```
# journalctl --catalog
```
Note that this feature should not be used when attaching logs to bug reports and support threads, as to limit extraneous output. You can list all known catalog entries by running journalctl --list-catalog.
Show all messages from a given time onwards (systemd.time(7) § PARSING TIMESTAMPS):
```
# journalctl --since="2012-10-30 18:17:16"
# journalctl --since "20 min ago"
```
Show all messages by a specific identifier:
```
# journalctl --identifier sudo
```
Show all messages by a specific unit: (the .service suffix can be omitted)
```
# journalctl --unit man-db.service
```
Note that user services require the use of --user-unit instead:
```
$ journalctl --user-unit dbus
```
Show only error, critical and alert priority messages:
```
# journalctl --priority err..alert
```
You can use numeric log level too, like journalctl -p 3..1. If single number/log level is used, journalctl -p 3, then all higher priority log levels are also included (i.e. 0 to 3 in this case).

This article or section is being considered for removal.

Reason: Redundant with the generic filtering advice, doesn't match facility 10 below's advice to also watch 4, and this is not a “common option” either. (Discuss in Talk:Systemd/Journal)

Show auth.log equivalent by filtering on syslog facility:

# journalctl SYSLOG_FACILITY=10

If the journal directory (by default located under /var/log/journal) contains a large amount of log data then journalctl can take several minutes to filter output. It can be sped up significantly by using --file option to force journalctl to look only into most recent journal:
```
# journalctl --file /var/log/journal/*/system.journal -f
```

Specify a different journal to view

There may be a need to check the logs of another system that is dead in the water, like booting from a live system to recover a production system. In such case, one can mount the disk in e.g. /mnt, and specify the journal path via -D/--directory, like so:

# journalctl -D /mnt/var/log/journal -e

Examining journal without `journalctl`

While the journal is stored in a binary format, the content of stored messages is not modified.

This means it is viewable with strings, for example for recovery in an environment which does not have systemd installed, e.g.:

$ strings /mnt/arch/var/log/journal/af4967d77fba44c6b093d0e9862f6ddd/system.journal | grep -i message

Priority level

A syslog severity code (in systemd called priority) is used to mark the importance of a message RFC 5424 6.2.1.

Value	Severity	Keyword	Description	Examples
0	Emergency	emerg	System is unusable	Severe Kernel BUG, systemd dumped core. This level should not be used by applications.
1	Alert	alert	Should be corrected immediately	Vital subsystem goes out of work. Data loss. `kernel: BUG: unable to handle kernel paging request at ffffc90403238ffc`.
2	Critical	crit	Critical conditions	Crashes, coredumps. Like familiar flash: `systemd-coredump[25319]: Process 25310 (plugin-containe) of user 1000 dumped core` Failure in the system primary application, like X11.
3	Error	err	Error conditions	Non-fatal error reported: `kernel: usb 1-3: 3:1: cannot get freq at ep 0x84`, `systemd[1]: Failed unmounting /var.`, `libvirtd[1720]: internal error: Failed to initialize a valid firewall backend`
4	Warning	warning	May indicate that an error will occur if action is not taken	A non-root file system has only 1GB free. `org.freedesktop. Notifications[1860]: (process:5999): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale`
5	Notice	notice	Events that are unusual, but not error conditions	`systemd[1]: var.mount: Directory /var to mount over is not empty, mounting anyway`, `gcr-prompter[4997]: Gtk: GtkDialog mapped without a transient parent. This is discouraged`
6	Informational	info	Normal operational messages that require no action	`lvm[585]: 7 logical volume(s) in volume group "archvg" now active`
7	Debug	debug	Messages which may need to be enabled first, only useful for debugging	`kdeinit5[1900]: powerdevil: Scheduling inhibition from ":1.14" "firefox" with cookie 13 and reason "screen"`

These rules are recommendations, and the priority level of a given error is at the application developer's discretion. It is always possible that the error will be at a higher or lower level than expected.

Facility

A syslog facility code is used to specify the type of program that is logging the message RFC 5424 6.2.1.

Facility code	Keyword	Description	Info
0	kern	Kernel messages
1	user	User-level messages
2	mail	Mail system	Archaic POSIX still supported and sometimes used (for more mail(1))
3	daemon	System daemons	All daemons, including systemd and its subsystems
4	auth	Security/authorization messages	Also watch for different facility 10
5	syslog	Messages generated internally by syslogd	For syslogd implementations (not used by systemd, see facility 3)
6	lpr	Line printer subsystem (archaic subsystem)
7	news	Network news subsystem (archaic subsystem)
8	uucp	UUCP subsystem (archaic subsystem)
9		Clock daemon	systemd-timesyncd
10	authpriv	Security/authorization messages	Also watch for different facility 4
11	ftp	FTP daemon
12	-	NTP subsystem
13	-	Log audit
14	-	Log alert
15	cron	Scheduling daemon
16	local0	Local use 0 (local0)
17	local1	Local use 1 (local1)
18	local2	Local use 2 (local2)
19	local3	Local use 3 (local3)
20	local4	Local use 4 (local4)
21	local5	Local use 5 (local5)
22	local6	Local use 6 (local6)
23	local7	Local use 7 (local7)

Useful facilities to watch: 0, 1, 3, 4, 9, 10, 15.

Journal storage

In Arch Linux, the directory /var/log/journal/ is a part of the systemd package. Since the default mode for the journal is Storage=persistent, the journal will write to /var/log/journal/, and the directory will be created if it is not present. If the mode is manually configured to Storage=auto, systemd will instead write its logs to /run/log/journal/ in a non-persistent way.

Journal size limit

The default size limit for persistent journals (the default mode) corresponds to 10% of the size of the underlying file system, but has a soft-cap at 4 GiB. For example, with /var/log/journal/ located on a 20 GiB partition, journal data may take up to 2 GiB. On a 50 GiB partition, it would at max. at 4 GiB. To confirm the current limits on your system, review systemd-journald unit logs:

# journalctl -b -u systemd-journald

The maximum size of the persistent journal can be controlled by uncommenting and changing the following:

/etc/systemd/journald.conf

SystemMaxUse=50M

Note If SystemMaxUse is set to a large amount, it may still be limited by the default SystemKeepFree parameter, which is set to 15 percent of the underlying filesystem. The journal daemon will respect both parameters, and use the smaller of the two.

It is also possible to use the drop-in snippets configuration override mechanism rather than editing the global configuration file. In this case, place the overrides under the [Journal] header:

/etc/systemd/journald.conf.d/00-journal-size.conf

[Journal] SystemMaxUse=50M

Restart the systemd-journald.service after changing this setting to apply the new limit.

See journald.conf(5) for more info.

Clean journal files manually

Journal files can be globally removed from /var/log/journal/ using e.g. rm, or can be trimmed according to various criteria using journalctl. For example:

Remove archived journal files until the disk space they use falls below 100M:
```
# journalctl --vacuum-size=100M
```
Make all journal files contain no data older than 2 weeks.
```
# journalctl --vacuum-time=2weeks
```

Journal files must have been rotated out and made inactive before they can be trimmed by vacuum commands. Rotation of journal files can be done by running journalctl --rotate. The --rotate argument can also be provided alongside one or more vacuum criteria arguments to perform rotation and then trim files in a single command.

See journalctl(1) for more info.

Tips and tricks

Per unit size limit by a journal namespace

Edit the unit file for the service you wish to configure (for example sshd) and add LogNamespace=ssh in the [Service] section.

Then create /etc/systemd/journald@ssh.conf by copying /etc/systemd/journald.conf. After that, edit journald@ssh.conf and adjust SystemMaxUse to your liking.

Restarting the service should automatically start the new journal service systemd-journald@ssh.service. The logs from the namespaced service can be viewed with journalctl --namespace ssh.

See systemd-journald.service(8) § JOURNAL NAMESPACES for details about journal namespaces.

Journald in conjunction with syslog

Compatibility with a classic, non-journald aware syslog implementation can be provided by letting systemd forward all messages via the socket /run/systemd/journal/syslog. To make the syslog daemon work with the journal, it has to bind to this socket instead of /dev/log (official announcement).

The default journald.conf for forwarding to the socket is ForwardToSyslog=no to avoid system overhead, because rsyslog or syslog-ng pull the messages from the journal by itself.

See Syslog-ng#Overview and Syslog-ng#syslog-ng and systemd journal, or rsyslog respectively, for details on configuration.

Forward journald to /dev/tty12

Create a drop-in directory /etc/systemd/journald.conf.d and create a fw-tty12.conf file in it:

/etc/systemd/journald.conf.d/fw-tty12.conf

[Journal] ForwardToConsole=yes TTYPath=/dev/tty12

Then restart systemd-journald.service.

Note

By design, this does not forward kernel ring log messages.
This does not have to be TTY 12 specifically, however that TTY must not be controlled by another process. In particular, see getty#Add additional virtual consoles if you wish to use TTY 1 to 6.

Journal access as user

By default, a regular user only has access to their own per-user journal. To grant read access for the system journal as a regular user, you can add that user to the systemd-journal user group. Members of the adm and wheel groups are also given read access.

See journalctl(1) § DESCRIPTION and Users and groups#User groups for more information.

Desktop notifications

Desktop notifications can help you quickly notice error messages, improving awareness compared to manually checking logs or not noticing them at all.

The journalctl-desktop-notification^AUR package provides an automatic desktop notification for each error message logged by any process. For more details and configuration options, visit the GitLab project page.

Hiding the hostname

By default, journalctl(1) shows the hostname of the machine which generated the logs, which is pertinent if you are viewing the logs of multiple machines at once (possibly on different terminals). But, in other cases, the -W/--no-hostname option can help make lines shorter.

Wrap journal lines instead of truncating them

By default, journalctl truncates lines longer than screen width, but in some cases, it may be better to enable wrapping instead of truncating. This can be controlled by the SYSTEMD_LESS environment variable, which contains options passed to less (the default pager) and defaults to FRSXMK (see less(1) and journalctl(1) for details).

By omitting the S option, the output will be wrapped instead of truncated. For example, start journalctl as follows:

$ SYSTEMD_LESS=FRXMK journalctl

To set this behaviour as default, add this as an environment variable.

Printing kernel messages only

journalctl can be used as a dmesg(8) alternative:

# journalctl --dmesg