Spawn Failed Message: Harmless Error but Could Turn Off Novice Users

Upon recommendation from @yuvipanda , I am submitting an issue here.

I administer a few JupyterHub servers. I have noticed on many occasions that when I access the JupyterHub I will get a

Spawn failed: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))

as can be seen here: https://photos.app.goo.gl/egp1XmwUCiNo3TdGA

Accompanying this error is this stack trace.

The workaround is easy. Simply go the the Home menu and click ‘Start My Server’. The problem, however, could be disconcerting for new users. Is there anyway to avoid this spawn error?

I am running:

• jupyterhub version 0.9.4
• jupyterhub-singleuser version 1.0.0.

with Zero to JupyterHub. The docker container that gets spawned inherits from jupyter/minimal-notebook and it is rather large (~2GB).

Running on NSF Jetstream (OpenStack) Cloud at TACC

Edit: Here is the Zero to JupyterHub config (roughly).

[julienchastang]

Switching data centers (Jetstream TACC --> IU) solved this problem for me so I am going to close this issue for now.

[julienchastang]

Possibly related: https://github.com/dask/distributed/pull/2485