systemd-journald, A Journal That Survives The Reboot
systemd-journald on EL 10: a drop-in that moves the journal to persistent storage, seals it, and puts a ceiling on the disk it may take. The live test reads the EFFECTIVE settings back out of systemd rather than the file it wrote, finds a real journal file on disk, round-trips a message through it, and runs a vacuum. Original role, live-tested on Rocky Linux 10.
Verification
Live-testedReally deployed to a container sandbox, proven idempotent (a second run changes nothing), verified against the role’s assertions, then torn down.
Conformance
- Static validation (yamllint · ansible-lint)
Provenance
- SHA-256 checksum
- Signature (pending)
Functional
- Live-tested - applied, verified, destroyed
Last verified 2026-09-26 · podman 4.9.3 · ansible 2.21.4 · how we verify
Cite it in your README
badge · attributionPaste this beside the module in the repository that uses it. The badge is rendered from this artifact's verification record, so it reads live-tested because the record says so, and the link lands on this page.
[](https://www.iac-bazaar.com/catalog/ansible-journald-retention?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Ansible role 1.0.0, live-tested on IaC Bazaar: [systemd-journald, A Journal That Survives The Reboot](https://www.iac-bazaar.com/catalog/ansible-journald-retention?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```yaml
# systemd-journald, A Journal That Survives The Reboot: https://www.iac-bazaar.com/catalog/ansible-journald-retention (download from your IaC Bazaar account)
```Preview:
Documentation
journald-retention
A journal that survives the reboot somebody is trying to explain. The role
writes one drop-in under /etc/systemd/journald.conf.d, moves the journal to
persistent storage, seals it, and puts a ceiling on how much disk it may take.
The live test reads the EFFECTIVE settings back out of systemd and then finds
the journal file on disk.
Nothing to install and no version to pin. journald is systemd, which is already there. What the role owns is the policy: where the journal lives, how much disk it may take, how far back it keeps, and whether it is sealed.
EL 10 ships no /etc/systemd/journald.conf at all. The defaults are compiled
in, so a drop-in is the whole configuration and there is nothing of the
distribution's to preserve or fight.
Nothing validates journald.conf. A key journald does not recognise is ignored
with a line in its own log, and the daemon starts perfectly well with a policy
that does nothing. That is why the verify asks
systemd-analyze cat-config systemd/journald.conf for the settings in FORCE
rather than reading back the file it just wrote.
SystemKeepFree wins over SystemMaxUse. On a small disk the journal
yields rather than filling it, which means a large SystemMaxUse is a ceiling
and not a promise.
License
Commercial - IaC Bazaar EULA. (c) IaC Bazaar.
Usage code & full reference need an account
The complete copy-paste usage, the full input/output reference, and operational notes are free with an account - shown here and bundled in the download. Sign in and this section fills in.
- Variables
- Test
Related modules
ansible-alertmanager
Prometheus Alertmanager from the upstream release (sha256-verified) as a hardened system service on loopback, its cluster gossip listener switched off and its configuration checked by amtool before it lands. The live test posts an alert through the API and reads it back active, held by the default receiver, and expects no 9094 listener at all. Original role, live-tested on Rocky Linux 10.
ansible-alloy
Grafana Alloy from the upstream release (sha256-verified) as a hardened system service on loopback with --disable-reporting, a self-scrape pipeline that proves the collector runs, and its configuration checked by alloy validate before it lands. The live test reads Alloy's own metrics and asks the component API for the scrape component's health. Original role, live-tested on Rocky Linux 10.
ansible-blackbox-exporter
Prometheus Blackbox exporter from the upstream release (sha256-verified) as a hardened system service on loopback with HTTP and TCP modules, checked by --config.check before the file lands. The live test has it probe itself over HTTP and TCP (probe_success 1) and a port with nothing behind it (probe_success 0): it measures, not only answers. Original role, live-tested on Rocky Linux 10.
ansible-grafana-server
Grafana on loopback with a secret key of yours: every install that never set one shares the package's, which encrypts the data-source credentials in its database. Secure cookies and HSTS for the TLS proxy in front; public snapshots, plugin update checks, feedback links and Gravatar switched off. Settings verified through the API, not the file. Original role, live-tested on Rocky Linux 10.
ansible-grafana
Grafana (sha256-verified) on EL 10 from the upstream release, as a hardened systemd service on loopback; the live test reads back the datasource this role provisioned, creates a dashboard and finds it by search, sees anonymous and wrong-password requests refused, and reads the build metric naming the version installed. Original role, live-tested on Rocky Linux 10.
ansible-jaeger
Jaeger v2, the tracing backend built on the OpenTelemetry Collector, from the upstream release (sha256-verified against the right checksum file) as a hardened system service on loopback with badger storage and the query API on loopback. The live test pushes a span over OTLP and reads the trace back by id with its name and service. Original role, live-tested on Rocky Linux 10.