Skip to content

Auto-restart

Auto-restart monitors explicitly selected services and retries a restart after repeated health failures. It is disabled by default. Use it for recoverable application failures; investigate repeated failures rather than raising the retry limit.

Enable it for a service

  1. Open the service page and select Tools → Auto-restart.
  2. Turn on Enable auto-restart and Restart on unhealthy checks.
  3. Under This Service, turn on Enable auto-restart for the selected service.
  4. Start with the defaults. For a known slow application, use Override defaults to allow a longer Grace period (sec) before health failures count.
  5. Select Save to File and check the saved indicator. Apply in Memory is temporary and is lost when DUMB restarts.
  6. Check the service's health/restart indicator on the dashboard. If it repeatedly restarts, open Service Logs and investigate the underlying error.

An empty service list monitors nothing, even when the global switch is enabled. A deliberate manual stop disables monitoring for that service until it is started again.

Choose when DUMB should try to recover a service that stops responding. DUMB 2.24.0 · Frontend 1.92.0 · Example data.
Technical details: monitoring and restart lifecycle

How it works

flowchart LR
    Ready[Stack ready/degraded] --> Grace[Wait service grace period]
    Grace --> Check[Check service health]
    Check -->|Consecutive unhealthy threshold| Limit{Within retry limit?}
    Limit -->|Yes| Restart[Wait backoff, restart]
    Restart --> Grace
    Limit -->|No| Hold[Wait for attempts to age out]
    Check -->|Healthy, degraded, or starting| Check

DUMB checks the tracked process, configured ports, and an allowlisted read-only application endpoint where available. Monitoring pauses while the stack is starting. After a restart, DUMB records success only when health checks pass.

Health states and application probes

State Meaning Restart behavior
Healthy Process, ports, and applicable probe passed Reset consecutive failures
Degraded Reachable, with a warning or an unsupported/protected optional probe Keep running; show the reason
Starting Application reports initialization or migration Wait without counting a failure
Unhealthy Process/port failure or a restart-relevant application failure Count toward the threshold

Indexer/provider warnings, missing articles, and content-health failures are not restart signals. Check the provider, storage, or application error first; restarting a healthy application will not usually repair them.

Technical details: application probes

Current application probes include InfiniDysk /health, Servarr /ping, Jellyfin /health, Emby ping, Plex /identity, Seerr status, TPA health, PostgreSQL pg_isready, pgAdmin ping, and rclone's local RC version endpoint when enabled. Unknown services retain process/port checks.

Indexer/provider warnings, missing articles, and content-health failures are not restart signals. Restarting a healthy application does not usually repair those conditions. InfiniDysk's migration response, 503 {"status":"migrating"}, is treated as Starting rather than a restart failure.

Technical details: restart JSON and field reference

Configuration

Set defaults under dumb.auto_restart:

{
  "dumb": {
    "auto_restart": {
      "enabled": true,
      "restart_on_unhealthy": true,
      "healthcheck_interval": 30,
      "unhealthy_threshold": 3,
      "max_restarts": 3,
      "window_seconds": 300,
      "backoff_seconds": [5, 15, 45, 120],
      "grace_period_seconds": 30,
      "services": [
        {
          "process_name": "Riven Backend",
          "enabled": true,
          "grace_period_seconds": 60
        }
      ]
    }
  }
}

This example enables monitoring for Riven Backend. The shipped defaults have enabled: false and services: [].

Field Shipped default Meaning
enabled false Global switch
restart_on_unhealthy true Allow unhealthy checks to trigger a restart
healthcheck_interval 30 Seconds between checks
unhealthy_threshold 3 Consecutive failures before retry
max_restarts 3 Attempts allowed within the rolling window
window_seconds 300 Length of that window in seconds
backoff_seconds [5, 15, 45, 120] Explicit delays between attempts
grace_period_seconds 30 Wait after stack readiness or a later launch
services [] Policy objects containing an exact process_name

Use process names from GET /process/processes, not guessed display labels. There is no separate health_check configuration object.

Backoff schedule

The delay comes from the configured list, not an exponential multiplier. The example uses 5, 15, 45, then 120 seconds for later attempts. Any attempt beyond the list uses its last entry.

Restart limits

The default permits three attempts within a rolling five-minute window. Attempts age out automatically. A manual start re-enables monitoring after an intentional stop but does not erase the recent-attempt record.

A slow application can receive a longer per-service grace period without delaying other services. Choose it from observed startup time. The stack's readiness deadline is separate; see Startup lifecycle.

Technical details: process and port checks

Health checks

Checks reject missing/zombie PIDs and test the service's configured port, frontend_port, backend_port, and webdav_port, including corresponding environment values. Incorrect configured ports can therefore create false failures.

A longer grace period helps a known slow startup. It does not fix a wrong port, failed database connection, or broken mount.

Monitoring restart status

Hover the dashboard or service-page health/restart indicator for its current reason. Notifications can send restart success/failure events when their severity and routing rules match.

Technical alternative: inspect restart state through the API

For API access:

curl 'http://localhost:3005/api/process/service-status?process_name=Riven%20Backend&include_health=true'

Add an Authorization header when DUMB authentication is enabled. The response includes health_status, health_reason, health_details, and a restart object:

Restart field Meaning
restart_attempts, restart_successes, restart_failures Recorded outcomes
recent_restart_attempts Attempts still in the rolling window
pending, next_restart_time Scheduled retry state
last_restart_time, last_exit_time, last_exit_reason Recent lifecycle evidence
unhealthy_count, unhealthy_threshold Consecutive failure count and policy
disabled Whether monitoring is disabled for this process

Live process updates arrive through /ws/status. Notifications can deliver success/failure events; the destination's severity filter still applies.

Disabling auto-restart

Open Tools → Auto-restart on the service page. Clear Enable auto-restart for that service and select Save to File. Reopen the panel to confirm the switch is off. To pause monitoring for every service, turn off the global Enable auto-restart switch and save.

Technical alternative: disable monitoring in configuration

Remove the entry from dumb.auto_restart.services or set that entry to "enabled": false. Set dumb.auto_restart.enabled to false to disable all monitoring while retaining saved service entries.

Troubleshooting

Symptom Check first
Repeated restarts Actual service error, dependency health, mounts, and configured ports
No automatic restart Global switch, exact enabled service entry, startup/grace state, and rolling-window limit
Long wait before retry Current backoff entry and recent attempts; verify the underlying failure before shortening delays