Skip to content

FFprobe monitor

When a Sonarr or Radarr import is stuck on media analysis, this automatic monitor can help release a stalled read. It is enabled by default and operates only for DUMB-managed Sonarr/Radarr instances. It cannot repair an unavailable mount, missing media, or a provider outage.

Check a stalled import

Check the storage path before relying on the monitor to release a stalled analysis:

flowchart TD
    accTitle: Investigate a stalled media analysis
    accDescr: Distinguish unavailable storage from a stalled probe, then inspect the monitor result without repeatedly restarting the application.
    Logs["Read the affected app's Service Logs"] --> Storage{"Storage healthy and file available?"}
    Storage -->|No| Fix["Restore storage or provider access first"]
    Fix --> Logs
    Storage -->|Yes| Monitor["Read DUMB ffprobe activity in Realtime Logs"]
    Monitor --> Wait["Allow the bounded check to finish"]
    Wait --> Progress{"Import progressing?"}
    Progress -->|Yes| Check["Confirm the item imported correctly"]
    Progress -->|No| Evidence["Keep the file context and error for diagnosis"]
  1. Open the affected Sonarr/Radarr service page and read Service Logs. Note the file and error rather than repeatedly restarting the application.
  2. Check that its storage service is healthy and that the file is available in the application's own interface.
  3. Open Realtime Logs → Logs from the sidebar and filter for DUMB/ffprobe monitor activity. Allow the monitor's bounded check to finish, then see whether the import progresses.
  4. If storage is unavailable, repair that connection first. If the same file repeatedly times out, keep the error and file context for troubleshooting.

Change monitor settings

Most users can leave the automatic defaults in place. There is no dedicated frontend panel for the shared monitor. If tuning is needed, ask the person managing DUMB to review the configuration reference below; the service's DUMB Config tab contains that service's own controller settings, not the shared monitor configuration.

Technical details: process selection, configuration, and probe limits

The monitor finds eligible ffprobe processes beneath DUMB-managed Sonarr or Radarr and runs a bounded probe of the same input. This can release a stalled media read, but it does not repair an unavailable mount or provider.


When it runs

The monitor activates only when at least one Sonarr or Radarr instance is enabled. If neither service is running, the worker stays idle.


How it works

  1. Collects running Sonarr/Radarr process IDs.
  2. Finds descendant ffprobe processes.
  3. Selects processes in uninterruptible sleep (D) whose total process age exceeds the configured minimum.
  4. Runs ffprobe on the same input within the configured timeout and per-cycle limits.

Configuration in dumb_config.json

For a manual change, stop DUMB and keep a copy of /config/dumb_config.json. Merge the intended values under dumb.ffprobe_monitor; do not replace the whole configuration with this example. Save valid JSON, restart DUMB, and check the main DUMB log for monitor activity.

{
  "dumb": {
    "ffprobe_monitor": {
      "enabled": true,
      "interval_sec": 10,
      "min_process_age_sec": 30,
      "min_poke_interval_sec": 60,
      "poke_timeout_sec": 30,
      "max_pokes_per_cycle": 3,
      "cache_ttl_sec": 3600,
      "ffprobe_path": "ffprobe"
    }
  }
}

Settings reference

Setting Description
enabled Turns the monitor on or off.
interval_sec Poll interval between checks.
min_process_age_sec Minimum age for an ffprobe process before it is considered stuck.
min_poke_interval_sec Minimum time between pokes for the same file path.
poke_timeout_sec Timeout for the probe used to nudge the stuck process.
max_pokes_per_cycle Maximum number of ffprobe pokes per polling cycle.
cache_ttl_sec How long to cache recently poked file paths.
ffprobe_path Path or command for ffprobe.

Operational notes

Scope

The monitor only targets ffprobe processes spawned under Sonarr/Radarr. It does not touch other ffprobe instances on the host.

Technical alternative: select a custom ffprobe binary

If your media stack uses a bundled ffprobe, set ffprobe_path to the full binary path.


Troubleshooting

  • If ffprobe checks never trigger, verify Sonarr/Radarr instances are enabled and visible to the DUMB process handler.
  • If the monitor logs repeated timeouts, lower max_pokes_per_cycle or increase poke_timeout_sec.