# Port conflict when running several nodes on a Slurm cluster

**URL:** https://discourse.julialang.org/t/port-conflict-when-running-several-nodes-on-a-slurm-cluster/85024
**Category:** Performance
**Tags:** question
**Created:** [July 30, 2022, 9:49am UTC](https://discourse.julialang.org/t/port-conflict-when-running-several-nodes-on-a-slurm-cluster/85024 "2022-07-30T09:49:05Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![DrChainsaw](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/drchainsaw/32/8497_2.png) [@DrChainsaw](https://discourse.julialang.org/u/DrChainsaw)
#### Post date: [July 30, 2022, 10:46am UTC](https://discourse.julialang.org/t/port-conflict-when-running-several-nodes-on-a-slurm-cluster/85024/2 "2022-07-30T10:46:03Z")

</div>

I have had the same issue on an LSF cluster. I think it should only happen when the same port is used with the same ip, something which can happen when a single machine has many slots.

Here is a post of how I worked around the above issue on LSF: [How to configure which port workers listen - #6 by DrChainsaw](https://discourse.julialang.org/t/how-to-configure-which-port-workers-listen/46759/6)

Dont know if slurm does things differently so that other constraints come to play.

---

_[View the full topic](https://discourse.julialang.org/t/port-conflict-when-running-several-nodes-on-a-slurm-cluster/85024)._