search

npm / npme-installer

npm Enterprise installer
https://www.npmjs.com/enterprise
Other
35 stars 21 forks source link

Test on Ubuntu 15 Vivid #89

Closed nexdrew closed 8 years ago

nexdrew commented 8 years ago
Min kernel version Compatible Docker versions
3.10 1.8 - latest (1.9)
nexdrew commented 8 years ago

I encountered no problems on a fresh instance of Ubuntu 15.10 Wily in AWS (ami-305d115a).

$ curl -sL https://deb.nodesource.com/setup_4.x | sudo -E bash -
$ sudo apt-get install -y nodejs
$ node -v && npm -v
v4.2.3
2.14.7
$ sudo npm install npmo -g --unsafe

After this, configuration and startup via admin web console on port 8800 worked as expected. :+1:

nexdrew commented 8 years ago

Note that Ubuntu systems upgraded to 15.10 from a prior version may have a problem starting the replicated daemons:

Setting up replicated (1.2-77) ...
start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
dpkg: error processing package replicated (--configure):
subprocess installed post-installation script returned error exit status 1
Setting up replicated-ui (1.2-52) ...
start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
dpkg: error processing package replicated-ui (--configure):
subprocess installed post-installation script returned error exit status 1
Setting up replicated-updater (1.2-26) ...
start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
dpkg: error processing package replicated-updater (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
replicated
replicated-ui
replicated-updater
E: Sub-process /usr/bin/dpkg returned an error code (1)
oh no! something went wrong during the install...
contact support@npmjs.com and we can help get you up and running

This is because Upstart has been replaced with systemd. Try manually starting the daemons to workaround this:

$ sudo systemctl start replicated replicated-ui replicated-updater

As long as the docker, replicated, replicated-ui, and replicated-updater daemons are running after installation, you should be good to go. Verify this as follows:

$ sudo ps aux | grep -e docker -e replicated
root      4354  1.5  1.1 495888 90560 ?        Ssl  16:40   6:57 /usr/bin/replicated -d
root      4363  0.0  0.1 115824 12924 ?        Ssl  16:40   0:11 /usr/bin/replicated-ui -d
root      4371  0.0  0.1 107200  7864 ?        Ssl  16:40   0:00 /usr/bin/replicated-updater -d
root      6512  1.2  0.6 1579584 50292 ?       Ssl  16:54   5:28 /usr/bin/docker daemon -H fd://