Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ondemand loses connection with ongoing Jupyter session #5

Open
ndjones opened this issue Aug 20, 2024 · 7 comments
Open

Ondemand loses connection with ongoing Jupyter session #5

ndjones opened this issue Aug 20, 2024 · 7 comments

Comments

@ndjones
Copy link
Member

ndjones commented Aug 20, 2024

After some period of time, ondemand lost its handle on a running jupyter session, reporting:

Jupyter Lab - staging (jupyterlab-t0x4kmix) Undetermined

Your session has entered a bad state. Feel free to contact support for further information.

@chrisdjscott
Copy link
Collaborator

When this happens does the app still show up as running under interactive sessions: https://163-7-144-39.sslip.io/pun/sys/dashboard/batch_connect/sessions ?

@DininduSenanayake DininduSenanayake transferred this issue from nesi/nesi-ood-rstudio-server-app Aug 20, 2024
@ndjones
Copy link
Member Author

ndjones commented Aug 20, 2024

the error above is copied from the session box for the related Jupyter session under interactive sessions. I didn't copy all the text, just the two indications of an issue.

@lbrick
Copy link
Collaborator

lbrick commented Aug 20, 2024

I believe I have recreated the issue.

It looks related to the OIDC token expiration, if I log in and out then click the "restart web server" once or twice the token gets reissued and the card returns to green.

I dont believe this is related to Jupyter as i have a feeling you can also recreate this with any app running

@chrisdjscott
Copy link
Collaborator

did we have this issue on the training environment too and had to adjust some timeout values in keycloak?

@chrisdjscott
Copy link
Collaborator

@lbrick
Copy link
Collaborator

lbrick commented Aug 20, 2024

Unsure if we did have the issue on the training environment

The Keycloak we are now using is controlled/maintained by CNI so will need to discuss with them if we can increase the SSO timeouts for tokens

@lbrick
Copy link
Collaborator

lbrick commented Aug 21, 2024

Yuriy and I have managed to resolve this.

We are investigating a few other options, however this is fixed in the current test environment and is related to OOD => kubernetes configuration more then the OOD application itself

I will leave this issue open for now till Yuriy and I have tried a few other ways.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants