Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Dashboard not activated after starting dask distributed cluster.

See original GitHub issue

What happened:

The dashboard is not active and remains grey even if the client started normaly.

What you expected to happen:

Minimal Complete Verifiable Example:

from dask.distributed import Client
client = Client()

Anything else we need to know?:

Environment:

Dask version: 2.22.0
Python version: 3.6.10
Jupyterhub: 1.1.0
Install method: conda -c conda-forge

Config:

distributed.yaml

#   ###################
#   # Bokeh dashboard #
#   ###################

   dashboard:
     link: "/user/{JUPYTERHUB_USER}/proxy/{port}/status"
#     export-tool: False

Issue Analytics

State:
Created 3 years ago
Comments:15 (5 by maintainers)

Top GitHub Comments

1reaction

statiksofcommented, Aug 13, 2020

@jacobtomlinson @ian-r-rose my bad, the url of the notebook changed so the dashboard url was not correct. Everything works fine now with all latest versions.

0reactions

jacobtomlinsoncommented, Aug 11, 2020

@devsentient how did you deploy your cluster? It sounds like some config is missing.

@statiksof the config documentation lists the locations where config is stored. I would check those places for errant config.

Top Results From Across the Web

Diagnostics (distributed) - Dask documentation

An interactive dashboard containing many plots and tables with live information. A progress bar suitable for interactive use in consoles or notebooks. Dashboard...

Dask dashboard not starting when starting scheduler with api

Firstly, even when starting the scheduler within a python process, you may wish to consider using LocalCluster : cluster = dask.distributed.

Automatically connect to new dashboard #26 - GitHub

It looks like this is a problem within the dask/distributed library. The Cluster.dashboard_link property gets the host address of the scheduler, ...

Can't connect to local cluster - times out - Dask Forum

New to Dask distributed. I've created a local cluster (default settings) and confirmed that it's running by checking the dashboard. But when I...

Troubleshooting and Optimizing Dask Resources | Saturn Cloud

Dask Cluster Settings · Increase the Worker Size · Add More Workers · Increase the Scheduler Size · Number of Workers Processes/Threads ·...