7. JupyterHub: errors and troubleshooting¶
7.1. Common issues¶
7.1.1. After submitting Spawner options I get returned to the Spawner options page after a minute or two¶
The cluster is not able to start your JupyterHub session at this time because:
the cluster is currently doesn’t have the capacity to start your JupyterHub job on demand at this time or
you have requested an incompatible set of resources from the Spawner options form or
the job scheduler allocates you resources on cluster nodes but the Jupyter server software cannot start for some reason.
To determine if the third of these possibilities is the case
check the most recent
jupyterhub.oXXXXXX log file in your home directory for error messages.
7.3. Less common issues¶
7.3.1. I get a ‘503’ error after logging in to JupyterHub¶
If you modify the
PYTHON_PATH variable in your
.bashrc file your Jupyter server may not start correctly.
The solution to this is to remove these lines from your
Also,f you have previously tried installing and running Jupyter yourself
(i.e. not using this JupyterHub interface) then you may get 503 errors when
connecting to JupyterHub due to the old .jupyter profile in your home
directory; if you then
find a Jupyter log file in your home directory containing
WRONG_VERSION_NUMBER then try deleting (or renaming) the
directory in your home directory.