domains / families / devops / dynamo-troubleshoot

dynamo-troubleshoot

separate

Diagnose failed or unhealthy Dynamo deployments. Use when pods, model-cache jobs, PVCs, workers, frontend/router health, endpoints, or benchmark jobs fail; use recipe-runner/router-starter before this for normal bring-up.

When to use

• Turn a Dynamo failure into a clear problem class, strongest signal, and next action. Start with read-only evidence, avoid secrets, and fix one layer at a time.

When not to use

• Read-only. Never mutates the cluster; remediation commands are returned, not executed.
• Will not collect secrets or print Hugging Face tokens; some failure modes (auth) may need user-side inspection.
• Bundle size grows with deployment size; on very large namespaces, scope with `--deployment-name`.
• Does not validate disagg transport — use `dynamo-interconnect-check` for that.

Skill page

Source