hyperpod-node-debugger
Diagnose and remediate per-node issues on a HyperPod cluster (EKS or Slurm) — a specific node is unhealthy, unresponsive, stuck, or needs replacing. Covers on-node EFA, GPU / accelerator hardware (XID, ECC, NVLink, row-remap, DCGM), Slurm node down/drained, disk and memory pressure, per-node lifecycle-script failures, SSM agent, container runtime, kernel panics, pod networking. Read-only. Not for cluster-wide provisioning (→ hyperpod-cluster-debugger), NCCL (→ hyperpod-nccl), or MFU (→ hyperpod-mfu-debugger).
- Version
- 0.0.1
Pinned to revision 4e8964e24a5a, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/hyperpod-node-debugger/SKILL.md
- skills/hyperpod-node-debugger/LICENSE
- skills/hyperpod-node-debugger/references/node-diagnostics-detail.md
- skills/hyperpod-node-debugger/references/node-issue-catalog.md
- skills/hyperpod-node-debugger/scripts/check-efa-sg.sh
- skills/hyperpod-node-debugger/scripts/check-node-reachability.sh
- skills/hyperpod-node-debugger/scripts/check-vpc-config.sh
- skills/hyperpod-node-debugger/scripts/triage-cluster.sh
Every link opens the file at its source, pinned to the revision this page describes.