-[My submitted job takes long time waiting in the queue or it is not running?](#my-submitted-job-takes-long-time-waiting-in-the-queue-or-it-is-not-running)
-[What IP's do I use to allow connections to/from HCC resources?](#what-ips-do-i-use-to-allow-connections-tofrom-hcc-resources)
-[Why my job is showing (ReqNodeNotAvail, Reserved for maintenance) before a downtime?](#why-my-job-is-showing-reqnodenotavail-reserved-for-maintenance-before-a-downtime)
-[Why my Open OnDemand JupyterLab/Interactive App Session is stuck and is not starting?](#why-my-open-ondemand-jupyterlabinteractive-app-session-is-stuck-and-is-not-starting)
-[Why my Open OnDemand JupyterLab or Interactive App Session is stuck and is not starting?](#why-my-open-ondemand-jupyterlab-or-interactive-app-session-is-stuck-and-is-not-starting)
-[My directories are not full, but my Open OnDemand JupyterLab Session is still not starting. What else should I try?](#my-directories-are-not-full-but-my-open-ondemand-jupyterlab-session-is-still-not-starting-what-else-should-i-try)
-[Why my Open OnDemand RStudio Session is crashing?](#why-my-open-ondemand-rstudio-session-is-crashing)
-[Why I can not access files under shared Attic/Swan Globus Collection?](#why-i-can-not-access-files-under-shared-atticswan-globus-collection)
...
...
@@ -264,7 +264,7 @@ the downtime begins (for example, 4 days if the downtime starts in 6 days). Use
job isn't prematurely terminated. Alternatively, you can simply wait until the downtime is completed. Jobs will
automatically resume normally afterwards; no special action is required.
#### Why my Open OnDemand JupyterLab/Interactive App Session is stuck and is not starting?
#### Why my Open OnDemand JupyterLab or Interactive App Session is stuck and is not starting?
The most common reason for this is full `$HOME` directory. You can check the size of the directories in `$HOME` by running `ncdu` on the terminal from the `$HOME` directory.
Then, please remove any unnecessary data; move data to [$COMMON or $WORK]({{<relref"../handling_data/">}}); or [back up important data elsewhere]({{<relref"../handling_data/data_storage/preventing_file_loss.md">}}).
...
...
@@ -272,8 +272,11 @@ If the majority of storage space in `$HOME` is utilized by `conda` environments,
#### My directories are not full, but my Open OnDemand JupyterLab Session is still not starting. What else should I try?
If the inode and storage quotas of the `$HOME` and `$WORK` directories on Swan are not exceeded, and your Open OnDemand JupyterLab Session is still not starting, there are two additional things you can check:
1) If a custom conda environment is not used, when installing packages with `pip` locally, these libraries are installed in `$HOME/.local`. When using other modules or applications that are based on Python/conda (e.g., Open OnDemand JupyterLab), these local installs can cause conflicts and errors. In this case, please rename the `$HOME/.local` directory (e.g., `mv $HOME/.local $HOME/.local_old`).
2) Please make sure that you don't set variables such as `PYTHONPATH` in your `$HOME/.bashrc` file. If you have this variable set in the `$HOME/.bashrc` file, please comment out that line and run `source $HOME/.bashrc` to apply the changes.
- If a custom conda environment is not used, when installing packages with `pip` locally, these libraries are installed in `$HOME/.local`. When using other modules or applications that are based on Python/conda (e.g., Open OnDemand JupyterLab), these local installs can cause conflicts and errors. In this case, please rename the `$HOME/.local` directory (e.g., `mv $HOME/.local $HOME/.local_old`).
- Please make sure that you don't set variables such as `PYTHONPATH` in your `$HOME/.bashrc` file. If you have this variable set in the `$HOME/.bashrc` file, please comment out that line and run `source $HOME/.bashrc` to apply the changes.
Whether you have renamed the `$HOME/.local` directory and/or modified the file `$HOME/.bashrc`, please cancel and restart your JupyterLab Session.
#### Why my Open OnDemand RStudio Session is crashing?
