← All posts systemd

Choose a systemd Restart policy without creating a crash loop

The Tryssh team ·

For systemd Restart policy, the safest approach is a bounded operational change, not a command pasted without context. This runbook starts with effective state, shows the smallest candidate action, and finishes by repeating the real user or system path.

TL;DR: Restart decides which exit causes trigger another start, while RestartSec and start limits control retry pacing and containment. Capture a baseline with systemctl show example.service -p Restart -p RestartUSec -p NRestarts -p StartLimitBurst -p StartLimitIntervalUSec, make the reviewed change only when the evidence matches, then verify with systemd-analyze verify /etc/systemd/system/example.service and keep the rollback ready.

Audience: Linux operators who can read a unit file and have sudo access plus a second recovery session. This guide assumes familiarity with systemd and a change window appropriate to the system.

Choose a systemd Restart policy without creating a crash loop observe, interpret, change, and verify workflow

The direct answer

An intentional failure follows the documented retry policy and remains inside the start-rate budget. That is the success condition for systemd Restart policy; command completion by itself is not enough.

The important boundary is unit definition, manager state, process state, and dependency ordering. Restart decides which exit causes trigger another start, while RestartSec and start limits control retry pacing and containment. If an observation does not identify which side of that boundary failed, collect a narrower observation before changing state.

How the mechanism works

For systemd Restart policy, use this mental model: systemd first loads unit configuration, calculates a dependency transaction, creates a cgroup, then supervises the processes associated with that unit. The model prevents a common mistake—treating configuration text, control-plane acceptance, process state, and end-user behavior as the same proof.

Follow four stages:

  1. Observe: identify the exact host, object, version, owner, and active configuration.
  2. Interpret: write the expected result, the abnormal result, and what would remain inconclusive.
  3. Change: apply one reviewed action at the narrowest layer that contradicts the baseline.
  4. Verify: repeat the original path and compare the same evidence, including adjacent safety controls.

Preflight and safety boundary

Keep the current service process and a second shell available until syntax, effective properties, and the real request path have all been verified.

Before systemd Restart policy, record UTC time, the current version or digest, the exact target, recent changes, and who owns the workload. The rollback for this runbook is: remove the restart-policy drop-in, reload, reset-failed if appropriate, and start the last known-good service once.

Do not continue if the target identity is ambiguous, the current state cannot be saved, the only recovery session would be at risk, or the proposed command affects more objects than the brief names.

Capture the read-only baseline

Run these commands one at a time. Replace example names and addresses deliberately; do not paste production secrets into a transcript.

systemctl show example.service -p Restart -p RestartUSec -p NRestarts -p StartLimitBurst -p StartLimitIntervalUSec
journalctl -u example.service --since '30 minutes ago' --no-pager

Interpret the baseline before moving on:

  • Expected: an intentional failure follows the documented retry policy and remains inside the start-rate budget.
  • Abnormal: NRestarts climbs continuously, the root failure is unchanged, or a clean operator stop unexpectedly restarts.
  • Inconclusive: missing output can also mean the wrong context, permissions, namespace, log window, binary, or target. Prove those assumptions before treating absence as health.

Save the decisive output, exit status, and timestamp. Redact credentials, customer data, private topology, tokens, and complete environment dumps.

Apply the smallest candidate change

The following is state-changing example syntax, not an instruction to run it unchanged:

sudo systemctl edit example.service

For systemd Restart policy, the proposed change is acceptable only when the read-only baseline predicts its effect and the rollback is available. The key risk is: Restart=always can turn deterministic bad configuration into sustained load and noisy log churn.

Prefer an immutable artifact, validated configuration, dry-run, transaction, candidate object, or staged target when the tool supports one. Record the exact command and UTC time so later telemetry can be correlated to the change.

Verify the result from the outside in

systemd-analyze verify /etc/systemd/system/example.service
systemctl restart example.service
systemctl show example.service -p NRestarts -p Result

Verification for systemd Restart policy has three layers:

  1. The control plane or command reports the intended effective state.
  2. The process, resource, or data path reflects that state without a new pressure signal.
  3. The original user-visible or dependent-system path succeeds from an independent vantage point.

If systemd-analyze verify /etc/systemd/system/example.service succeeds but the original path still fails, stop. The change may have repaired a local symptom while DNS, policy, routing, caching, dependency, or client state remains broken.

Failure branches

The baseline does not match this runbook

When NRestarts climbs continuously, the root failure is unchanged, or a clean operator stop unexpectedly restarts, do not force the candidate command. Return to identity and scope, compare a healthy peer only through effective settings, and name a new falsifiable mechanism.

The change succeeds but behavior does not

A successful sudo systemctl edit example.service proves that one interface accepted a request. It does not prove convergence, readiness, data compatibility, external routing, or client recovery. Re-run the same evidence at each downstream boundary.

The change makes the system worse

Execute the written rollback: remove the restart-policy drop-in, reload, reset-failed if appropriate, and start the last known-good service once. Preserve the failed candidate and relevant logs long enough to explain the outcome; do not destroy the evidence with broad cleanup or repeated restarts.

Operator checklist

  • Confirm the exact target, context, identity, version, and active owner.
  • Capture the read-only baseline and one disconfirming observation.
  • Label sudo systemctl edit example.service as state-changing during review.
  • Keep recovery access and rollback independent of the path being edited.
  • Change one layer, record UTC time, and wait for its real convergence boundary.
  • Verify the original path, adjacent controls, resource pressure, and persistence.
  • Update the runbook when observed behavior differs from the source-reviewed model.

Investigate it in Tryssh

Tryssh keeps the command, approval boundary, output, and verification beside the host conversation.

Tryssh can preserve this evidence loop and show a state-changing command for human approval. It does not make the operator's identity, recovery access, rollback, or platform authority decisions.

Evidence and review status

This systemd Restart policy runbook was source-reviewed on 2026-07-29 against current first-party documentation. The commands are illustrative and use example targets. The page does not claim that the change was reproduced across every distribution, managed service, version, network, or workload.

Limitations and trade-offs

Restart=always can turn deterministic bad configuration into sustained load and noisy log churn. Managed platforms may generate configuration, restrict privileges, replace local state, or expose a different control plane than the upstream project. Confirm the installed version and provider contract before applying a repair.

Search visibility is not proof of operational correctness. Treat this page as a decision aid, preserve independent recovery, and stop when the evidence contradicts its assumptions.

Related operator runbooks

Continue with systemd timer vs cron, systemd WorkingDirectory, the systemd foundation guide, and the SSH hardening checklist.

Sources and further reading