NCCL Hang Detection
NCCL hangs can be hard to detect because they don't produce errors until the watchdog timeout. Proper monitoring helps catch them early.
NCCL hangs can be hard to detect because they don't produce errors until the watchdog timeout.
What this failure is
NCCL Hang Detection is a Communication failure seen during ML training runs. NCCL hangs can be hard to detect because they don't produce errors until the watchdog timeout. Proper monitoring helps catch them early. Common tags: Nccl, Hang, Detection, Monitoring.
Is this what broke your run? Paste your log.
You're reading about NCCL Hang Detection. Paste your own crash log or traceback below and get the real root cause for YOUR run, not this generic entry. No account, no card. Logs are masked at ingress and never saved to account history.
Want 14 days on the Scale plan?
Request a work-email trial for up to 50 diagnoses a day, alerts, history, and follow-up questions. No credit card or automatic subscription.
Why it happens (the mechanism)
NCCL watchdog timeout is 30 minutes default. Hangs without errors are hard to detect. NCCL_DEBUG=INFO adds overhead. No native monitoring in NCCL. Taken together, these mechanisms explain why the failure is reproducible, why it tends to surface on specific workloads or scales, and why generic mitigation attempts often fall short without addressing the underlying cause.
What you'll observe
- Training hangs with no error
- NCCL operation takes longer than expected
- No error message before hang
Common symptoms and what they mean
| Symptom | Why it happens |
|---|---|
| GPU utilization drops to 0% on some ranks | NCCL watchdog timeout is 30 minutes default |
| NCCL operation never completes | Hangs without errors are hard to detect |
| No progress for minutes or hours | NCCL_DEBUG=INFO adds overhead |
Which systems are affected
- Multi-node training with NCCL
- Production distributed training
- Long-running training jobs
How to confirm this is the problem
Use this checklist to test the hypothesis against a small reproduction. No single line proves the root cause, so preserve the preceding events and compare one variable at a time.
- ✓Reproduce the failure from a clean checkpoint/seed: the symptom must appear without warm-up state from a previous run.
- ✓Verified signal present: GPU utilization drops to 0% on some ranks
- ✓Verified signal present: NCCL operation never completes
- ✓Verified signal present: No progress for minutes or hours
- ✓A targeted fix from the "How to fix it" section eliminates or substantially reduces the symptom within one validation pass.
The fix and the prevention pattern
The root cause is on this page and stays free. A free account adds the exact remediation steps, keeps your diagnoses instead of discarding them, and unlocks the fix on every entry in the encyclopedia.
Sign up free. Unlock the full analysisNo credit card · 3 free diagnoses · Instant access
Diagnose this failure in VS Code
Select the traceback or open the failed terminal, then run Denpex locally to see the initiating rank, collateral failures, exact fix, and verification command without uploading the log.
Install the free VS Code extensionNCCL errors in context
NCCL is where a distributed job reports failure, which is not the same as where it failed. The hub lists every common NCCL error next to what it actually indicates, and the environment variables that tell them apart.
Compare every nccl error side by sideRelated failures to investigate next
Root cause
- NCCL watchdog timeout is 30 minutes default
- Hangs without errors are hard to detect
- NCCL_DEBUG=INFO adds overhead
- No native monitoring in NCCL
The fix and how to prevent it
Unlock the full remediation runbook
14 days on the Scale plan, up to 50 diagnoses a day. Step-by-step remediation, the RMA evidence payload, and multi-node correlation on your own logs. No card, and it does not roll into a subscription.
Don't just read the fix, diagnose your run
The encyclopedia tells you what went wrong. Denpex tells you what went wrong in YOUR training run. With your logs, your config, and your stack.