Kernel dead when running notebook in a server
See original GitHub issueI have a Jupyter notebook running on a server on a specific port and IP. The notebook runs fine locally however, the kernel dies when I run the notebook from another computer. The line that crashes is vp = Plotter(title='My title goes here')
.
I am running the notebook in the server with jupyter notebook --no-browser --port=8080 --ip 10.xxx.xx.xx
. Access is done via http://10.xxx.xx.xx:8080/?token=xxx
. Could you guys think of something else I can try? Thanks.
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
python 3.x - Jupyter notebook - Dead Kernel - Stack Overflow
The kernel has died, and the automatic restart has failed. It is possible the kernel cannot be restarted. If you are not able...
Read more >dead kernel and restart repeatedly occurred in a notebook on ...
I have a notebook with virtualenv environment running both remotely and locally. For the remote run, I forward the remote port to a...
Read more >How to Fix Kernel Error in Jupyter Notebook
The Jupyter Notebook most of us work with runs on Anaconda. So to get to the back-end, open the Anaconda command prompt. Since...
Read more >Newbie question, I keep getting a dead kernel warning when ...
Hi, I'm trying to learn python, and can't get notebook to run pandas, from my research its probably a python conflict but I...
Read more >How to fix Kernel Error or broken Python in Jupyter Notebook
TL;DW BELOW! If you delete or upgrade your python version, you might get a Kernel Error when trying to use Jupyter Notebooks !...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
LOL …no, that’s because of a vtk call trying to get the physical size of your screen (which in your case does not exist since it on a server)…
It will be fixed in the next release, thanks for spotting the problem! M.
Are you saying my 13inch screen isn’t too big for the default screensize? 😃