search

det-lab / jupyterhub-deploy-kubernetes-jetstream

CDMS JupyterHub deployment on XSEDE Jetstream
0 stars 1 forks source link

Instance takes a long time to spin up (or does not spin up) #16

Closed pibion closed 4 years ago

pibion commented 4 years ago

I'm trying to access a JupyterHub instance, but it seems to be taking a very long time to spin up.

Is anyone else having this issue? @zonca @ziqinghong

zonca commented 4 years ago

I know they were updating some of the services on Jetstream today, I'll check the deployment later today and then get back to you.

zonca commented 4 years ago

same issue I encountered in #10, let's continue debugging in that issue, I'll close this one.

pibion commented 4 years ago

@zonca when trying to access https://supercdms.jetstream-cloud.org I'm able to authenticate but the server takes a long time to spin up.

Actually, it hasn't spun up yet so I'm not sure if it's able to. I'll report back when I get an error or it completes.

zonca commented 4 years ago

I see your pod running, you cannot access it?

zonca commented 4 years ago

I found the problem, while developing I had setup that the docker image of the container is pulled everytime. Now back to normal, so it should start a lot quicker

pibion commented 4 years ago

Yes, this spawned quickly for me!

pibion commented 4 years ago

Hi @zonca , one of our users is having trouble spinning up an instance. I've attached her message and images.

I've run into some difficulties with accessing JupyterHub/Jetstream. I have tried relaunching the server several times-- just in case it may have been my internet connection being slow. I am currently receiving the same messages each time I refresh (Attached below). I'm not sure if it has to do with the recent update or something on my side.

JupyterHubServerStart2 JupyterHubServerStart1

zonca commented 4 years ago

yes, I see all the persistent volumes have been deleted. Now I would like to understand why that happened. After I redeployed on Thursday around noon Pacific (https://github.com/det-lab/jupyterhub-deploy-kubernetes-jetstream/issues/28#issuecomment-650011693) has anyone tested JupyterHub, did they see their old data?

zonca commented 4 years ago

@pibion, anyway I reset the volumes, now it should work fine for all users. Can they try again?

pibion commented 4 years ago

@jpanmany466, could you try to access JupyterHub again and let us know if you see your existing files?

zonca commented 4 years ago

@pibion next time please open a new issue to report anything not working, even if symptoms are similar, most of the time errors are unrelated. That helps me keep track of things. Thanks.

Existing files are definitely gone, I'm sorry about that, something went wrong either in my redeployment or something happened afterwards. I'll be sure I ask someone to test just after I redeploy next time.

pibion commented 4 years ago

@zonca re issues: sounds good, will do. I'll contact the student and see if they need any help setting up again.

zonca commented 4 years ago

I think this is fixed, if not please open another issue