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.
Related
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
I use google cloud shell to execute this program
Linux version
Distributor ID: Debian
Description: Debian GNU/Linux 10 (buster)
Release: 10
Codename: buster
Tor version 0.3.5.10.
When I tried restarting "sudo service tor restart" Tor I received an error
[ ok ] Stopping tor daemon...done (not running - there is no /run/tor/tor.pid).
[....] Starting tor daemon...Jun 27 01:51:04.132 [warn] Directory /var/lib/tor cannot be read: Permission denied
Jun 27 01:51:04.132 [warn] Failed to parse/validate config: Couldn't create private data directory "/var/lib/tor"
Jun 27 01:51:04.132 [err] Reading config failed--see warnings above.
failed.
So I set full permissions for the tor directory sudo chmod -R 777 /var/lib/tor
[FAIL] Checking if tor configuration is valid ... failed!
Jun 27 01:53:59.685 [notice] Tor 0.3.5.10 running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1g, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.3.8.
Jun 27 01:53:59.685 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Jun 27 01:53:59.685 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Jun 27 01:53:59.685 [notice] Read configuration file "/etc/tor/torrc".
Jun 27 01:53:59.688 [warn] Error setting groups to gid 114: "Operation not permitted".
Jun 27 01:53:59.688 [warn] If you set the "User" option, you must start Tor as root.
Jun 27 01:53:59.688 [warn] Failed to parse/validate config: Problem with User value. See logs for details.
Jun 27 01:53:59.688 [err] Reading config failed--see warnings above.
I use root privileges sudo su
[ ok ] Stopping tor daemon...done (not running - there is no /run/tor/tor.pid).
[....] Starting tor daemon...Jun 27 01:58:58.455 [warn] Directory /var/lib/tor cannot be read: Permission denied
Jun 27 01:58:58.455 [warn] Failed to parse/validate config: Couldn't create private data directory "/var/lib/tor"
Jun 27 01:58:58.455 [err] Reading config failed--see warnings above.
Is there any way that can help me solve my problem or how can i be able to install tor version 2.9.14?
You might have already solved the problem by now, if not I hope this can help.
Is there any way that can help me solve my problem?
OPTION 1
Let's take a look at these warnings:
[warn] Error setting groups to gid 114: "Operation not permitted".
[warn] If you set the "User" option, you must start Tor as root.
[warn] Failed to parse/validate config: Problem with User value.
To get a log of all users run cat /etc/passwd and you'll see debian-tor listed:
...
debian-tor:x:108:114::/var/lib/tor:/bin/false
...
The folder /var/lib/tor is owned by user debian-tor, so sudo -u debian-tor tor will work.
Alternatively, you can run this for your current user: (or chmod 777 for all)
chmod 700 -R /var/lib/tor/*
chown -R tor /var/lib/tor/
sudo service tor restart
You actually should run tor as non-root, else you get this message:
You are running Tor as root. You don't need to, and you probably shouldn't.
OPTION 2
As the warning suggests to see logs for details you should check for a message within dsmeg and /var/log/syslog. If you find anything then it can be AppArmor or SELinux blocking tor. Both SELinux and AppArmor provide a set of tools to isolate applications from each other to protect the host system from being compromised, so it's not recommended disabling them permanently but temporarily for debugging.
According to Debian SELinux support:
The Debian packaged Linux kernels have SELinux support compiled in,
but disabled by default.
Check the SELinux state with getenforce, if the output is Permissive or Disabled then you're set.
Moreover, looking at AppArmor/Progress:
Since Debian 10 (Buster), AppArmor is enabled by default.
To disable AppArmor on your system run: (reference)
sudo mkdir -p /etc/default/grub.d
echo 'GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT apparmor=0"' \
| sudo tee /etc/default/grub.d/apparmor.cfg
sudo update-grub
sudo reboot
There's a chance that either one's the culprit. Users have reported similar issue here.
How can i be able to install tor version 2.9.14?
Downgrading the tor package is as simple as this:
sudo apt-get install tor=0.2.9.14
But why would you want do that?
tor v2 will be deprecated soon. You'll see warnings like:
[warn] At least one protocol listed as required in the consensus is
not supported by this version of Tor. You should upgrade. This version
of Tor will not work as a client on the Tor network. The missing
protocols are: DirCache=2 HSDir=2 HSIntro=4 Link=4-5
NB: Post on tor.stackexchange for tor related issues.
I was trying to send message to the microbit using Bluezero I am using macOS, but got and error.
Sample code.
from bluezero import microbit
ubit = microbit.Microbit(adapter_addr='x',
device_addr='x',
accelerometer_service=True,
button_service=True,
magnetometer_service=False,
pin_service=False,
temperature_service=True)
my_text = 'Hello, world'
ubit.connect()
while my_text is not '':
ubit.text = my_text
my_text = input('Enter message: ')
ubit.disconnect()
Error
dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket
/opt/local/var/run/dbus/system_bus_socket: No such file or directory
I've get this error on Ubuntu 20
Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
normally this file is created/listening by dbus daemon
# netstat --all --program | grep system_bus_socket
unix 2 [ ACC ] STREAM LISTENING 19161 1/init /run/dbus/system_bus_socket
but on this server dbus.service is not running
# systemctl status dbus.service
● dbus.service - D-Bus System Message Bus
Loaded: loaded (/lib/systemd/system/dbus.service; static; vendor preset: enabled)
Active: inactive (dead)
TriggeredBy: ● dbus.socket
Docs: man:dbus-daemon(1)
attempt to start dbus.service failed
# systemctl start dbus.service
Failed to start dbus.service: Operation refused, unit dbus.service may be requested by dependency only (it is configured to refuse manual start/stop).
Maybe it can be started by systemctl start dbus.socket but I've solved this by finding service which has dependency on dbus.service it was firewalld
# grep -r dbus /etc/systemd/system/*
/etc/systemd/system/dbus-org.fedoraproject.FirewallD1.service:After=dbus.service
and start it
# systemctl start firewalld
and that's it
# ls -la /var/run/dbus/system_bus_socket
srw-rw-rw- 1 root root 0 Jul 28 13:45 /var/run/dbus/system_bus_socket
The Bluezero library talks via DBus to the BlueZ bluetooth daemon (bluetoothd). As BlueZ is not available for MacOS, this is not going to work.
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?
Issue:
sudo service opscenterd start
Failed to start opscenterd.service: Unit opscenterd.service failed to load: No such file or directory.
(ERROR)-(Exit Code 6)-(Unknown error code)
sudo service opscenterd status
opscenterd.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
Config
[webserver]
port = 8888
interface = 0.0.0.0
I tried another port and ip (localhost)
Cassandra installed and running (dsc21, cassandra 2.1.10)
no log files been generated in /var/log/opscenter/
opscenter installed via apt-get (5.2)
Please help me to resolve this issue
I have the same issues as you, seems like OpsCenter could not run as service on Ubuntu 15, I went running it as background process and it works,
try:
$ sudo your_opscenter_install_path/bin/opscenter
hope helpping