Skip to content
Fleet

Freeze

The freeze commands let you stop a crash-looping service and prevent systemd from restarting it, while recording the frozen state in the registry.

fleet freeze

Stop an app, disable its systemd service, and mark it as frozen in the registry. Fleet will not start the service again until you explicitly unfreeze it.

Frozen apps appear with a frozen health state in fleet status.

Usage

Terminal window
fleet freeze <app> [reason]

Arguments

ArgumentRequiredDescription
appYesApp name
reasonNoHuman-readable reason (stored in registry, shown in status)

Examples

Terminal window
$ fleet freeze worker "OOM crash loop, investigate memory usage"
✓ Frozen worker: OOM crash loop, investigate memory usage
Terminal window
$ fleet freeze myapp
✓ Frozen myapp

What freeze does

  1. Calls systemctl stop <service>
  2. Calls systemctl disable <service>
  3. Sets frozenAt and optionally frozenReason on the app entry in registry.json
  • MCP tool: fleet_freeze

fleet unfreeze

Clear the frozen state, re-enable the systemd service, and start it.

Usage

Terminal window
fleet unfreeze <app>

Arguments

ArgumentRequiredDescription
appYesApp name (must currently be frozen)

Examples

Terminal window
$ fleet unfreeze worker
✓ Unfrozen worker — service enabled and started

What unfreeze does

  1. Removes frozenAt and frozenReason from the registry entry
  2. Calls systemctl enable <service>
  3. Calls systemctl start <service>
  • MCP tool: fleet_unfreeze