Gloo Connection refused to host 29500 during initial rendezvous
Gloo TCP store connection failed (connection refused or DNS resolution failed), ranks cannot reach the rendezvous point. This entry explains how to confirm the cause, apply the fix, and separate it from adjacent gdr-fabric failures.
Gloo Connection refused to host 29500 during initial rendezvous means Gloo TCP store connection failed (connection refused or DNS resolution failed), ranks cannot reach the rendezvous point. Preserve the first preceding error, then run the targeted control below.
- Symptom
Gloo Connection refused to host 29500 during initial rendezvous- Root cause
- Gloo TCP store connection failed (connection refused or DNS resolution failed), ranks cannot reach the rendezvous point. The decisive evidence is the first log line that precedes "Gloo Connection refused to host 29500 during initial rendezvous" and differs from a healthy run. A nearby failure remains a competing hypothesis until a control separates configuration, capacity, transport, and hardware causes.
- Recommended fix
- Verify MASTER_ADDR resolves correctly: getent hosts $MASTER_ADDR. Check firewall: nc -zv $MASTER_ADDR $MASTER_PORT. Ensure rank 0 starts first. For K8s, verify headless service DNS.
- How Denpex helps
- Denpex investigates Gloo Connection refused to host 29500 during initial rendezvous using the evidence you provide or your connected workload collects. Earlier rank, host or application evidence is needed to distinguish an initiating failure from a downstream report.
What this failure is
The literal signature is "Gloo Connection refused to host 29500 during initial rendezvous". It is a communication failure associated with GPUDirect RDMA, RoCE, GDRCopy, and NUMA topology. The line identifies the failing operation or subsystem, while the surrounding evidence decides whether it is the initiating fault or a downstream symptom.
Is this what broke your run? Paste your log.
You're reading about Gloo Connection refused to host 29500 during initial rendezvous. Paste your own traceback and relevant evidence for an investigation of your workload, with a next action or a specific missing fact. A reference entry does not establish your cause. No account or card for the free diagnosis. Review data handling before submitting sensitive logs.
Before uploading, review cloud data handling and local options.
Why it happens (the mechanism)
Gloo TCP store connection failed (connection refused or DNS resolution failed), ranks cannot reach the rendezvous point. 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.
What you'll observe
- The workload stops or loses forward progress after emitting "Gloo Connection refused to host 29500 during initial rendezvous".
- 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.
Common symptoms and what they mean
| Symptom | Why it happens |
|---|---|
| Gloo Connection refused to host 29500 during initial rendezvous | Gloo TCP store connection failed (connection refused or DNS resolution failed), ranks cannot reach the rendezvous point. |
| The same operation fails at a consistent stage of GPUDirect RDMA, RoCE, GDRCopy, and NUMA topology. | The decisive evidence is the first log line that precedes "Gloo Connection refused to host 29500 during initial rendezvous" and differs from a healthy run. |
| The first related warning appears before the final exception and names the causal subsystem. | A nearby failure remains a competing hypothesis until a control separates configuration, capacity, transport, and hardware causes. |
| A known-good control changes one variable and either reproduces or clears the failure. | Gloo TCP store connection failed (connection refused or DNS resolution failed), ranks cannot reach the rendezvous point. |
Which systems are affected
- GPUDirect RDMA, RoCE, GDRCopy, and NUMA topology
- production-shaped multi-accelerator workloads
- containerized and bare-metal deployments of the same stack
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.
- ✓Find the first occurrence of "Gloo Connection refused to host 29500 during initial rendezvous" and preserve at least 100 lines before it.
- ✓Identify which rank, node, device, or process emitted the first related warning.
- ✓Compare the failing rank, node, input, or configuration with one known-good control.
- ✓Repeat the same input after the targeted change and require the signature to disappear.
- ✓Resume from latest checkpoint only after the control passes.
Root cause
- Gloo TCP store connection failed (connection refused or DNS resolution failed), ranks cannot reach the rendezvous point.
- The decisive evidence is the first log line that precedes "Gloo Connection refused to host 29500 during initial rendezvous" and differs from a healthy run.
- A nearby failure remains a competing hypothesis until a control separates configuration, capacity, transport, and hardware causes.
The fix and how to prevent it
Searchable error signature
Gloo Connection refused to host 29500 during initial rendezvousUse this text as a lookup key in logs and upstream issue trackers. It is not presented as a captured customer log. Confirm the cause from your own preceding events, versions, configuration and the cited references.
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.
Why the recommended fix works
Verify MASTER_ADDR resolves correctly: getent hosts $MASTER_ADDR. Check firewall: nc -zv $MASTER_ADDR $MASTER_PORT. Ensure rank 0 starts first. For K8s, verify headless service DNS. This changes the condition in the causal diagnosis instead of hiding the outer exception. The repeated control proves ownership before recovery from latest checkpoint.
Code examples
# 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 -- "Gloo Connection refused to host 29500 during initial rendezvous" <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.
Best practices by model family
| Model / Stack | Recommendation | Notes |
|---|---|---|
| First response | Preserve the first failure | Keep the context before "Gloo Connection refused to host 29500 during initial rendezvous" so aggregation does not erase causality. |
| Confirmation | Change one variable | Use a known-good node, rank, input, or configuration as the control. |
| Recovery | Resume from latest checkpoint | Resume only after the literal signature no longer appears in the same control. |
With the fix vs without the fix
| Dimension | With the fix | Without the fix |
|---|---|---|
| Evidence | First preceding error and one controlled comparison | Only the final aggregated exception |
| Fix | Verify MASTER_ADDR resolves correctly: getent hosts $MASTER_ADDR. Check firewall: nc -zv $MASTER_ADDR $MASTER_PORT. Ensure rank 0 starts first. For K8s, verify headless service DNS. | Retrying the unchanged workload |
| Exit criterion | "Gloo Connection refused to host 29500 during initial rendezvous" is absent in the repeated control | The job happened to run once |
Diagnostic note
“Treat "Gloo Connection refused to host 29500 during initial rendezvous" as a search key and an investigation checkpoint, not as proof of every cause associated with the phrase. The high-value evidence is what changed immediately before it and whether the failure follows the workload, node, or configuration.”
Visual fingerprint
literal error captured
|
v
find first preceding failure
|
v
run one known-good control
|
+-- follows workload --> inspect input or configuration
+-- follows node ------> inspect hardware or platform
+-- disappears --------> validate the targeted fixDiagnose 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 extensionRelated failures to investigate next
Frequently asked questions
Questions engineers and on-call staff commonly ask about this failure.
What does "Gloo Connection refused to host 29500 during initial rendezvous" mean?
Is this line always the root cause?
What should I collect before restarting?
What is the fastest confirmation?
How do I prevent it from recurring?
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.