Update _FAQ_My Open OnDemand JupyterLab/Interactive App Session is stuck and...
Compare changes
Conflict: This file was modified in the source branch, but removed in the target branch.
Ask someone with write access to resolve it.
+ 12
− 2
@@ -17,7 +17,8 @@ weight = "95"
@@ -17,7 +17,8 @@ weight = "95"
- [I want to talk to a human about my problem. Can I do that?](#i-want-to-talk-to-a-human-about-my-problem-can-i-do-that)
- [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-ip-s-do-i-use-to-allow-connections-to-from-hcc-resources)
- [Why is my job is showing (ReqNodeNotAvail, Reserved for maintenance) before a downtime?](#why-is-my-job-is-showing-reqnodenotavail-reserved-for-maintenance-before-a-downtime)
@@ -241,7 +242,7 @@ if your local network blocks outgoing connections. To allow HCC IP's, add the fo
@@ -241,7 +242,7 @@ if your local network blocks outgoing connections. To allow HCC IP's, add the fo
Jobs submitted before a downtime may pend and show _(ReqNodeNotAvail, Reserved for maintenance)_ for their status.
(Information on upcoming downtimes can be found at [status.hcc.unl.edu](https://status.hcc.unl.edu/).)
Any job which cannot finish before a downtime is scheduled to begin will pend and show this message. For example,
@@ -250,3 +251,12 @@ If you are sure your job can finish in time, you can lower the requested time to
@@ -250,3 +251,12 @@ If you are sure your job can finish in time, you can lower the requested time to
the downtime begins (for example, 4 days if the downtime starts in 6 days). Use this with care however to ensure your
job isn't prematurely terminated. Alternatively, you can simply wait until the downtime is completed. Jobs will
\ No newline at end of file