NCCL BUFFSIZE Oversized, Socket Transport Stall
Setting NCCL_BUFFSIZE too large causes NCCL Socket transport to stall or hang during communication. This is a configuration error where users increase the buffer size hoping for better performance but exceed the socket buffer limits. Denpex detects the oversized buffer from NCCL debug logs.
Setting NCCL_BUFFSIZE too large causes NCCL Socket transport to stall or hang during communication.
What this failure is
NCCL BUFFSIZE Oversized. Socket Transport Stall is a Communication failure seen during ML training runs. Setting NCCL_BUFFSIZE too large causes NCCL Socket transport to stall or hang during communication. This is a configuration error where users increase the buffer size hoping for better performance but exceed the socket buffer limits. Denpex detects the oversized buffer from NCCL debug logs. Common tags: Nccl, Buffsize, Socket, Buffer.
Is this what broke your run? Paste your log.
You're reading about NCCL BUFFSIZE Oversized, Socket Transport Stall. 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 an evaluation code. A verified workplace organization activates up to 50 diagnoses a day, alerts, history, and follow-up questions. No credit card or automatic subscription.
Why it happens (the mechanism)
NCCL_BUFFSIZE controls the per-channel buffer size for NCCL communication. When Socket transport is used, the buffer size must fit within the OS socket buffer limits (rmem_max, wmem_max). Setting NCCL_BUFFSIZE to a value larger than the OS socket buffer limits causes the socket write to block indefinitely. IB transport has its own memory registration and doesn't have this socket buffer limit. 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 at NCCL communication after setting NCCL_BUFFSIZE to a very large value
- Socket transport stalls while IB transport works fine with the same buffer size
- Increasing NCCL_BUFFSIZE made performance worse instead of better
Common symptoms and what they mean
| Symptom | Why it happens |
|---|---|
| NCCL hangs during all-reduce or all-gather after NCCL_BUFFSIZE was manually increased | NCCL_BUFFSIZE controls the per-channel buffer size for NCCL communication |
| NCCL_DEBUG=INFO shows Socket transport timeouts or retransmissions | When Socket transport is used, the buffer size must fit within the OS socket buffer limits (rmem_max, wmem_max) |
| Watchdog timeout after increasing NCCL_BUFFSIZE | Setting NCCL_BUFFSIZE to a value larger than the OS socket buffer limits causes the socket write to block indefinitely |
| Training works with default NCCL_BUFFSIZE but hangs with custom value | IB transport has its own memory registration and doesn't have this socket buffer limit |
Which systems are affected
- Clusters using Socket transport (no IB/EFA)
- Users who manually tuned NCCL_BUFFSIZE hoping for better performance
- TCP-based multi-node training over Ethernet
- Environments where /proc/sys/net/core/rmem_max and wmem_max are too low for the configured buffer size
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: NCCL hangs during all-reduce or all-gather after NCCL_BUFFSIZE was manually increased
- ✓Verified signal present: NCCL_DEBUG=INFO shows Socket transport timeouts or retransmissions
- ✓Verified signal present: Watchdog timeout after increasing NCCL_BUFFSIZE
- ✓Verified signal present: Training works with default NCCL_BUFFSIZE but hangs with custom value
- ✓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, saved history, and the fix on every entry in the encyclopedia.
Sign up free. Unlock the full analysisNo credit card. Daily allowance follows verified trust tier. 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_BUFFSIZE controls the per-channel buffer size for NCCL communication
- When Socket transport is used, the buffer size must fit within the OS socket buffer limits (rmem_max, wmem_max)
- Setting NCCL_BUFFSIZE to a value larger than the OS socket buffer limits causes the socket write to block indefinitely
- IB transport has its own memory registration and doesn't have this socket buffer limit
The fix and how to prevent it
Evaluate Denpex on your own logs
Request a Scale evaluation code. A verified workplace organization activates 14 days with up to 50 diagnoses a day. Every account keeps its current diagnosis allowance and gets a verification path. No card or automatic 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.