search

jupyterhub / jupyterhub-deploy-teaching

Reference deployment of JupyterHub and nbgrader on a single server
http://jupyterhub-deploy-teaching.readthedocs.io/en/latest/
BSD 3-Clause "New" or "Revised" License
247 stars 85 forks source link

config-http-proxy not installing #26

Closed ellisonbg closed 8 years ago

ellisonbg commented 8 years ago

With a fresh deployment, I get an error:

[I 2016-10-02 15:50:13.731 JupyterHub app:624] Loading cookie_secret from /srv/jupyterhub/cookie_secret
[I 2016-10-02 15:50:13.819 JupyterHub app:1232] Hub API listening on http://127.0.0.1:8081/hub/
[W 2016-10-02 15:50:13.822 JupyterHub app:960] Running JupyterHub without SSL. There better be SSL termination happening somewhere else...
[I 2016-10-02 15:50:13.822 JupyterHub app:969] Starting proxy @ http://65.61.190.162:8000/
[E 2016-10-02 15:50:13.824 JupyterHub app:977] Failed to find proxy ['configurable-http-proxy']
    The proxy can be installed with `npm install -g configurable-http-proxy`

Running conda list does not show the configurable-http-proxy package.

@minrk @willingc any ideas?

ellisonbg commented 8 years ago

Hmm, running conda install configurable-http-proxy seems to work, don't know why it failed in the ansible stuff...

willingc commented 8 years ago

@ellisonbg Just to clarify... are you running 16.04 LTS or 14.04 LTS?

ellisonbg commented 8 years ago

14.04

minrk commented 8 years ago

@ellisonbg CHP is only packaged by conda-forge, so if it's failing, that could mean that the conda-forge channel is not enabled.

minrk commented 8 years ago

@ellisonbg how did you provision the server? Did you run anything prior to the deploy?

jkuruzovich commented 8 years ago

I got the same error and used the following and got it to work:

ssh root@servername

  1. apt install npm
  2. git clone https://github.com/jupyter/configurable-http-proxy.git
  3. cd configurable-http-proxy
  4. sudo npm install -g
  5. PATH="$PATH:/usr/local/bin" npm install -g bower less grunt-cli
  6. sudo apt-get install nodejs-legacy
  7. supervisorctl (if not running then supervisord)
  8. start all

I found this an issue on Ubuntu 16.04.

ellisonbg commented 8 years ago

@minrk it was a fresh 14.04 server on rackspace. I hadn't done anything before I ran the ansible scripts. The only other thing I did was to change the ansible config file to run things as root (that is the user that rackspace uses).

minrk commented 8 years ago

What exact flavor of VM, setup? Did you use let's encrypt? I ran with the changes in #28 and it completed in one go on 14.04 and 16.04. The changes I made don't seem like they would be relevant to the issues you had, though.

Can you share your vars file (privately)? Maybe some choices you made caused it to take a different path than mine.

willingc commented 8 years ago

I'm wondering if this is perhaps a node installation issue with 14.04 and Rackspace.

https://nodejs.org/en/download/package-manager/

The nodejs-legacy package installs a node symlink that is needed by many modules to build and run correctly. The Node.js modules available in the distribution official repositories do not need it.

Rackspace doc: https://developer.rackspace.com/sdks/node-js/

minrk commented 8 years ago

@willingc we don't install nodejs with apt, we install it with conda. The issue appears to be that @ellisonbg is not getting packages from conda-forge, where configurable-http-proxy is packaged.