- bookworm 252.17-1~deb12u1
- bookworm-backports 254.5-1~bpo12+1
- testing 254.5-1
- unstable 254.5-1
- experimental 255~rc1-3
SYSTEMD-JOURNAL-REMOTE(8) | systemd-journal-remote | SYSTEMD-JOURNAL-REMOTE(8) |
NAME¶
systemd-journal-remote - Receive journal messages over the network
SYNOPSIS¶
systemd-journal-remote [OPTIONS...] [-o/--output=DIR|FILE] [SOURCES...]
DESCRIPTION¶
systemd-journal-remote is a command to receive serialized journal events and store them to the journal. Input streams are in the Journal Export Format[1], i.e. like the output from journalctl --output=export. For transport over the network, this serialized stream is usually carried over an HTTPS connection.
SOURCES¶
Sources can be either "active" (systemd-journal-remote requests and pulls the data), or "passive" (systemd-journal-remote waits for a connection and then receives events pushed by the other side).
systemd-journal-remote can read more than one event stream at a time. They will be interleaved in the output file. In case of "active" connections, each "source" is one stream, and in case of "passive" connections, each connection can result in a separate stream. Sockets can be configured in "accept" mode (i.e. only one connection), or "listen" mode (i.e. multiple connections, each resulting in a stream).
When there are no more connections, and no more can be created (there are no listening sockets), then systemd-journal-remote will exit.
Active sources can be specified in the following ways:
--url=ADDRESS
Passive sources can be specified in the following ways:
--listen-raw=ADDRESS
--listen-http=ADDRESS, --listen-https=ADDRESS
$LISTEN_FDS
SINKS¶
The location of the output journal can be specified with -o or --output=. For "active" sources, this option is required.
--output=FILE
--output=DIR
If --output= is not used, the output directory /var/log/journal/remote/ will be used. In case the output file is not specified, journal files will be created underneath the selected directory. Files will be called remote-hostname.journal, where the hostname part is the escaped hostname of the source endpoint of the connection, or the numerical address if the hostname cannot be determined.
In case of "active" sources, the output file name must always be given explicitly.
OPTIONS¶
The following options are understood:
--split-mode
In case of "active" sources, the output file name must always be given explicitly and only none is allowed.
--compress [BOOL]
--seal [BOOL]
--getter=PROG --option1 --option2
Examples:
--getter='curl "-HAccept: application/vnd.fdo.journal" https://some.host:19531/'
--getter='wget --header="Accept: application/vnd.fdo.journal" -O- https://some.host:19531/'
-h, --help
--version
EXAMPLES¶
Copy local journal events to a different journal directory:
journalctl -o export | systemd-journal-remote -o /tmp/dir -
Retrieve all available events from a remote systemd-journal-gatewayd(8) instance and store them in /var/log/journal/remote/remote-some.host.journal:
systemd-journal-remote --url http://some.host:19531/
Retrieve current boot events and wait for new events from a remote systemd-journal-gatewayd(8) instance, and store them in /var/log/journal/remote/remote-some.host.journal:
systemd-journal-remote --url http://some.host:19531/entries?boot&follow
SEE ALSO¶
systemd-journal-upload(8), journalctl(1), systemd-journald.service(8), systemd-journal-gatewayd.service(8) journal-remote.conf(5)
NOTES¶
- 1.
- Journal Export Format
systemd 233 |