Forums

Any new Jupyter Notebooks that I create can't connect to their kernel.

What's strange is that other existing notebooks in the same directory can connect to their kernel. I would expect this sort of issue to affect all notebooks, not just new ones.

That's odd. If you go to the "Consoles" tab and view your processes, do you see a large number of running jupyter processes?

It looks like there are thirteen IPython kernels running right now even though I don't think that I have any notebooks open anymore. Killing the kernels only seems to cause them to restart.

I tried killing the /usr/local/bin/python3.4 /usr/local/bin/jupyterhub-singleuser process and that seems to have cleared everything up.

Thanks giles!

Hmm, interesting. Are you creating subprocesses in your notebooks at all?

Not intentionally. I'm only using modules like pandas and json and sqlite3.

Hmm, OK. I wouldn't expect those to start subprocesses. The problem definitely sounds like your new notebook kernels weren't starting because you were hitting our process limit. But that limit is pretty high -- over 100.

Anyway, I guess things are working again now -- but if the same thing happens again, please do let us know.