--no-full

Ellipsize fields when they do not fit in available columns. The default is to show full fields, allowing them to wrap or betruncated by the pager, if one is used.The old options -l/--full are not useful anymore, except to undo --no-full.

-a

Show all fields in full, even if they include unprintable characters or are very long.

-f

Show only the most recent journal entries, and continuously print new entries as they are appended to the journal.

-e

Immediately jump to the end of the journal inside the implied pager tool. This implies -n1000 to guarantee that the pager willnot buffer logs of unbounded size. This may be overridden with an explicit -n with some other numeric value, while -nall willdisable this cap. Note that this option is only supported for the less(1) pager.

-n

Show the most recent journal events and limit the number of events shown. If --follow is used, this option is implied. Theargument is a positive integer or "all" to disable line limiting. The default value is 10 if no argument is given.

--no-tail

Show all stored output lines, even in follow mode. Undoes the effect of --lines=.

-r

Reverse output so that the newest entries are displayed first.

-o

Controls the formatting of the journal entries that are shown. Takes one of the following options:shortis the default and generates an output that is mostly identical to the formatting of classic syslog files, showing one lineper journal entry.short-fullis very similar, but shows timestamps in the format the --since= and --until= options accept. Unlike the timestampinformation shown in short output mode this mode includes weekday, year and timezone information in the output, and islocale-independent.short-isois very similar, but shows ISO 8601 wallclock timestamps.short-iso-preciseas for short-iso but includes full microsecond precision.short-preciseis very similar, but shows classic syslog timestamps with full microsecond precision.short-monotonicis very similar, but shows monotonic timestamps instead of wallclock timestamps.short-unixis very similar, but shows seconds passed since January 1st 1970 UTC instead of wallclock timestamps ("UNIX time"). The timeis shown with microsecond accuracy.verboseshows the full-structured entry items with all fields.exportserializes the journal into a binary (but mostly text-based) stream suitable for backups and network transfer (see JournalExport Format[1] for more information). To import the binary stream back into native journald format use systemd-journal-remote(8).jsonformats entries as JSON data structures, one per line (see Journal JSON Format[2] for more information).json-prettyformats entries as JSON data structures, but formats them in multiple lines in order to make them more readable by humans.json-sseformats entries as JSON data structures, but wraps them in a format suitable for Server-Sent Events[3].catgenerates a very terse output, only showing the actual message of each journal entry with no metadata, not even a timestamp.

--output-fields

A comma separated list of the fields which should be included in the output. This only has an effect for the output modes whichwould normally show all fields (verbose, export, json, json-pretty, and json-sse). The "__CURSOR", "__REALTIME_TIMESTAMP","__MONOTONIC_TIMESTAMP", and "_BOOT_ID" fields are always printed.

--utc

Express time in Coordinated Universal Time (UTC).

--no-hostname

Don't show the hostname field of log messages originating from the local host. This switch only has an effect on the short familyof output modes (see above).

-x

Augment log lines with explanation texts from the message catalog. This will add explanatory help texts to log messages in theoutput where this is available. These short help texts will explain the context of an error or log event, possible solutions, aswell as pointers to support forums, developer documentation, and any other relevant manuals. Note that help texts are notavailable for all messages, but only for selected ones. For more information on the message catalog, please refer to the MessageCatalog Developer Documentation[4].Note: when attaching journalctl output to bug reports, please do not use -x.

-q

Suppresses all informational messages (i.e. "-- Logs begin at ...", "-- Reboot --"), any warning messages regarding inaccessiblesystem journals when run as a normal user.

-m

Show entries interleaved from all available journals, including remote ones.

-b

Show messages from a specific boot. This will add a match for "_BOOT_ID=".The argument may be empty, in which case logs for the current boot will be shown.If the boot ID is omitted, a positive offset will look up the boots starting from the beginning of the journal, and anequal-or-less-than zero offset will look up boots starting from the end of the journal. Thus, 1 means the first boot found in thejournal in chronological order, 2 the second and so on; while -0 is the last boot, -1 the boot before last, and so on. An emptyoffset is equivalent to specifying -0, except when the current boot is not the last boot (e.g. because --directory was specifiedto look at logs from a different machine).If the 32-character ID is specified, it may optionally be followed by offset which identifies the boot relative to the one givenby boot ID. Negative values mean earlier boots and positive values mean later boots. If offset is not specified, a value of zerois assumed, and the logs for the boot given by ID are shown.

--list-boots

Show a tabular list of boot numbers (relative to the current boot), their IDs, and the timestamps of the first and last messagepertaining to the boot.

-k

Show only kernel messages. This implies -b and adds the match "_TRANSPORT=kernel".

-t

Show messages for the specified syslog identifier SYSLOG_IDENTIFIER.This parameter can be specified multiple times.

-u

Show messages for the specified systemd unit UNIT (such as a service unit), or for any of the units matched by PATTERN. If apattern is specified, a list of unit names found in the journal is compared with the specified pattern and all that match areused. For each unit name, a match is added for messages from the unit ("_SYSTEMD_UNIT=UNIT"), along with additional matches formessages from systemd and messages about coredumps for the specified unit.This parameter can be specified multiple times.

--user-unit

Show messages for the specified user session unit. This will add a match for messages from the unit ("_SYSTEMD_USER_UNIT=" and"_UID=") and additional matches for messages from session systemd and messages about coredumps for the specified unit.This parameter can be specified multiple times.

-p

Filter output by message priorities or priority ranges. Takes either a single numeric or textual log level (i.e. between0/"emerg" and 7/"debug"), or a range of numeric/text log levels in the form FROM..TO. The log levels are the usual syslog loglevels as documented in syslog(3), i.e. "emerg" (0), "alert" (1), "crit" (2), "err" (3), "warning" (4), "notice" (5),"info" (6), "debug" (7). If a single log level is specified, all messages with this log level or a lower (hence more important)log level are shown. If a range is specified, all messages within the range are shown, including both the start and the end valueof the range. This will add "PRIORITY=" matches for the specified priorities.

-g

Filter output to entries where the MESSAGE= field matches the specified regular expression. PERL-compatible regular expressionsare used, see pcre2pattern(3) for a detailed description of the syntax.If the pattern is all lowercase, matching is case insensitive. Otherwise, matching is case sensitive. This can be overridden withthe --case-sensitive option, see below.

--case-sensitive[

Make pattern matching case sensitive or case insenstive.

-c

Start showing entries from the location in the journal specified by the passed cursor.

--after-cursor

Start showing entries from the location in the journal after the location specified by the passed cursor. The cursor is shownwhen the --show-cursor option is used.

--show-cursor

The cursor is shown after the last entry after two dashes:

--

The format of the cursor is private and subject to change.

-S

Start showing entries on or newer than the specified date, or on or older than the specified date, respectively. Datespecifications should be of the format "2012-10-30 18:17:16". If the time part is omitted, "00:00:00" is assumed. If only theseconds component is omitted, ":00" is assumed. If the date component is omitted, the current day is assumed. Alternatively thestrings "yesterday", "today", "tomorrow" are understood, which refer to 00:00:00 of the day before the current day, the currentday, or the day after the current day, respectively. "now" refers to the current time. Finally, relative times may be specified,prefixed with "-" or "+", referring to times before or after the current time, respectively. For complete time and datespecification, see systemd.time(7). Note that --output=short-full prints timestamps that follow precisely this format.

-F

Print all possible data values the specified field can take in all entries of the journal.

-N

Print all field names currently used in all entries of the journal.

--system

Show messages from system services and the kernel (with --system). Show messages from service of current user (with --user). Ifneither is specified, show all messages that the user can see.

-M

Show messages from a running, local container. Specify a container name to connect to.

-D

Takes a directory path as argument. If specified, journalctl will operate on the specified journal directory DIR instead of thedefault runtime and system journal paths.

--file

Takes a file glob as an argument. If specified, journalctl will operate on the specified journal files matching GLOB instead ofthe default runtime and system journal paths. May be specified multiple times, in which case files will be suitably interleaved.

--root

Takes a directory path as an argument. If specified, journalctl will operate on journal directories and catalog file hierarchyunderneath the specified directory instead of the root directory (e.g. --update-catalog will createROOT/var/lib/systemd/catalog/database, and journal files under ROOT/run/journal or ROOT/var/log/journal will be displayed).

--new-id128

Instead of showing journal contents, generate a new 128-bit ID suitable for identifying messages. This is intended for usage bydevelopers who need a new identifier for a new message they introduce and want to make recognizable. This will print the new IDin four different formats which can be copied into source code or similar.

--header

Instead of showing journal contents, show internal header information of the journal fields accessed.

--disk-usage

Shows the current disk usage of all journal files. This shows the sum of the disk usage of all archived and active journal files.

--vacuum-size

Removes archived journal files until the disk space they use falls below the specified size (specified with the usual "K", "M","G" and "T" suffixes), or all archived journal files contain no data older than the specified timespan (specified with the usual"s", "m", "h", "days", "months", "weeks" and "years" suffixes), or no more than the specified number of separate journal filesremain. Note that running --vacuum-size= has only an indirect effect on the output shown by --disk-usage, as the latter includesactive journal files, while the vacuuming operation only operates on archived journal files. Similarly, --vacuum-files= might notactually reduce the number of journal files to below the specified number, as it will not remove active journal files.

--list-catalog

List the contents of the message catalog as a table of message IDs, plus their short description strings.If any 128-bit-IDs are specified, only those entries are shown.

--dump-catalog

Show the contents of the message catalog, with entries separated by a line consisting of two dashes and the ID (the format is thesame as .catalog files).If any 128-bit-IDs are specified, only those entries are shown.

--update-catalog

Update the message catalog index. This command needs to be executed each time new catalog files are installed, removed, orupdated to rebuild the binary catalog index.

--setup-keys

Instead of showing journal contents, generate a new key pair for Forward Secure Sealing (FSS). This will generate a sealing keyand a verification key. The sealing key is stored in the journal data directory and shall remain on the host. The verificationkey should be stored externally. Refer to the Seal= option in journald.conf(5) for information on Forward Secure Sealing and fora link to a refereed scholarly paper detailing the cryptographic theory it is based on.

--force

When --setup-keys is passed and Forward Secure Sealing (FSS) has already been configured, recreate FSS keys.

--interval

Specifies the change interval for the sealing key when generating an FSS key pair with --setup-keys. Shorter intervals increaseCPU consumption but shorten the time range of undetectable journal alterations. Defaults to 15min.

--verify

Check the journal file for internal consistency. If the file has been generated with FSS enabled and the FSS verification key hasbeen specified with --verify-key=, authenticity of the journal file is verified.

--verify-key

Specifies the FSS verification key to use for the --verify operation.

--sync

Asks the journal daemon to write all yet unwritten journal data to the backing file system and synchronize all journals. Thiscall does not return until the synchronization operation is complete. This command guarantees that any log messages writtenbefore its invocation are safely stored on disk at the time it returns.

--flush

Asks the journal daemon to flush any log data stored in /run/log/journal into /var/log/journal, if persistent storage is enabled.This call does not return until the operation is complete. Note that this call is idempotent: the data is only flushed from/run/log/journal into /var/log/journal once during system runtime, and this command exits cleanly without executing any operationif this has already happened. This command effectively guarantees that all data is flushed to /var/log/journal at the time itreturns.

--rotate

Asks the journal daemon to rotate journal files. This call does not return until the rotation operation is complete.

-h

Print a short help text and exit.

--version

Print a short version string and exit.

--no-pager

Do not pipe output into a pager.EXIT STATUSOn success, 0 is returned; otherwise, a non-zero failure code is returned.ENVIRONMENT$SYSTEMD_PAGERPager to use when --no-pager is not given; overrides $PAGER. If neither $SYSTEMD_PAGER nor $PAGER are set, a set of well-knownpager implementations are tried in turn, including less(1) and more(1), until one is found. If no pager implementation isdiscovered no pager is invoked. Setting this environment variable to an empty string or the value "cat" is equivalent to passing

--no-pager.

$SYSTEMD_LESSOverride the options passed to less (by default "FRSXMK").$SYSTEMD_LESSCHARSETOverride the charset passed to less (by default "utf-8", if the invoking terminal is determined to be UTF-8 compatible).EXAMPLESWithout arguments, all collected logs are shown unfiltered:journalctlWith one match specified, all entries with a field matching the expression are shown:journalctl _SYSTEMD_UNIT=avahi-daemon.serviceIf two different fields are matched, only entries matching both expressions at the same time are shown:journalctl _SYSTEMD_UNIT=avahi-daemon.service _PID=28097If two matches refer to the same field, all entries matching either expression are shown:journalctl _SYSTEMD_UNIT=avahi-daemon.service _SYSTEMD_UNIT=dbus.serviceIf the separator "+" is used, two expressions may be combined in a logical OR. The following will show all messages from the Avahiservice process with the PID 28097 plus all messages from the D-Bus service (from any of its processes):journalctl _SYSTEMD_UNIT=avahi-daemon.service _PID=28097 + _SYSTEMD_UNIT=dbus.serviceShow all logs generated by the D-Bus executable:journalctl /usr/bin/dbus-daemonShow all kernel logs from previous boot:journalctl -k -b -1Show a live log display from a system service apache.service:journalctl -f -u apache