I am trying to run jupyter lab but the kernel is not connecting and I am not too sure the reason why. Any help will be appreciated thank you so much! This is the error I am getting:
RuntimeError: This event loop is already running
[W 2022-02-11 09:54:20.931 ServerApp] AsyncIOLoopKernelRestarter: restart failed
[W 2022-02-11 09:54:20.931 ServerApp] Kernel c9bb27e5-56fc-4daf-9631-306d5d277217 died, removing from map.
[W 2022-02-11 09:54:20.949 ServerApp] AsyncIOLoopKernelRestarter: restart failed
[W 2022-02-11 09:54:20.949 ServerApp] Kernel d2ab9d87-1ddd-4cdb-a7a7-3bfaf3e91fc0 died, removing from map.
[W 2022-02-11 09:54:20.960 ServerApp] AsyncIOLoopKernelRestarter: restart failed
[W 2022-02-11 09:54:20.961 ServerApp] Kernel b17914dd-d148-4d22-af26-f1a0a9f6149e died, removing from map.
[W 2022-02-11 09:54:20.972 ServerApp] AsyncIOLoopKernelRestarter: restart failed
[W 2022-02-11 09:54:20.972 ServerApp] Kernel b37ce6bf-f2cb-428d-8188-f6b41ab3309e died, removing from map.
[W 2022-02-11 09:55:05.901 ServerApp] Timeout waiting for kernel_info reply from b37ce6bf-f2cb-428d-8188-f6b41ab3309e
[E 2022-02-11 09:55:05.904 ServerApp] Error opening stream: HTTP 404: Not Found (Kernel does not exist: b37ce6bf-f2cb-428d-8188-f6b41ab3309e)
[W 2022-02-11 09:55:06.196 ServerApp] Timeout waiting for kernel_info reply from c9bb27e5-56fc-4daf-9631-306d5d277217
[E 2022-02-11 09:55:06.197 ServerApp] Error opening stream: HTTP 404: Not Found (Kernel does not exist: c9bb27e5-56fc-4daf-9631-306d5d277217)
If you are using Anaconda to run Python then this post might be useful ...
http://www.techanswersweb.com/kernel-error-jupyter-notebook
Related
I had installed the couchdb 3.2.1. The service started automatically on server boot. After upgrading automatically to 3.2.2 all went wrong and i removed 3.2.1 and made a fresh install of 3.2.2. All is working except the start of the service if the server boots. What can i do to fix this? Thank you.
EDIT:
Following the suggestion of Honeywild, i confirm that the service is enabled. I reboot the server and the couchdb did not started again. In the log appeared this:
[error] 2022-04-26T12:49:53.718192Z couchdb#127.0.0.1 <0.3835.0> -------- OS Process died with status: 143
[error] 2022-04-26T12:49:53.719167Z couchdb#127.0.0.1 <0.3894.0> -------- OS Process died with status: 143
[error] 2022-04-26T12:49:53.838879Z couchdb#127.0.0.1 <0.3835.0> -------- gen_server <0.3835.0> terminated with reason: {exit_status,143}
[error] 2022-04-26T12:49:53.839013Z couchdb#127.0.0.1 <0.3835.0> -------- gen_server <0.3835.0> terminated with reason: {exit_status,143}
[error] 2022-04-26T12:49:53.839087Z couchdb#127.0.0.1 <0.3894.0> -------- gen_server <0.3894.0> terminated with reason: {exit_status,143}
[error] 2022-04-26T12:49:53.839171Z couchdb#127.0.0.1 <0.3894.0> -------- gen_server <0.3894.0> terminated with reason: {exit_status,143}
[error] 2022-04-26T12:49:53.843963Z couchdb#127.0.0.1 <0.3835.0> -------- CRASH REPORT Process (<0.3835.0>) with 0 neighbors exited with reason: {exit_status,143} at gen_server:handle_common_reply/8(line:805) <= proc_lib:init_p_do_apply/3(line:226); initial_call: {couch_os_process,init,['Argument__1']}, ancestors: [<0.3834.0>], message_queue_len: 0, links: [<0.279.0>], dictionary: [], trap_exit: false, status: running, heap_size: 987, stack_size: 28, reductions: 5062
[error] 2022-04-26T12:49:53.844450Z couchdb#127.0.0.1 <0.3835.0> -------- CRASH REPORT Process (<0.3835.0>) with 0 neighbors exited with reason: {exit_status,143} at gen_server:handle_common_reply/8(line:805) <= proc_lib:init_p_do_apply/3(line:226); initial_call: {couch_os_process,init,['Argument__1']}, ancestors: [<0.3834.0>], message_queue_len: 0, links: [<0.279.0>], dictionary: [], trap_exit: false, status: running, heap_size: 987, stack_size: 28, reductions: 5062
[error] 2022-04-26T12:49:53.844742Z couchdb#127.0.0.1 <0.3894.0> -------- CRASH REPORT Process (<0.3894.0>) with 0 neighbors exited with reason: {exit_status,143} at gen_server:handle_common_reply/8(line:805) <= proc_lib:init_p_do_apply/3(line:226); initial_call: {couch_os_process,init,['Argument__1']}, ancestors: [<0.3893.0>], message_queue_len: 0, links: [<0.279.0>], dictionary: [], trap_exit: false, status: running, heap_size: 987, stack_size: 28, reductions: 8319
[error] 2022-04-26T12:49:53.845669Z couchdb#127.0.0.1 <0.3894.0> -------- CRASH REPORT Process (<0.3894.0>) with 0 neighbors exited with reason: {exit_status,143} at gen_server:handle_common_reply/8(line:805) <= proc_lib:init_p_do_apply/3(line:226); initial_call: {couch_os_process,init,['Argument__1']}, ancestors: [<0.3893.0>], message_queue_len: 0, links: [<0.279.0>], dictionary: [], trap_exit: false, status: running, heap_size: 987, stack_size: 28, reductions: 8319
[error] 2022-04-26T12:49:53.867452Z couchdb#127.0.0.1 <0.549.0> -------- gen_server <0.549.0> terminated with reason: killed
[error] 2022-04-26T12:49:53.867542Z couchdb#127.0.0.1 <0.549.0> -------- gen_server <0.549.0> terminated with reason: killed
[error] 2022-04-26T12:49:53.867706Z couchdb#127.0.0.1 <0.549.0> -------- CRASH REPORT Process (<0.549.0>) with 0 neighbors exited with reason: killed at gen_server:decode_msg/9(line:475) <= proc_lib:init_p_do_apply/3(line:226); initial_call: {couch_multidb_changes,init,['Argument__1']}, ancestors: [<0.431.0>,couch_replicator_sup,<0.397.0>], message_queue_len: 0, links: [], dictionary: [], trap_exit: true, status: running, heap_size: 2586, stack_size: 28, reductions: 12699
[error] 2022-04-26T12:49:53.867823Z couchdb#127.0.0.1 <0.549.0> -------- CRASH REPORT Process (<0.549.0>) with 0 neighbors exited with reason: killed at gen_server:decode_msg/9(line:475) <= proc_lib:init_p_do_apply/3(line:226); initial_call: {couch_multidb_changes,init,['Argument..
Then i simple run service couchdb start, and it started without any problem.
This kind of problems did not occur in previous couchdb version and usually i simple made upgrade without any problems. I am using Ubuntu 20.04.04 LTS.
Any more ideas? Than you.
First of all, check if the systemctl service is enabled, run systemctl is-enabled
sudo systemctl list-unit-files | grep enabled | grep couchdb
or
sudo systemctl list-unit-files --state=enabled | grep couchdb
if the output to a console will be empty, run:
sudo systemctl enable couchdb.service
then check again:
sudo systemctl list-unit-files --state=enabled | grep couchdb
next, if the service has been enabled, you did right, you followed a good practice, which is to identify the error in the logs.
Probably you tried:
sudo journalctl -u couchdb.service
and then you found the error which you mentioned above.
Further research steps can include:
Disable the systemd service (temporary): systemctl disable couchdb
Reboot
Run the application manually not as a systemd service /path/to/couchdb and check a result.
Run the application manually with strace strace /path/to/couchdband check a result.
One more idea:
You have to be sure that the service is started after the network is started
More:
agree and conduct a diagnostic session together to understand what exactly causes this error.
There was an update from couchdb that fixed the problem: now version is 3.2.2-2 in ubuntu.
I'm trying to set up a docker container with a jupyter notebook installed. Everything seems to be running fine until I open an .ipynb file.
Here's the debug logs from running jupyter:
jupyter_1 | [D 16:32:58.134 NotebookApp] Native kernel (python3) available from /root/anaconda/lib/python3.6/site-packages/ipykernel/resources
jupyter_1 | [D 16:32:58.135 NotebookApp] Starting kernel: ['/root/anaconda/bin/python', '-m', 'ipykernel', '-f', '/root/.local/share/jupyter/runtime/kernel-d709c271-698e-4593-9e21-ee782bb057a1.json']
jupyter_1 | [D 16:32:58.140 NotebookApp] Connecting to: tcp://127.0.0.1:50259
jupyter_1 | [I 16:32:58.140 NotebookApp] Kernel started: d709c271-698e-4593-9e21-ee782bb057a1
jupyter_1 | [D 16:32:58.140 NotebookApp] Kernel args: {'kernel_name': 'python3', 'cwd': '/var/workspace'}
jupyter_1 | [D 16:32:58.142 NotebookApp] 201 POST /api/sessions (172.19.0.1) 12.44ms
jupyter_1 | [D 16:32:58.144 NotebookApp] 200 GET /api/contents/Untitled.ipynb/checkpoints?_=1495902777780 (172.19.0.1) 1.26ms
jupyter_1 | [D 16:32:58.214 NotebookApp] 304 GET /static/components/MathJax/extensions/Safe.js?rev=2.6.0 (172.19.0.1) 1.21ms
jupyter_1 | [D 16:32:58.297 NotebookApp] Initializing websocket connection /api/kernels/d709c271-698e-4593-9e21-ee782bb057a1/channels
jupyter_1 | [D 16:32:58.300 NotebookApp] Requesting kernel info from d709c271-698e-4593-9e21-ee782bb057a1
jupyter_1 | [D 16:32:58.300 NotebookApp] Connecting to: tcp://127.0.0.1:37738
jupyter_1 | [I 16:33:01.142 NotebookApp] KernelRestarter: restarting kernel (1/5)
jupyter_1 | [D 16:33:01.144 NotebookApp] Starting kernel: ['/root/anaconda/bin/python', '-m', 'ipykernel', '-f', '/root/.local/share/jupyter/runtime/kernel-d709c271-698e-4593-9e21-ee782bb057a1.json']
jupyter_1 | [D 16:33:01.149 NotebookApp] Connecting to: tcp://127.0.0.1:50259
jupyter_1 | [I 16:33:04.152 NotebookApp] KernelRestarter: restarting kernel (2/5)
jupyter_1 | [D 16:33:04.153 NotebookApp] Starting kernel: ['/root/anaconda/bin/python', '-m', 'ipykernel', '-f', '/root/.local/share/jupyter/runtime/kernel-d709c271-698e-4593-9e21-ee782bb057a1.json']
jupyter_1 | [D 16:33:04.159 NotebookApp] Connecting to: tcp://127.0.0.1:50259
jupyter_1 | [I 16:33:07.161 NotebookApp] KernelRestarter: restarting kernel (3/5)
jupyter_1 | [D 16:33:07.162 NotebookApp] Starting kernel: ['/root/anaconda/bin/python', '-m', 'ipykernel', '-f', '/root/.local/share/jupyter/runtime/kernel-d709c271-698e-4593-9e21-ee782bb057a1.json']
jupyter_1 | [D 16:33:07.168 NotebookApp] Connecting to: tcp://127.0.0.1:50259
jupyter_1 | [W 16:33:08.302 NotebookApp] Timeout waiting for kernel_info reply from d709c271-698e-4593-9e21-ee782bb057a1
jupyter_1 | [D 16:33:08.303 NotebookApp] Opening websocket /api/kernels/d709c271-698e-4593-9e21-ee782bb057a1/channels
jupyter_1 | [D 16:33:08.304 NotebookApp] Connecting to: tcp://127.0.0.1:37738
jupyter_1 | [D 16:33:08.305 NotebookApp] Connecting to: tcp://127.0.0.1:46487
jupyter_1 | [D 16:33:08.305 NotebookApp] Connecting to: tcp://127.0.0.1:48305
jupyter_1 | [I 16:33:10.169 NotebookApp] KernelRestarter: restarting kernel (4/5)
jupyter_1 | WARNING:root:kernel d709c271-698e-4593-9e21-ee782bb057a1 restarted
jupyter_1 | [D 16:33:10.171 NotebookApp] Starting kernel: ['/root/anaconda/bin/python', '-m', 'ipykernel', '-f', '/root/.local/share/jupyter/runtime/kernel-d709c271-698e-4593-9e21-ee782bb057a1.json']
jupyter_1 | [D 16:33:10.176 NotebookApp] Connecting to: tcp://127.0.0.1:50259
jupyter_1 | [W 16:33:13.177 NotebookApp] KernelRestarter: restart failed
jupyter_1 | [W 16:33:13.178 NotebookApp] Kernel d709c271-698e-4593-9e21-ee782bb057a1 died, removing from map.
jupyter_1 | ERROR:root:kernel d709c271-698e-4593-9e21-ee782bb057a1 restarted failed!
jupyter_1 | [D 16:33:13.185 NotebookApp] Websocket closed d709c271-698e-4593-9e21-ee782bb057a1:0580392FC0924FAA8D06C61958352847
jupyter_1 | [W 16:33:13.188 NotebookApp] Kernel deleted before session
jupyter_1 | [W 16:33:13.189 NotebookApp] 410 DELETE /api/sessions/892c369f-0dda-4d24-a084-52c7646c79e6 (172.19.0.1) 1.49ms referer=http://0.0.0.0:8888/notebooks/Untitled.ipynb
And for reference here's my Dockerfile:
FROM ubuntu:16.04
## install python
RUN apt-get update \
&& apt-get install -y apt-utils python3 python3-pip wget \
&& pip3 install --upgrade pip setuptools
## Install anaconda and do cleanup
RUN wget https://repo.continuum.io/archive/Anaconda3-4.3.1-Linux-x86_64.sh -O anaconda.sh \
&& chmod 700 anaconda.sh \
&& /bin/bash anaconda.sh -bp /root/anaconda \
&& rm -f anaconda.sh \
&& /root/anaconda/bin/conda install -y jupyter
WORKDIR /var/workspace
EXPOSE 8888
CMD ["/root/anaconda/bin/jupyter", "notebook", "--no-browser", "--ip=0.0.0.0", "--log-level=DEBUG"]
This is actually the second attempt, the first of which I have on my github account in which I tried to do this on a alpine linux install and I was having the same problem there. I switched to ubuntu just to make sure that wasn't the issue.
Ideally I'd like to get debug logs from the kernel itself, but I don't see any way to get the system to pass the debug log level onto the kernel. Perhaps I'll try hacking the site-packages files to see if I can update the system call to include the debug flags.
In the mean-time, has anyone experienced this and found a solution?
Oh.. btw. I have this installed locally and it works just fine. I could give up and just use that, but what fun would that be?
I've installed Docker via pacman -S docker, but when I'm trying to run Dockerd it says
INFO[0000] libcontainerd: new containerd process, pid: 9792
WARN[0000] containerd: low RLIMIT_NOFILE changing to max current=1024 max=4096
FATA[0001] Your Linux kernel version 3.4.39 is not supported for running docker. Please upgrade your kernel to 3.10.0 or newer.
I'm trying to run it with DOCKER_NOWARN_KERNEL_VERSION=1 and it gives me
INFO[0000] libcontainerd: new containerd process, pid: 9810
WARN[0000] containerd: low RLIMIT_NOFILE changing to max current=1024 max=4096
ERRO[0001] [graphdriver] prior storage driver devicemapper failed: devicemapper: Error running deviceCreate (CreatePool) dm_task_run failed
Error starting daemon: error initializing graphdriver: devicemapper: Error running deviceCreate (CreatePool) dm_task_run failed
What did I do wrong?!..
Running this on Orang Pi PC
Thanks
I've found, that kernel > 4.0 does exist for this Pi. I've installed Armbian on my Orange Pi PC and I'm sure that it the best thing you could install. I goes with linux-4.10.3 on the board and works fine.
Been stuck in this issue for the past two days.
Followed the github link regarding this issue. Didn't worked.
https://github.com/jupyter/jupyterhub/issues/237
saimmehmood#saimmehmood-VirtualBox:~$ sudo jupyterhub
[sudo] password for saimmehmood:
[I 2016-03-22 02:18:54.577 JupyterHub app:558] Loading cookie_secret from /home/saimmehmood/jupyterhub_cookie_secret
[W 2016-03-22 02:18:54.865 JupyterHub app:292]
Generating CONFIGPROXY_AUTH_TOKEN. Restarting the Hub will require restarting the proxy.
Set CONFIGPROXY_AUTH_TOKEN env or JupyterHub.proxy_auth_token config to avoid this message.
[W 2016-03-22 02:18:54.893 JupyterHub app:685] No admin users, admin interface will be unavailable.
[W 2016-03-22 02:18:54.900 JupyterHub app:686] Add any administrative users to `c.Authenticator.admin_users` in config.
[I 2016-03-22 02:18:54.906 JupyterHub app:712] Not using whitelist. Any authenticated user will be allowed.
[I 2016-03-22 02:18:55.016 JupyterHub app:1113] Hub API listening on http://127.0.0.1:8081/hub/
[E 2016-03-22 02:18:55.055 JupyterHub app:855] Refusing to run JuptyterHub without SSL. If you are terminating SSL in another layer, pass --no-ssl to tell JupyterHub to allow the proxy to listen on HTTP.
saimmehmood#saimmehmood-VirtualBox:~$ sudo jupyterhub --no-ssl
[I 2016-03-22 02:19:12.896 JupyterHub app:558] Loading cookie_secret from /home/saimmehmood/jupyterhub_cookie_secret
[W 2016-03-22 02:19:13.046 JupyterHub app:292]
Generating CONFIGPROXY_AUTH_TOKEN. Restarting the Hub will require restarting the proxy.
Set CONFIGPROXY_AUTH_TOKEN env or JupyterHub.proxy_auth_token config to avoid this message.
[W 2016-03-22 02:19:13.079 JupyterHub app:685] No admin users, admin interface will be unavailable.
[W 2016-03-22 02:19:13.080 JupyterHub app:686] Add any administrative users to `c.Authenticator.admin_users` in config.
[I 2016-03-22 02:19:13.080 JupyterHub app:712] Not using whitelist. Any authenticated user will be allowed.
[I 2016-03-22 02:19:13.149 JupyterHub app:1113] Hub API listening on http://127.0.0.1:8081/hub/
[W 2016-03-22 02:19:13.174 JupyterHub app:851] Running JupyterHub without SSL. There better be SSL termination happening somewhere else...
[I 2016-03-22 02:19:13.174 JupyterHub app:860] Starting proxy # http://*:8000/
/usr/bin/env: node: No such file or directory
[C 2016-03-22 02:19:14.297 JupyterHub app:1119] Failed to start proxy
Traceback (most recent call last):
File "/usr/local/lib/python3.4/dist-packages/jupyterhub/app.py", line 1117, in start
yield self.start_proxy()
File "/usr/local/lib/python3.4/dist-packages/jupyterhub/app.py", line 881, in start_proxy
_check()
File "/usr/local/lib/python3.4/dist-packages/jupyterhub/app.py", line 877, in _check
raise e
RuntimeError: Proxy failed to start with exit code 127
Kindly let me know any solution.
Thank you!
It looks like the problem is in this line
/usr/bin/env: node: No such file or directory
Either you don't have nodejs installed or it's not in $PATH. Note that nodejs/npm are required to run jupyterhub. It looks like you're running some linux distribution so you should just be able to run
sudo apt-get install npm nodejs-legacy
See the JupyterHub GitHub page and the docs for more info.
I am able to start an NX session without any issues. But, when I 'disconnect' (leaving a persistent connection, as opposed to 'terminate'), I am unable to reconnect. Here is the error from /var/log/messages:
Aug 5 19:05:41 praveen NXNODE-3.5.0-3[20703]: ERROR: NX> 596 ERROR: NXNODE Ver. 3.5.0-3 (Error id e77ECD3) [e77ECD3] Logger::log nxnode 2963
Aug 5 19:05:41 praveen NXNODE-3.5.0-3[20703]: ERROR: NX> 596 ERROR: create session: run commands [e77ECD3] Logger::log nxnode 2963
Aug 5 19:05:41 praveen NXNODE-3.5.0-3[20703]: ERROR: NX> 596 ERROR: execution of last command failed [e77ECD3] Logger::log nxnode 2963
Aug 5 19:05:41 praveen NXNODE-3.5.0-3[20703]: ERROR: NX> 596 last command: /usr/bin/xauth -v source /home/pmohandas/.nx/C-praveen-1003-707A5CF0D1B5184E1EBEDC07BB4981EF/scripts/authority [e77ECD3] Logger::log nxnode 2963
Aug 5 19:05:41 praveen NXNODE-3.5.0-3[20703]: ERROR: NX> 596 exit value: 1 [e77ECD3] Logger::log nxnode 2963
Aug 5 19:05:41 praveen NXNODE-3.5.0-3[20703]: ERROR: NX> 596 stdout: [e77ECD3] Logger::log nxnode 2963
Aug 5 19:05:41 praveen NXNODE-3.5.0-3[20703]: ERROR: NX> 596 stderr: /usr/bin/xauth: error in locking authority file /home/pmohandas/.Xauthority [e77ECD3] Logger::log nxnode 2963
I am on a RHEL6.1 x86_64 machine.
I tried running xauth -b quit prior to reconnecting to the NX session. No luck with that either.
Does anyone know how I could get rid of this error? I find NX to be much snappier than VNC and would love to get this to work :) Thanks in advance!
I don't know the cause of this annoying error yet either, but a workaround is to ssh to the nx server machine and remove your ~/.Xauthority-c and ~/.Xauthority-l files. You'll lose any existing sessions, but you will still be able to connect.
Solution here from : http://forums.fedoraforum.org/showthread.php?t=223609
First I must say that I'm running my installation in a virtual machine but I think that doesn't matter.
Problem: I found out that the hostname I enter at the installation wasn't added to the /etc/hosts file. There were only the default entries for localhost/localdomain.
So the DNS server (see /etc/resolve.conf which is generated by the network manager) couldn't resolve my hostname which is needed for xauth.
You can check this by traceroute your hostname (note nslookup or host won't work because they ignore /etc/hosts).
Solution: I just added my hostname to the /etc/hosts file, checked it with traceroute and connected via nxclient from my windows host.
So adding server.craneworks to /etc/hosts should solve the problem for you.
The problem seems to happen when you have duplicate entries in your /etc/hosts. Here is the xauth bug: http://www.kerneltrap.com/mailarchive/openbsd-bugs/2009/3/8/5118304
Fixed the problem by removing the duplicate entries in /etc/hosts.