# Lots of Warnings while launching a cluster

**URL:** https://dask.discourse.group/t/lots-of-warnings-while-launching-a-cluster/1694
**Category:** Uncategorized
**Created:** [March 27, 2023, 9:26am UTC](https://dask.discourse.group/t/lots-of-warnings-while-launching-a-cluster/1694 "2023-03-27T09:26:14Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![kvdm.dev](https://avatars.discourse-cdn.com/v4/letter/k/96bed5/32.png) [@kvdm.dev](https://dask.discourse.group/u/kvdm.dev)
#### Post date: [March 27, 2023, 9:26am UTC](https://dask.discourse.group/t/lots-of-warnings-while-launching-a-cluster/1694/1 "2023-03-27T09:26:14Z")

</div>

Is it alright to see so many warnings during a normal launching scenario?  
That’s kind of annoying.

```python
In [7]: from dask.distributed import Client, progress, LocalCluster
   ...:
   ...: cluster = LocalCluster(dashboard_address='127.0.0.1:8787',
   ...: worker_dashboard_address='127.0.0.1:8787',
   ...: n_workers=8,
   ...: threads_per_worker=1,
   ...: memory_limit='400MiB')
   ...: client = Client(cluster)

/home/vol/.local/lib/python3.8/site-packages/distributed/node.py:182: UserWarning: Port 8787 is already in use.
Perhaps you already have a cluster running?
Hosting the HTTP server on port 34375 instead
  warnings.warn(
/home/vol/.local/lib/python3.8/site-packages/distributed/node.py:182: UserWarning: Port 8787 is already in use.
Perhaps you already have a cluster running?
Hosting the HTTP server on port 43001 instead
  warnings.warn(
/home/vol/.local/lib/python3.8/site-packages/distributed/node.py:182: UserWarning: Port 8787 is already in use.
Perhaps you already have a cluster running?
Hosting the HTTP server on port 46245 instead
  warnings.warn(
/home/vol/.local/lib/python3.8/site-packages/distributed/node.py:182: UserWarning: Port 8787 is already in use.
Perhaps you already have a cluster running?
Hosting the HTTP server on port 41197 instead
  warnings.warn(
/home/vol/.local/lib/python3.8/site-packages/distributed/node.py:182: UserWarning: Port 8787 is already in use.
Perhaps you already have a cluster running?
Hosting the HTTP server on port 36131 instead
  warnings.warn(
/home/vol/.local/lib/python3.8/site-packages/distributed/node.py:182: UserWarning: Port 8787 is already in use.
Perhaps you already have a cluster running?
Hosting the HTTP server on port 36221 instead
  warnings.warn(
/home/vol/.local/lib/python3.8/site-packages/distributed/node.py:182: UserWarning: Port 8787 is already in use.
Perhaps you already have a cluster running?
Hosting the HTTP server on port 39607 instead
  warnings.warn(
/home/vol/.local/lib/python3.8/site-packages/distributed/node.py:182: UserWarning: Port 8787 is already in use.
Perhaps you already have a cluster running?
Hosting the HTTP server on port 35521 instead
  warnings.warn(

```

---

<div class="post-metadata">

### Author: ![guillaumeeb](https://yyz1.discourse-cdn.com/flex035/user_avatar/dask.discourse.group/guillaumeeb/32/1613_2.png) [@guillaumeeb](https://dask.discourse.group/u/guillaumeeb)
#### Post date: [March 27, 2023, 5:13pm UTC](https://dask.discourse.group/t/lots-of-warnings-while-launching-a-cluster/1694/2 "2023-03-27T17:13:19Z")

</div>

Hi @kvdm.dev,

It’s normal considering your code: you’re trying to launch 8 local workers with the same port as the scheduler, so 8 warnings.

---

<div class="post-metadata">

### Author: ![kvdm.dev](https://avatars.discourse-cdn.com/v4/letter/k/96bed5/32.png) [@kvdm.dev](https://dask.discourse.group/u/kvdm.dev)
#### Post date: [March 27, 2023, 5:29pm UTC](https://dask.discourse.group/t/lots-of-warnings-while-launching-a-cluster/1694/3 "2023-03-27T17:29:51Z")

</div>

Ummmm, but i launch a cluster, not workers particularly, that’s a conceptual difference.

So how i should run a cluster with multiple workers to avoid warnings?

---

<div class="post-metadata">

### Author: ![kvdm.dev](https://avatars.discourse-cdn.com/v4/letter/k/96bed5/32.png) [@kvdm.dev](https://dask.discourse.group/u/kvdm.dev)
#### Post date: [March 27, 2023, 5:33pm UTC](https://dask.discourse.group/t/lots-of-warnings-while-launching-a-cluster/1694/4 "2023-03-27T17:33:23Z")

</div>

You probably mean this parameter ` worker_dashboard_address='127.0.0.1:8787',`. I added it without understanding what it is for at the very beginning, because by default the addresses assigned to workers are public `0.0.0.0`.

In such the case i should remove the parameter and somehow disable the `0.0.0.0` default worker dashboard address.

---

<div class="post-metadata">

### Author: ![guillaumeeb](https://yyz1.discourse-cdn.com/flex035/user_avatar/dask.discourse.group/guillaumeeb/32/1613_2.png) [@guillaumeeb](https://dask.discourse.group/u/guillaumeeb)
#### Post date: [March 28, 2023, 10:08am UTC](https://dask.discourse.group/t/lots-of-warnings-while-launching-a-cluster/1694/5 "2023-03-28T10:08:20Z")

</div>

> [@kvdm.dev](#):
>
> In such the case i should remove the parameter and somehow disable the `0.0.0.0` default worker dashboard address.

Yes, that’s it. Did you try with `worker_dashboard_address='127.0.0.1:0'` ?

---

<div class="post-metadata">

### Author: ![kvdm.dev](https://avatars.discourse-cdn.com/v4/letter/k/96bed5/32.png) [@kvdm.dev](https://dask.discourse.group/u/kvdm.dev)
#### Post date: [March 28, 2023, 3:49pm UTC](https://dask.discourse.group/t/lots-of-warnings-while-launching-a-cluster/1694/6 "2023-03-28T15:49:28Z")

</div>

It works, thank you. I’ve never seen the zero-port notation .
