Hub Trouble-Shooting and Diagnostics

So far, I had 2 serious problems while using the hub (one of them the Tornado 6 one) – and the logs are quite often unhelpful even on DEBUG level. As soon as the notebook server / kernel is involved, you somehow stare into a black hole. Am I missing something, like a “write a log” setting for the notebook part?

What I assembled so far is here. And while manually starting a notebook server sometimes helps, I’d prefer something less disruptive.

could you clarify what kind of jupyterhub setup you’re using? Are you deploying your own custom jupyterhub? Or following one of the jupyterhub distributions like or ?

Quite unsurprising, I’m using 1and1/debianized-jupyterhub. Meaning this, pretty much unchanged.

1 Like