1. Spawn failed: pod did not start in 300 seconds

Spawn failed: pod did not start in 300 seconds

Home Forums FABRIC General Questions and Discussion Spawn failed: pod did not start in 300 seconds

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #4633
    yoursunny
    Participant

      When I open JupyterHub, after selecting “default” and passing “CI Login”, I often receive this error:

      Server requested
      Spawn failed: pod jhub-prod/jupyter-someone-40example-2ecom did not start in 300 seconds!

      This issue started last week, and it’s occurring more and more frequently.

      Is the Jupyter server running out of resources?

      #4636
      Ilya Baldin
      Participant

        I believe this has been resolved now. We ran into some scaling issues with the Kubernetes cluster hosting the Hub. Thank you for reporting it.

      Viewing 2 posts - 1 through 2 (of 2 total)
      • You must be logged in to reply to this topic.