To stop them, you can expand the twistie icon next to the notebook name and choose 'Stop'. Running notebooks are marked with a lightning bolt in the 'Recent Notebooks' sidebar. Now I am trying to run python kernel but it throws the following error: I 15:54:17.322 NotebookApp KernelRestart.
![python jupyter notebook dead kernal python jupyter notebook dead kernal](https://ipython.org/ipython-doc/3/_images/frontend-kernel.png)
Before installing itorch and ir there was no problem working with ipython.
![python jupyter notebook dead kernal python jupyter notebook dead kernal](https://vscode-westeu.azurewebsites.net/assets/docs/python/jupyter/jupyter-notebook.png)
![python jupyter notebook dead kernal python jupyter notebook dead kernal](http://i.stack.imgur.com/X7vfk.png)
PYTHON JUPYTER NOTEBOOK DEAD KERNAL WINDOWS
Python (187) Ubuntu (81) OpenContrail (79) OpenStack (79) Django (69) Linux (67) Horizon (27) Networking (27) VMware (27) OpenStack Neutron (26) Git (25) OpenStack Heat (24) Puppet (24) OpenvSwitch (22) Keystone (21) OpenStack Dev Tips (19) go (19) golang (19) linux network namespace (19) Libvirt (18) Cloud (17) Horizon Dev Tips (16) Openstack debug (16) Amazon (15) Keystone Dev Tips (15) EC2 (14) PyS60 (14) Machine Learning (13) MySQL (13) CentOS (11) Tempest (10) iptables (10) zeromq (10) ESXi (9) TensorFlow (9) Xen (9) OpenStack Icehouse (8) OpenStack Tempest (8) Pyramid (8) ironic (8) Eucalyptus (7) KVM (7) Openldap (7) Pylons (7) RabbitMQ (7) VIM (7) Vagrant (7) pip (7) qemu (7) Modem (6) Mutt (6) Mutt Email Client (6) qemu-img (6) vEth (6) vEth interfaces (6) Contribution to OpenStack (5) Debian Packaging (5) DevStack (5) Fedora (5) FreeNAS (5) GRE (5) GRE Tunnel (5) OpenStack Packaging (5) OpenStack zeromq (5) Postgresql (5) SQLAlchemy (5) Teamviewer (5) Ubuntu Video Converter (5) opencloudblog (5) tacker (5) unittest (5) vCenter (5) vSphere (5) virtualenv (5) ARP (4) ClearOS (4) OpenDaylight SDN Controller (4) OpenStack Debug Tips (4) OpenStack Glance (4) OpenStack Networking (4) OpenStack Unit Test (4) PowerShell (4) Python Packaging (4) SVN (4) Screen (4) Skype (4) Subversion (4) Ubuntu 14.04 LTS (4) Virtualization (4) Windows (4) opencontrail vnc api (4) python unittest (4) Captcha (3) Cubietruck (3) Exim Mail Server (3) Havana (3) LXC (3) Linux Bridge (3) Linux Containers (3) MooTools (3) Network layer (3) OCR (3) OpenStack CLI (3) Proxy (3) S3 (3) Sublime Text (3) Tesseract (3) Ubuntu 12.04 (3) cloud-init (3) expect (3) haproxy (3) iptables REDIRECT target (3) port forwarding (3) under-cloud (3) virsh (3) ARP Table (2) Apache (2) Boto (2) EasyInstall (2) Ext JS (2) Flask (2) GNS3 (2) Google Chrome (2) IRC (2) JavaScript (2) Jenkins (2) Mobile (2) MongoDB (2) NFS (2) Netbeans (2) OpenStack Ceilometer (2) PDB (2) Python Debugging (2) Python Distutils (2) Python SetupTools (2) Rspec (2) SDN (2) ShellScript (2) Tox (2) VLAN (2) VXLAN (2) WSGI (2) WorkBench (2) apt-key (2) cherry-pick (2) dsetia (2) github (2) ipmitool (2) lsof (2) netconf (2) neutron (2) ovftool (2) python mox (2) quanta (2) run_tests. The best way to keep Jupyter within Data Scientist Workbench healthy is to stop any running notebooks after you're done with them. I am using anaconda2 with itorch and ir kernel.