For 日本の基盤モデル開発チームおよびhpc・分散学習エンジニア
H200 InfiniBand NDR 通信障害と Slurm 強制終了を瞬時に切り分け
大規模マルチノード環境で発生するmlx5 RDMAリトライ超過、host cgroup OOM、Xid 79を後続の全ランクタイムアウトから自動分離します。
Free 30-day Team evaluation. No card or automatic subscription. Work email verification required.
国内H200マルチノード分散学習の障害ログ再生
Upload your log file. Review the selected evidence and masking, then run diagnosis. Keep the original log for any follow-up questions.
Before uploading, review cloud data handling and local options.
Upload your log file. Large files are processed in your browser. Only selected evidence is submitted when you run diagnosis.
Try Denpex for 30 days. FREE.
No credit card. No automatic subscription. See whether Denpex helps with an incident you already understand.
Start your free 30-day Team evaluation
Up to 50 diagnoses a day for 30 days. Verify your work email to activate an eligible company evaluation, then replay a resolved incident and compare the evidence and next steps with your team's confirmed cause.
What a useful evaluation should establish
原因不明の再実行による計算資源の浪費を防ぎ、クラウド事業者へのエスカレーション時間を大幅に短縮します。
Use Denpex alongside your existing telemetry tools to investigate submitted incident evidence. With monitoring configured on a supported plan, detected failures can trigger alerts and an automatic diagnosis from the captured evidence.
Inside Denpex
See the evidence, not just the claim
Follow the causal chain, inspect the quoted evidence and prepare the next handoff. These actual product captures use founder-account examples and the VS Code extension, with the source identified under each image. Open a capture to inspect it at full size.
Follow the failure through the cascade

Prepare the hardware escalation

Ask for the evidence that is missing

Keep the investigation in the editor

GMO GPUクラウド · ABCI 3.0 (H200) - Observed Runtime Evidence
Incident pattern summary
H200 8基ノードを複数台接続した学習ジョブで、特定ノードのInfiniBandポート瞬断やSlurm OOMにより全ランクがハングした際、起点ランクのみを証拠付きで特定します。
jp-h200-node05:3120:3154 [1] misc/ibvwrap.cc:284 NCCL WARN Call to ibv_poll_cq returned error 12 (Transport retry counter exceeded)
slurmstepd: error: Detected 1 oom_kill event in StepId=88412.0Recommended verification flags
Set these environment flags in your training container or launch script to capture high-resolution collective logs:
NCCL_DEBUG=INFONCCL_IB_HCA=mlx5TORCH_NCCL_DUMP_ON_TIMEOUT=1CUDA_DEVICE_ORDER=PCI_BUS_IDDiagnostic Scope Boundary
Denpexはログと設定出力の解析のみを行い、利用者クラスタや物理スイッチへ直接変更を加えません。
Other GPU Cloud Failure Workflows
Compare evidence patterns across multi-node fabrics, Kubernetes pods, and bare-metal environments.