verifyfirst

preflight · 6 checks

I restarted a service

A systemd unit, container or daemon was reloaded to pick up new code or config.

Before you call it done

  1. Compare the unit's ExecStart on disk against the live process.systemctl show -p ExecStart -p MainPID UNIT && ps -p $MAINPID -o args=guards against NS-005 NS-038
  2. Confirm the binary the process is executing is the one you replaced.stat -Lc %i /proc/$MAINPID/exe # against stat -c %i /path/to/binaryguards against NS-038
  3. Ask the socket, not the manager. Type=simple is active before execve.ss -ltnp 'sport = :PORT'guards against NS-026 NS-037
  4. Check it is not crash-looping between your observations.systemctl show -p NRestarts -p ExecMainStartTimestamp UNITguards against NS-027
  5. Ask the running service what config it loaded, not the filesystem what it holds.For Caddy: the admin API's live config. For sshd: sshd -T as root.guards against NS-008 NS-023
  6. Confirm the unit's workers stopped, not just the unit.systemctl show -p KillMode UNIT; then ps for the children by nameguards against NS-087 NS-086

Plain text: /recipes.txt · all tasks