Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: 'unable to contact kernel' on Jupyter 3.2.x + #6

Closed
brylie opened this issue Jul 4, 2016 · 2 comments
Closed

Error: 'unable to contact kernel' on Jupyter 3.2.x + #6

brylie opened this issue Jul 4, 2016 · 2 comments

Comments

@brylie
Copy link

brylie commented Jul 4, 2016

When running these notebooks on Jupyter 3.2.x or 4.2.x, I get the following error:

Failed to start the kernel

The 'None' kernel is not available. Please pick another suitable kernel instead, or install that kernel.

Note, the Kernel is running when I create a new notebook, so the problem seems to be related to incompatibility between these notebooks and Jupyter.

Environment

localhost

Here is my local Environment:

The version of the notebook server is 4.2.1 and is running on:

Python 3.5.1 |Anaconda 4.1.0 (64-bit)| (default, Jun 15 2016, 15:32:45)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-1)]

Current Kernel Information:

unable to contact kernel

mybinder.org

The version of the notebook server is 3.2.0-8b0eef4 and is running on:

Python 2.7.10 |Anaconda 2.3.0 (64-bit)| (default, May 28 2015, 17:02:03)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-1)]

@brylie brylie changed the title [04 Model Training] iframe not working Error: 'unable to contact kernel' on Jupyter 3.2.x + Jul 4, 2016
@justmarkham
Copy link
Owner

I'm updating the notebooks later this week and will let you know what I find out. Thanks!

@justmarkham
Copy link
Owner

@brylie I just updated the notebooks today. Hopefully that resolves the issue, but please let me know if the issue persists!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants