NCCL WARN Ring via NET/Socket Call to connect returned Connection refused

An NCCL ring peer attempted a TCP connection before the expected listener was reachable. The destination rank may have crashed, advertised the wrong interface, or been blocked by host or network policy. This entry explains how to confirm the cause, apply the fix, and separate it from adjacent nccl failures.

The literal signature is "NCCL WARN Ring via NET/Socket Call to connect returned Connection refused". It is a communication failure associated with NCCL and ProcessGroupNCCL collectives. The line identifies the failing operation or subsystem, while the surrounding evidence decides whether it is the initiating fault or a downstream symptom.

An NCCL ring peer attempted a TCP connection before the expected listener was reachable. The destination rank may have crashed, advertised the wrong interface, or been blocked by host or network policy. The failure becomes visible at this call site because the operation first requires the missing resource, valid state, healthy peer, or correct result. Earlier log lines and a known-good control carry more causal value than the final wrapper exception.

• The workload stops or loses forward progress after emitting "NCCL WARN Ring via NET/Socket Call to connect returned Connection refused".
• A retry on the same configuration reproduces the failure because the causal state has not changed.
• The outer framework exception can hide the rank, node, allocation, or dependency that failed first.
• Increasing timeouts or reducing workload size can suppress the symptom without correcting the cause.

• NCCL and ProcessGroupNCCL collectives
• production-shaped multi-accelerator workloads
• containerized and bare-metal deployments of the same stack

Apply the following checklist to a small reproduction: each box below is a positive signal that you are looking at this exact failure rather than a sibling in the same taxonomy.

• ✓Find the first occurrence of "NCCL WARN Ring via NET/Socket Call to connect returned Connection refused" and preserve at least 100 lines before it.
• ✓Identify which rank, node, device, or process emitted the first related warning.
• ✓compare hostname resolution and NCCL_SOCKET_IFNAME across nodes, then test the advertised address from the source node. Check container network namespaces and firewall rules.
• ✓Repeat the same input after the targeted change and require the signature to disappear.
• ✓Resume from job start after every ring peer is reachable only after the control passes.

NCCL WARN Ring via NET/Socket Call to connect returned Connection refused

Timestamps and exact values vary across runs, but the pattern. An info-level start, an early WARN, an ERROR carrying the symptom. Is the actual fingerprint you should alert on. The Denpex platform flags this combination automatically.

find the destination host and port in NCCL_DEBUG=INFO output, then verify the destination rank is alive and listening. This changes the condition in the causal diagnosis instead of hiding the outer exception. The repeated control proves ownership before recovery from job start after every ring peer is reachable.

# Preserve evidence before restarting
NCCL_DEBUG=INFO NCCL_DEBUG_SUBSYS=INIT,NET,COLL torchrun train.py
ibstat
ethtool -S <interface>

# Find the exact signature in the complete log
rg -n -F -- "NCCL WARN Ring via NET/Socket Call to connect returned Connection refused" <log-file>

Adapt the snippet to your framework. The same pattern holds for PyTorch Lightning, Hugging Face Trainer, DeepSpeed, Megatron-LM, and vLLM training wrappers. Where the wrapper exposes a config flag (for examplelr_scheduler_type in Trainer), prefer the flag over the imperative API to keep the schedule declarative and reproducible.

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.

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.

• An NCCL ring peer attempted a TCP connection before the expected listener was reachable. The destination rank may have crashed, advertised the wrong interface, or been blocked by host or network policy.
• The decisive evidence is the first log line that precedes "NCCL WARN Ring via NET/Socket Call to connect returned Connection refused" and differs from a healthy run.
• A nearby failure remains a competing hypothesis until a control separates configuration, capacity, transport, and hardware causes.