Closed twrobinson closed 4 years ago
Thanks for the report. Could you try the latest dask-jobqueue release namely 0.7.1 to see whether that fixes the issue?
Hi, unfortunately I see no difference with 0.7.1.
Full pip list is now:
aiohttp (3.5.4)
alembic (1.0.11)
appdirs (1.4.4)
asn1crypto (0.24.0)
async-generator (1.10)
async-timeout (3.0.1)
attrs (19.1.0)
backcall (0.1.0)
bash-kernel (0.7.2)
batchspawner (0.9.0.dev0)
black (19.10b0)
bleach (3.1.0)
bokeh (1.3.4)
bqplot (0.11.6)
certifi (2019.6.16)
certipy (0.1.3)
cffi (1.12.3)
chardet (3.0.4)
click (6.6)
cloudpickle (1.3.0)
colorcet (2.0.2)
contextvars (2.4)
cryptography (2.7)
cycler (0.10.0)
Cython (0.28.4)
dask (2.18.1)
dask-jobqueue (0.7.1)
dask-labextension (1.0.3)
decorator (4.4.0)
defusedxml (0.6.0)
distributed (2.18.0)
docrep (0.2.7)
entrypoints (0.3)
fsspec (0.4.1)
funcsigs (1.0.2)
graphviz (0.12)
HeapDict (1.0.0)
idna (2.8)
idna-ssl (1.1.0)
immutables (0.14)
ipydatawidgets (4.0.1)
ipykernel (5.1.1)
ipympl (0.3.3)
ipyparaview (0.1.0a0)
ipython (7.7.0)
ipython-genutils (0.2.0)
ipywidgets (7.5.1)
itk-core (5.0.1)
itk-filtering (5.0.1)
itk-meshtopolydata (0.5.1)
itk-numerics (5.0.1)
itkwidgets (0.25.0)
jedi (0.14.1)
Jinja2 (2.10.1)
json5 (0.8.5)
jsonschema (3.0.1)
jupyter-client (5.3.1)
jupyter-core (4.5.0)
jupyter-server-proxy (1.1.0)
jupyterhub (1.0.0)
jupyterlab (1.1.1)
jupyterlab-code-formatter (1.1.0)
jupyterlab-nvdashboard (0.2.1)
jupyterlab-server (1.0.0)
kiwisolver (1.1.0)
locket (0.2.0)
Mako (1.0.14)
MarkupSafe (1.1.1)
matplotlib (2.2.2)
mistune (0.8.4)
more-itertools (4.1.0)
mpi4py (2.0.0)
msgpack (0.6.1)
multidict (4.5.2)
nbconvert (5.5.0)
nbformat (4.4.0)
nbresuse (0.3.2)
nose (1.3.7)
notebook (6.0.0)
numpy (1.15.1)
oauthlib (3.0.2)
packaging (19.1)
pamela (1.0.0)
pandas (0.23.3)
pandocfilters (1.4.2)
param (1.9.2)
parso (0.5.1)
partd (1.0.0)
pathspec (0.8.0)
pexpect (4.7.0)
pickleshare (0.7.5)
Pillow (6.1.0)
pip (9.0.3)
plotly (4.0.0)
pluggy (0.6.0)
prometheus-client (0.7.1)
prompt-toolkit (2.0.9)
psutil (5.6.3)
ptyprocess (0.6.0)
py (1.5.3)
pycparser (2.19)
pyct (0.4.6)
Pygments (2.4.0)
pynvml (8.0.4)
pyOpenSSL (19.0.0)
pyparsing (2.4.2)
pyrsistent (0.15.4)
pytest (3.5.1)
python-dateutil (2.8.0)
python-editor (1.0.4)
pytz (2019.3)
PyYAML (5.1.2)
pyzmq (18.0.2)
regex (2020.6.8)
requests (2.22.0)
retrying (1.3.3)
scipy (1.1.0)
Send2Trash (1.5.0)
setuptools (39.0.1)
simpervisor (0.3)
six (1.11.0)
sortedcontainers (2.1.0)
SQLAlchemy (1.3.6)
tblib (1.6.0)
terminado (0.8.2)
testpath (0.4.2)
toml (0.10.1)
toolz (0.9.0)
tornado (6.0.3)
traitlets (4.3.2)
traittypes (0.2.1)
typed-ast (1.4.1)
typing-extensions (3.7.4)
urllib3 (1.25.3)
wcwidth (0.1.7)
webencodings (0.5.1)
widgetsnbextension (3.5.1)
yarl (1.3.0)
zict (1.0.0)
zstandard (0.13.0)
Thanks for the report our doc was misleading and I improved it see https://github.com/dask/dask-jobqueue/blob/master/docs/source/interactive.rst#configuration.
The yaml configuration file should be something like this:
distributed:
dashboard:
link: "/proxy/{port}/status"
Closing this one, please reopen if that doesn't fix your problem.
Hi,
I am using dask-jobqueue and the dask-labextension through JupyterHub.
After starting a SLURM cluster with jobqueue,
client
orcluster.dashboard_link
printhttp://<ip>:8787/status
. However, as I am through JupyterHub this URL does not work, of course.If I paste
https://<url-of-server>/proxy/8787/status
into the dask labextension search bar, the dashbboard comes up and is functioning correctly.According to the docs:
"you may want to update the dashboard link that is displayed in the notebook, shown from Cluster and Client objects. In order to do this, edit dask config file, either ~/.config/dask/jobqueue.yaml or ~/.config/dask/distributed.yaml, and add the following:"
However, when I try adding anything to either jobqueue.yaml or distributed.yaml, such as:
it seems this is completely ignored. The
cluster.dashboard_link
stays ashttp://<ip>:8787/status
.Do I need to upgrade any of my components, or have I misunderstood how to change the dashboard link displayed?
Many thanks!
Environment: