notebook: Kernel error
I fond that every time I change the name of my pc, there was a Kernel error. How can I deal with it? `The error is:
Traceback (most recent call last): File “D:\Applications\Scoop\apps\anaconda3\2019.10\lib\site‑packages\spyder\plugins\ipythonconsole.py”, line 1572, in create_kernel_manager_and_kernel_client kernel_manager.start_kernel(stderr=stderr_handle) File “D:\Applications\Scoop\apps\anaconda3\2019.10\lib\site‑packages\jupyter_client\manager.py”, line 240, in start_kernel self.write_connection_file() File “D:\Applications\Scoop\apps\anaconda3\2019.10\lib\site‑packages\jupyter_client\connect.py”, line 547, in write_connection_file kernel_name=self.kernel_name File “D:\Applications\Scoop\apps\anaconda3\2019.10\lib\site‑packages\jupyter_client\connect.py”, line 212, in write_connection_file with secure_write(fname) as f: File “D:\Applications\Scoop\apps\anaconda3\2019.10\lib\contextlib.py”, line 112, in enter return next(self.gen) File “D:\Applications\Scoop\apps\anaconda3\2019.10\lib\site‑packages\jupyter_client\connect.py”, line 102, in secure_write with os.fdopen(os.open(fname, open_flag, 0o600), mode) as f: PermissionError: [Errno 13] Permission denied: ‘C:\Users\blank\AppData\Roaming\jupyter\runtime\kernel�dd8fe4.json’` I reset my pc, and there was no problem when I don’t change the name of the PC.
About this issue
- Original URL
- State: open
- Created 5 years ago
- Comments: 25 (12 by maintainers)
Sorry I have finished my university homework last days. My os is windows 10 1903 And I use the scoop to install it then there was the error. So I uninstall it by the scoop and run Anaconda3 installer as Administrator. Everything ok.
Ok - no rush - that fact is consistent with what I’m seeing in the couple images I have pulled.
I wonder if this has something to do with you using a linux-based image on a Windows file-system. The changes @MSeal made that are coming into play now have specific changes for both Windows and Linux and I wonder if this combination of usage is presenting problems.
Once you go back to using jupyter_client 5.3.4, It might be an interesting experiment to try running with the following added to the command line:
-e JUPYTER_RUNTIME_DIR=/tmpso that the kernel connection file is written to /tmp (and no “os boundaries” are crossed).I ran with the following and confirmed the kernel’s connection file (
kernel-<kernel-id>.json) to be in /tmp after running this is a cell!ls /tmp/kernel-*.And when I run it as Administrator. Nothing wrong