- This topic has 7 replies, 4 voices, and was last updated 3 years ago by
.
-
Posts
-
I’m getting the following when trying to open a jupyterhub notebook. How do I work around this?
Spawn failed: pod/jupyter-ssthapa-40uchicago-2eedu did not start in 300 seconds!
Event log
Server requested
2021-11-10 21:13:33+00:00 [Warning] pod has unbound immediate PersistentVolumeClaims (repeated 2 times)
Spawn failed: pod/jupyter-ssthapa-40uchicago-2eedu did not start in 300 seconds!I have a similar problem:
Spawn failed: Timeout
Event log
Server requested
2021-11-10 21:24:24+00:00 [Warning] pod has unbound immediate PersistentVolumeClaims (repeated 2 times)
Spawn failed: TimeoutAny thoughts?
This may or may not be an issue. The utility function in the notebook has a timeout that can be chosen by the user. There is a sane default but larger slices may exceed that timeout.
If you are hitting that timeout and later the VMs become accessible, you might want to increase the timeout for your use case.
I’m still seeing the timeout unfortunately. It looks like the jupyterhub pod is landing on a node that’s out of space or something.
Your server is starting up.
You will be redirected automatically when it’s ready for you.
100% Complete
Spawn failed: Timeout
Event log
Server requested
2021-11-11 21:05:39+00:00 [Warning] pod has unbound immediate PersistentVolumeClaims (repeated 2 times)
Spawn failed: Timeout
- You must be logged in to reply to this topic.