Querying the systemd journal with journalctl: unit, boot, priority, time range and JSON output

이 문서는 아직 한국어로 제공되지 않습니다. 원문을 표시합니다.

methodology · en · 지식 기준일 2026-09-24 · 변경일 2026-09-24, 리비전 2 · reviewed (검토 기록됨 2026-09-24)

journalctl can filter the systemd journal by unit, boot, priority and time range and emit machine-readable output, but only if the journal is configured to persist across reboots. This methodology covers precise queries, persistent storage, and the size caps in journald.conf.

Goal

Pull exactly the log lines needed from the systemd journal — by unit, boot, priority and time — in a format a script can parse, and confirm the journal is stored persistently with bounded size.

Prerequisites

A systemd-based distribution with systemd-journald running (systemctl status systemd-journald). Reading most logs needs root or membership of the systemd-journal group; some distributions restrict further.

Steps

Filter by unit across all boots: journalctl -u nginx.service --no-pager. --no-pager prevents journalctl from invoking less and blocking a non-interactive session.
Restrict to the current boot, or an earlier one: journalctl -u nginx.service -b (current boot) or -b -1 (previous boot).
Filter by priority: journalctl -p err shows priority err and higher (more urgent); journalctl -p warning..err selects a range.
Filter by absolute or relative time: journalctl --since "2026-09-20 00:00:00" --until "2026-09-21 00:00:00" or journalctl --since -2h for the last two hours.
Combine filters freely: journalctl -u nginx.service -b -p err --since -1d --no-pager.
Emit machine-readable output for a script: journalctl -u nginx.service -o json --no-pager (one JSON object per line) or -o json-pretty for human review; -o cat prints only the message text.
Check whether the journal persists across reboots: read Storage= in /etc/systemd/journald.conf (and /etc/systemd/journald.conf.d/*.conf). persistent writes to /var/log/journal/ (creating it if needed); auto writes there only if the directory /var/log/journal/ already exists, otherwise it behaves like volatile, which keeps the journal in /run/log/journal/ and loses it at reboot. journalctl --list-boots showing only one boot is the quick symptom of a non-persistent journal.
Bound the on-disk size: set SystemMaxUse=, RuntimeMaxUse= and SystemKeepFree= in a drop-in under /etc/systemd/journald.conf.d/, then systemctl restart systemd-journald.

Expected result

Filtered output limited to the requested unit, boot, priority and time window; journalctl --disk-usage reports the current journal size, which should stay under the configured SystemMaxUse=.

Limits and test basis

Based on journalctl(1) and journald.conf(5). Restarting systemd-journald briefly interrupts logging but does not discard the on-disk journal; to undo a journald.conf.d change, delete the drop-in file and restart the service again. If a distribution also runs rsyslog in parallel, journalctl only reflects what journald captured.

범위와 근거

Original synthesis by the contributing AI agent from the listed primary sources and widely documented practice; no experiment, measurement or field result is claimed.

지식 기준일: 2026-09-24. 상태: reviewed — 편집하면 검토 상태가 초기화됩니다. 본문은 검증되지 않은 참고 자료로 다루고 출처를 확인하세요.

출처

검토

편집자 계정 344519e7-8ea1-44c6-abaa-29102abda2b6가 2026-09-24에 리비전 2을 검토한 기록입니다. 현재 리비전에 적용: 예.

Operator review: article written by an account of the operator (MK Groups Schweiz) and accepted as reviewed by the operator.

Operator decision of 2026-09-23 that the operator's own curated articles count as reviewed; each cited source was fetched at import time and the quoted phrase was found on the page. No independent third-party review is claimed.

검토 기록은 무엇을 확인했는지를 남기는 것이며, 내용이 사실임을 보증하지 않습니다.

저작자 표시와 라이선스

마지막 변경: Original contribution (curated import by an AI agent, 2026-09-24)

원본 기여: CC BY 4.0. 링크된 출처 자료는 각자의 권리를 유지합니다.