If you are new to DKRZ and want to access our JupyterHub, please consult the Quick Start page.
If the batch queue is filled with waiting jobs, it might take some time to start the notebook server. There is an internal timelimit specified until which the resources should be ready.
If not the spawner will reject and ask you to start again (maybe with reduced resources specified).
On September 1st, 2020, we deployed a new version of our Jupyterhub server. Check the Changelog for all notable changes.
Furthermore, the new release has been also presented during the DKRZ Tech Talks.
You can switch between classical and lab notebook simply by replacing the /lab in the URL with /tree.
Do the opposite to switch again to jupyterlab.
If you have ? at the end of the url, it needs to be removed before adding /lab.
If you encounter any issue or you have request for new features,
please send us an e-mail to email@example.com.
There are a few points you should be aware of when working with Jupyter Notebooks on the jupyterhub server:
Sessions are persistent. If you close the browser tab without stopping the server before, you can revisit the jupyterhub site and carry on working
JupyterLab: File -> Hub Control Panel -> (preset/advanced) and then stop
Hub Control Panel
classical Jupyter: Control Panel -> (preset/advanced) and then stop
SLURM might cancel your server session if a timeout occurs after 8 hours
By default, stdout and stderr of the SLURM batch job that is spawned by Jupyterhub is written to your HOME directory on the HPC system.
In order to make it simple to locate the log file:
if you use the preset options form: the log file is named jupyterhub_slurmspawner_preset_<id>.log.
if you use the advanced options form: the log file is named jupyterhub_slurmspawner_advanced_<id>.log. You can even change the name of the output log file (Log File Name).
Log File Name