Hi, I’m running Jupyterhub on an Azure cluster with node autoscaling enabled. When starting a new Notebook, it takes a while 'till the node is spun up. I’ve the the start_timeout to 3600 seconds (even the http_timeout to 3600), yet after 5 minutes, the UI errors out with Spawn failed: Timeout In …

Spawn failed: Timeout even when start_timeout is set to 3600 seconds

sam February 25, 2021, 3:51pm 2

Topic		Replies	Views
Spawn failed: Server at http://some_ip:8888/user/a/ didn't respond in 30 seconds Zero to JupyterHub on Kubernetes jupyterhub	4	357	February 7, 2024
JupyterHub on Kubernetes: Spawn Failed for users with `timeout 3`. Increase pod creation Timeout Zero to JupyterHub on Kubernetes help-wanted	5	1878	May 1, 2023
Spawn failed due to 30 second timeout JupyterHub	4	3821	June 7, 2021
Server never showed up at http://161.32.35.176:8888/user/niranjan/ after 30 seconds. Giving up Zero to JupyterHub on Kubernetes jupyterhub	4	698	February 28, 2024
JupyterHub on Kubernetes with Kubespawner JupyterHub	1	413	September 12, 2021