Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

Unable to install and start #45

Open
gta0anu opened this issue Mar 6, 2018 · 16 comments
Open

Unable to install and start #45

gta0anu opened this issue Mar 6, 2018 · 16 comments

Comments

@gta0anu
Copy link

gta0anu commented Mar 6, 2018

Hi,

I followed all the steps present in the respective GitHub repositories.

Here are the system details:
Distributor ID: Ubuntu
Description: Ubuntu 16.04.4 LTS
Release: 16.04

jupyter --version
4.4.0
jupyterhub --version
0.8.1
python --version
Python 2.7.12
python3 --version
Python 3.5.2
node --version
v8.9.4
npm --version
5.7.1

Facing following error while starting the jupyterhub after setting the jupyterhub_config.py

[E 2018-03-06 13:41:05.373 JupyterHub user:427] Unhandled error starting ubuntu's server: [Errno 2] No such file or directory: 'jupyterhub-labhub'

Tried looking for the file in the entire system also, no luck.

jupyter labextension install @jupyterlab/hub-extension

Getting the following warning when installing via
Command:

jupyter labextension install @jupyterlab/hub-extension

Error:

warning "@jupyterlab/json-extension > [email protected]" has unmet peer dependency "react@^0.14.0 || ^15.0.0 || ^16.0.0".
warning "@jupyterlab/json-extension > [email protected]" has unmet peer dependency "react@^15.0.0".
warning "@jupyterlab/json-extension > [email protected]" has unmet peer dependency "react-dom@^15.0.0".
warning "@jupyterlab/vdom-extension > @nteract/[email protected]" has unmet peer dependency "react@^15.6.1".
[4/4] Building fresh packages...
[-/2] ⠐ waiting...
[2/2] ⠐ canvas: gyp ERR!
[-/2] ⠐ waiting...
[-/2] ⠐ waiting...
warning Error running install script for optional dependency: "/usr/local/share/jupyter/lab/staging/node_modules/canvas: Command failed.\nExit code: 1\nCommand: node-gyp rebuild\nArguments: \nDirectory: /usr/local/share/jupyter/lab/staging/node_modules/canvas\nOutput:\ngyp info it worked if it ends with ok\ngyp info using [email protected]\ngyp info using [email protected] | linux | x64\ngyp info spawn /usr/bin/python2\ngyp info spawn args [ '/usr/lib/nodejs/node-v8.9.4/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',\ngyp info spawn args   'binding.gyp',\ngyp info spawn args   '-f',\ngyp info spawn args   'make',\ngyp info spawn args   '-I',\ngyp info spawn args   '/usr/local/share/jupyter/lab/staging/node_modules/canvas/build/config.gypi',\ngyp info spawn args   '-I',\ngyp info spawn args   '/usr/lib/nodejs/node-v8.9.4/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',\ngyp info spawn args   '-I',\ngyp info spawn args   '/root/.node-gyp/8.9.4/include/node/common.gypi',\ngyp info spawn args   '-Dlibrary=shared_library',\ngyp info spawn args   '-Dvisibility=default',\ngyp info spawn args   '-Dnode_root_dir=/root/.node-gyp/8.9.4',\ngyp info spawn args   '-Dnode_gyp_dir=/usr/lib/nodejs/node-v8.9.4/lib/node_modules/npm/node_modules/node-gyp',\ngyp info spawn args   '-Dnode_lib_file=/root/.node-gyp/8.9.4/<(target_arch)/node.lib',\ngyp info spawn args   '-Dmodule_root_dir=/usr/local/share/jupyter/lab/staging/node_modules/canvas',\ngyp info spawn args   '-Dnode_engine=v8',\ngyp info spawn args   '--depth=.',\ngyp info spawn args   '--no-parallel',\ngyp info spawn args   '--generator-output',\ngyp info spawn args   'build',\ngyp info spawn args   '-Goutput_dir=.' ]\n./util/has_lib.sh: 31: ./util/has_lib.sh: pkg-config: not found\ngyp: Call to './util/has_lib.sh freetype' returned exit status 0 while in binding.gyp. while trying to load binding.gyp\ngyp ERR! configure error \ngyp ERR! stack Error: `gyp` failed with exit code: 1\ngyp ERR! stack     at ChildProcess.onCpExit (/usr/lib/nodejs/node-v8.9.4/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:336:16)\ngyp ERR! stack     at emitTwo (events.js:126:13)\ngyp ERR! stack     at ChildProcess.emit (events.js:214:7)\ngyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_psuccess Saved lockfile.
@blink1073
Copy link
Contributor

Hi @gta0anu, it looks like the install went fine, but the spawner command should be jupyter-labhub instead of 'jupyterhub-labhub.

@gta0anu
Copy link
Author

gta0anu commented Mar 7, 2018

Hi @blink1073, that made it work. I want to ask one more thing, are we suppose to be able to logout from the JupyterLab? Because I am trying to logout and it just opens a new tab with JupyterHub login screen.

@blink1073
Copy link
Contributor

I believe that is intentional, it has logged you out and is presenting you with the ability to log back in.

@gta0anu
Copy link
Author

gta0anu commented Mar 13, 2018

But the jupyterlab never logs out. Is it not supposed to logout?

@itcarroll
Copy link

I see the same behavior as @gta0anu, the notebooks in the jupyterlab tab remain fully active after "logout" ... which doesn't appear to do anything but open a new login tab.

@gta0anu
Copy link
Author

gta0anu commented May 10, 2018

Hi,

Is the jupyter lab not supposed to log out?

@liffiton
Copy link
Contributor

I think PR #59 fixes the logout issue. I don't know when a new package will be uploaded to npm, though.

@blink1073
Copy link
Contributor

I just pushed 0.9.1 to npm.

@gta0anu
Copy link
Author

gta0anu commented Jun 13, 2018

@blink1073 I will test out 0.9.1 and provide feedback. Thanks.

@dhirschfeld
Copy link

This can probably be closed to reduce noise in the issues list

@echyam
Copy link

echyam commented Sep 20, 2018

I think this is related to the original issue here. The extension installed without giving me any issues, and I can run JupyterHub and JupyterLab with no problem. But I get the following error when I try to run sudo jupyterhub -f ./jupyterhub_config.py with c.Spawner.cmd = ['jupyter-labhub'] in my jupyterhub_config.py.

Unhandled error starting testuser's server: [Errno 2] No such file or directory: 'jupyter-labhub'

Would there any reason why JupyterHub can't find jupyter-labhub?

@blink1073
Copy link
Contributor

Is which jupyter-labhub on the same root path as which jupyterhub?

@echyam
Copy link

echyam commented Sep 21, 2018

which jupyterhub gives /usr/local/bin/jupyterhub
which jupyter-labhub gives /home/ubuntu/anaconda3/bin/jupyter-labhub
which jupyter gives /usr/local/bin/jupyter
We actually installed all of them using conda, so when we moved that to the front of the path, all of them now show
/home/ubuntu/anaconda3/bin/jupyter-labhub
/home/ubuntu/anaconda3/bin/jupyterhub
/home/ubuntu/anaconda3/bin/jupyter
But we're still getting the same error. What's strange is running jupyterhub alone (without putting jupyter-labhub) works fine, but running notebook and lab outside the context of jupyterhub doesn't work and they give the following error when we try to close them:

Serving notebooks from local directory: /home/ubuntu
0 active kernels 
The Jupyter Notebook is running at: http://localhost:8890/?token=ead834f6c489da53d2fbd689d7cef46faff93d39764a9a6e
Shutdown this notebook server (y/[n])? y
[C 23:14:07.930 LabApp] Shutdown confirmed
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/home/ubuntu/anaconda3/lib/python3.6/threading.py", line 916, in _bootstrap_inner
    self.run()
  File "/home/ubuntu/anaconda3/lib/python3.6/threading.py", line 864, in run
    self._target(*self._args, **self._kwargs)
  File "/home/ubuntu/anaconda3/lib/python3.6/site-packages/notebook/notebookapp.py", line 1075, in _confirm_exit
    ioloop.IOLoop.current().stop()
  File "/home/ubuntu/anaconda3/lib/python3.6/site-packages/zmq/eventloop/ioloop.py", line 116, in current
    loop = ioloop.IOLoop.current(*args, **kwargs)
  File "/home/ubuntu/anaconda3/lib/python3.6/site-packages/tornado/ioloop.py", line 282, in current
    loop = asyncio.get_event_loop()
  File "/home/ubuntu/anaconda3/lib/python3.6/asyncio/events.py", line 671, in get_event_loop
    return get_event_loop_policy().get_event_loop()
  File "/home/ubuntu/anaconda3/lib/python3.6/asyncio/events.py", line 583, in get_event_loop
    % threading.current_thread().name)
RuntimeError: There is no current event loop in thread 'Thread-1'.

@blink1073
Copy link
Contributor

Hi @echyam, it would help to have more context about your setup. I wasn't able to replicate in Ubuntu 18.04. Would you mind filing a new issue and filling in the new bug report template?

@echyam
Copy link

echyam commented Sep 25, 2018

I don't know what went wrong before (probably something to do with the configs), but I uninstalled everything and reinstalled it, and it worked. Thanks for your help!

@blink1073
Copy link
Contributor

Glad you got sorted!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants