-
Notifications
You must be signed in to change notification settings - Fork 5k
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: Kernel busy (Cell move forward without execution) #3845
Comments
I was helped by the complete removal and clean installation of Anaconda |
|
The problem was not that of hardware, there was something that cannot be resolved. I then change my operating system (I used to do it frequently) from Ubuntu 17.10 to Kali linux (Plasma KDE). Now, it works perfectly fine for me. Thanks for the solution by the way. |
Most likely cause is a failure to properly establish the websocket connection. The root cause of that on Windows can be bad firewalls or AV software. One option is to specify |
The system cannot find the file specified. |
System: 3.6.5 | Anaconda, Inc.| (default, Mar 29 2018, 13:32:41) [MSC v.1900 64 bit (AMD64)] on Windows 10.
Notebook Installation details: Anaconda version 5.2.0 (64 bit).
What are some problem details?
In the notebook, the default kernel ipykernel (at /ipykernel/resources) is showing busy (kernel busy). Python scripts are not running on it, and instead of showing anything the cell moves forward to new cell. The problem remains same whether notebook started from anaconda-navigator or using command prompt (cmd-windows) as
jupyter notebook
showing-Notice that third line showing 0 active kernels.
A screenshot of running jupyter notebook is
.
This problem looks similar to #3612 and #3724.
More details
Output of
jupyter kernelspec list
(It was showing python3 kernel when we tried installing python3 kernel, and it didn't work).Here is the output of
jupyter troubleshoot
:Tried some measures:
It looks like there is a problem in system (i.e. hardware). Is it?
The text was updated successfully, but these errors were encountered: