Closed michzimny closed 5 years ago
The same happens for the current version of SWAN, for instance when it fails to spawn a kernel.
What do you mean by "when it fails to spawn a kernel"? When I tried to start a session, I was unable and then got blocked. Manual actions are necessary (restart jupyterhub, inside the jupyterhub container). But hopefully this is fixed in the update I want to push this week.
What do you mean by "when it fails to spawn a kernel"?
I mean when it fails to spawn the jupyter-user* container. Regarding the spawn fail, I will report it separately soon.
This issue should be fixed with the update I sent you today.
Other situation, when I see these errors, also in the latest version, is when one tries to launch jupyter to quickly after deployment of a new version. Then, the swanuser image is not yet fully downloaded, so it fails to start before the timeout of 30 secs.
That is true, but giving some waiting time before opening the gates to the public should be enough to solve it. I'm closing this issue but re-open it if you think these problems are not solved.
At swan.test.up2university.eu, after the new version of SWAN had been deployed, 1-2 weeks ago, I experienced SWAN being unable to start a session. I cannot reproduce it, so it's not an issue right now. But I saw then the following error message:
The "here" links led to CERN instances, e.g. https://cernbox.cern.ch/
They should rather point at the paired CERNBox instance at PSNC (cernbox.test.up2u...).