Loading jupyter_on_rhea.md +9 −9 Original line number Diff line number Diff line Loading @@ -27,7 +27,7 @@ the notebook server must be tunneled out of the compute nodes. The [jupyter-on-rhea.pbs](jupyter-on-rhea.pbs) batch script in this repo launches a Jupyter server on a single batch node and sets up a script to create the necessary SSH tunnel to access it. In order to work, you will need to have Jupyter installed somewhere in your PYTHONPATH. This can either be in Jupyter installed somewhere in your `$PYTHONPATH`. This can either be in `/ccs/proj/...` or, on Rhea, simply in your user site-packages directory. It is recommended that you use a virtualenv or alternate Python install to manage your Python environment for this app. Loading @@ -40,8 +40,8 @@ $ . $MYVENVPATH/bin/activate (myvenv)$ pip install --user jupyter ``` The rest these instructions assume you will have the installed Jupyter package in your PATH either through an activated virtualenv or other scheme. The rest of these instructions assume you will have the installed Jupyter package in your `$PATH` either through an activated virtualenv or other scheme. ## Secure the Server Loading @@ -61,8 +61,8 @@ Verify password: c.NotebookApp.password = 'sha1:123:some:456:secret:789:password:012:hash:3456789abcd' ``` add the output hashed password line to the profile config file (typically `$HOME/.jupyter/jupyter_notebook_config.py`) add the hashed/salted password line that is output to your Jupyter profile config file (typically `$HOME/.jupyter/jupyter_notebook_config.py`) Now that access is password protected, you must **encrypt all communication traffic**, otherwise someone can simply intercept the unencrypted stream and Loading Loading @@ -140,8 +140,8 @@ allocation. Any of the configuration details should be tuned to your needs. Specifically, the ports may need to be different for your case. You may want to change 'c.NotebookManager.notebook_dir' to use a different path then the default so as to keep your toplevel $HOME directory tidy. change `c.NotebookManager.notebook_dir` to use a different path than the default so as to keep your toplevel `$HOME` directory tidy. ## Troubleshooting Loading Loading @@ -169,8 +169,8 @@ include: 1. **Cannot start a new server jobs even though no server job is running.** * New servers won't start while a `$HOME/.jupyter_connect` script exists. This script is used as a lockfile, but is sometimes not removed when the last server job exits. Verify that no server job is running using `showq -u $USER` and if none is running, simply delete `$HOME/.jupyter_connect` to last server job exits. Verify that no server job is running using `showq -u $USER` and if none is running, simply delete `$HOME/.jupyter_connect` to allow a new server job to start. This is a symptom of the crude method of creating and clearing lockfiles used by this technique and should be improved. Loading Loading
jupyter_on_rhea.md +9 −9 Original line number Diff line number Diff line Loading @@ -27,7 +27,7 @@ the notebook server must be tunneled out of the compute nodes. The [jupyter-on-rhea.pbs](jupyter-on-rhea.pbs) batch script in this repo launches a Jupyter server on a single batch node and sets up a script to create the necessary SSH tunnel to access it. In order to work, you will need to have Jupyter installed somewhere in your PYTHONPATH. This can either be in Jupyter installed somewhere in your `$PYTHONPATH`. This can either be in `/ccs/proj/...` or, on Rhea, simply in your user site-packages directory. It is recommended that you use a virtualenv or alternate Python install to manage your Python environment for this app. Loading @@ -40,8 +40,8 @@ $ . $MYVENVPATH/bin/activate (myvenv)$ pip install --user jupyter ``` The rest these instructions assume you will have the installed Jupyter package in your PATH either through an activated virtualenv or other scheme. The rest of these instructions assume you will have the installed Jupyter package in your `$PATH` either through an activated virtualenv or other scheme. ## Secure the Server Loading @@ -61,8 +61,8 @@ Verify password: c.NotebookApp.password = 'sha1:123:some:456:secret:789:password:012:hash:3456789abcd' ``` add the output hashed password line to the profile config file (typically `$HOME/.jupyter/jupyter_notebook_config.py`) add the hashed/salted password line that is output to your Jupyter profile config file (typically `$HOME/.jupyter/jupyter_notebook_config.py`) Now that access is password protected, you must **encrypt all communication traffic**, otherwise someone can simply intercept the unencrypted stream and Loading Loading @@ -140,8 +140,8 @@ allocation. Any of the configuration details should be tuned to your needs. Specifically, the ports may need to be different for your case. You may want to change 'c.NotebookManager.notebook_dir' to use a different path then the default so as to keep your toplevel $HOME directory tidy. change `c.NotebookManager.notebook_dir` to use a different path than the default so as to keep your toplevel `$HOME` directory tidy. ## Troubleshooting Loading Loading @@ -169,8 +169,8 @@ include: 1. **Cannot start a new server jobs even though no server job is running.** * New servers won't start while a `$HOME/.jupyter_connect` script exists. This script is used as a lockfile, but is sometimes not removed when the last server job exits. Verify that no server job is running using `showq -u $USER` and if none is running, simply delete `$HOME/.jupyter_connect` to last server job exits. Verify that no server job is running using `showq -u $USER` and if none is running, simply delete `$HOME/.jupyter_connect` to allow a new server job to start. This is a symptom of the crude method of creating and clearing lockfiles used by this technique and should be improved. Loading