make remote_jupyter_manager.sh work on mistral.dkrz.de
On mistral the remote jupyter manager does only partially work. You can start a server using the undocumented third option "0.0.0.0":
remote_jupyter_manager.sh firstname.lastname@example.org start 0.0.0.0
but a wrong URL is returned
Copy/paste this URL into your browser when you connect for the first time, to login with a token: http://(mlogin104 or 127.0.0.1):8888/?token=4f8e866a51e0b2d124c9d023b61b6266248548f01f13a41b
if you correct the URL manually and copy it into the Chrome window which is opened by the script, you are able to use the jupyterlab instance that is fired up on one of mistrals login nodes (
mlogin1xx). The script is not able to find a running jupyterlab instance on one of the login nodes at the moment, and logging in directly into one of the login nodes is not possible (or I don't know how to do it, tried mlogin1xx.dkrz.de and mlogin1xx.hpc.dkrz.de).
The problem described here may apply to other computing centres as well where you cannot login into a specific login from remote.