[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: jupyter notebook immediately crashes with dead kernel



D. R. Evans wrote on 11/06/2018 07:56 AM:
> D. R. Evans wrote on 11/05/2018 06:14 PM:
>> vipul kumar wrote on 11/05/2018 05:35 PM:
>>> Run Jupyter-notebook from terminal. Send log report which you'll get on terminal while running jupyter-notebook.
>>>
>>
> 
>>
>> [HN:~] jupyter-notebook
>> [I 18:11:04.210 NotebookApp] Serving notebooks from local directory: /home/n7dr
>> [I 18:11:04.211 NotebookApp] 0 active kernels
>> [I 18:11:04.211 NotebookApp] The Jupyter Notebook is running at:
>> http://localhost:8888/
>> [I 18:11:04.211 NotebookApp] Use Control-C to stop this server and shut down
>> all kernels (twice to skip confirmation).
>>
>> ----
> 
> I see additional messages when I actually try to create the notebook (sorry; I
> wasn't looking for those yesterday):
> 
> ----
> 
> HN:~] jupyter-notebook
> [I 07:37:19.123 NotebookApp] Serving notebooks from local directory: /home/n7dr
> [I 07:37:19.124 NotebookApp] 0 active kernels
> [I 07:37:19.124 NotebookApp] The Jupyter Notebook is running at:
> http://localhost:8888/
> [I 07:37:19.124 NotebookApp] Use Control-C to stop this server and shut down
> all kernels (twice to skip confirmation).
> [I 07:37:29.629 NotebookApp] Creating new notebook in
> [I 07:37:32.575 NotebookApp] Kernel started: 00f6d461-87f1-410e-9963-5f5db91602f3
> /usr/bin/python: No module named ipykernel_launcher
> [I 07:37:35.561 NotebookApp] KernelRestarter: restarting kernel (1/5)
> /usr/bin/python: No module named ipykernel_launcher
> [I 07:37:38.571 NotebookApp] KernelRestarter: restarting kernel (2/5)
> /usr/bin/python: No module named ipykernel_launcher
> [I 07:37:41.582 NotebookApp] KernelRestarter: restarting kernel (3/5)
> /usr/bin/python: No module named ipykernel_launcher
> [W 07:37:42.678 NotebookApp] Timeout waiting for kernel_info reply from
> 00f6d461-87f1-410e-9963-5f5db91602f3
> [I 07:37:44.592 NotebookApp] KernelRestarter: restarting kernel (4/5)
> WARNING:root:kernel 00f6d461-87f1-410e-9963-5f5db91602f3 restarted
> /usr/bin/python: No module named ipykernel_launcher
> [W 07:37:47.604 NotebookApp] KernelRestarter: restart failed
> [W 07:37:47.605 NotebookApp] Kernel 00f6d461-87f1-410e-9963-5f5db91602f3 died,
> removing from map.
> ERROR:root:kernel 00f6d461-87f1-410e-9963-5f5db91602f3 restarted failed!
> [W 07:37:47.654 NotebookApp] Kernel deleted before session
> [W 07:37:47.656 NotebookApp] 410 DELETE
> /api/sessions/56ef952c-800c-448f-baf0-857081b87abc (::1) 3.46ms
> referer=http://localhost:8888/notebooks/Untitled4.ipynb?kernel_name=python3
> 
> ----
> 
> The strange thing here is:
>   /usr/bin/python: No module named ipykernel_launcher
> 
> Why is it running /usr/bin/python, which is a link to python2??
> 
> ----
> 
> HN:~] ls -al /usr/bin/python
> lrwxrwxrwx 1 root root 9 Jan 24  2017 /usr/bin/python -> python2.7
> 
> ----
> 
> I would have thought that, since the package installed the ipython3 kernel for
> jupyter, and when I try to create a notebook, it's python3 that is in the
> "New" drop-down menu on the jupyter page, then it should be executing
> /usr/bin/python3, not /usr/bin/python.
> 
> Is this perhaps an error in the packaging?

This is now bug 913110:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913110

The bug report includes a simple fix.

  Doc

-- 
Web:  http://enginehousebooks.com/drevans

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: