(SOLVED) Issues with Galaxy Deployment

deployment
1

Here is the code

There are no more logs to show
v001
2017-04-04 14:30:41+01:00Building version 1.
v001
2017-04-04 14:30:41+01:00Pulling base image.
v001
2017-04-04 14:30:42+01:00Step 1 :
v001
2017-04-04 14:30:42+01:00 ---> 7fc7aff21a31
v001
2017-04-04 14:30:42+01:00Step 2 : RUN /bin/bash -x /app/setup.sh https://eu-west-1-galaxy-bundles.s3-eu-west-1.amazonaws.com/bundles/srejQ9tdPW5zMEvNf/20170404-132725/bundle.6KB6FZKZHE7v8ig94.tgz?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJ73MF4INKDN2D76A%2F20170404%2Feu-west-1%2Fs3%2Faws4_request&X-Amz-Date=20170404T133041Z&X-Amz-Expires=900&X-Amz-SignedHeaders=host&X-Amz-Signature=7b550e6e213549d91251a269d37b627bb4498b7eb25fbd3ee49abbe331533ad8
v001
2017-04-04 14:30:42+01:00 ---> [Warning] Your kernel does not support swap limit capabilities, memory limited without swap.
v001
2017-04-04 14:30:42+01:00 ---> Running in 8343d60fdba8
v001
2017-04-04 14:30:43+01:00+ set -ex
v001
2017-04-04 14:30:43+01:00+ cd /app
v001
2017-04-04 14:30:43+01:00+ tar xz -m
v001
2017-04-04 14:30:43+01:00+ curl -5fbd3ee49abbe331533ad8'
v001
2017-04-04 14:30:45+01:00+ cd /app/bundle
v001
2017-04-04 14:30:45+01:00+ export NODE_VERSION
v001
2017-04-04 14:30:45+01:00++ /app/select_node_version.sh
v001
2017-04-04 14:30:45+01:00+ NODE_VERSION=4.7.3
v001
2017-04-04 14:30:45+01:00+ /app/install_node.sh
v001
2017-04-04 14:30:45+01:00Installing node version 4.7.3 to /node-v4.7.3-linux-x64
v001
2017-04-04 14:30:45+01:00+ curl -SLO https://nodejs.org/dist/v4.7.3/node-v4.7.3-linux-x64.tar.gz
v001
2017-04-04 14:30:45+01:00 % Total % Received % Xferd Average Speed Time Time Time Current
v001
2017-04-04 14:30:45+01:00 Dload Upload Total Spent Left Speed
v001
2017-04-04 14:30:46+01:00
 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
 23 11.6M 23 2735k 0 0 2666k 0 0:00:04 0:00:01 0:00:03 2669k
100 11.6M 100 11.6M 0 0 8075k 0 0:00:01 0:00:01 --:--:-- 8078k
v001
2017-04-04 14:30:46+01:00+ tar -xzf node-v4.7.3-linux-x64.tar.gz -C /
v001
2017-04-04 14:30:47+01:00+ rm node-v4.7.3-linux-x64.tar.gz
v001
2017-04-04 14:30:47+01:00+ export PATH=/node-v4.7.3-linux-x64/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
v001
2017-04-04 14:30:47+01:00+ PATH=/node-v4.7.3-linux-x64/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
v001
2017-04-04 14:30:47+01:00+ npm -g install npm@latest
v001
2017-04-04 14:30:53+01:00/node-v4.7.3-linux-x64/bin/npm -> /node-v4.7.3-linux-x64/lib/node_modules/npm/bin/npm-cli.js
v001
2017-04-04 14:30:54+01:00npm@4.4.4 /node-v4.7.3-linux-x64/lib/node_modules/npm
v001
2017-04-04 14:30:54+01:00+ pushd programs/server
v001
2017-04-04 14:30:54+01:00+ npm install --unsafe-perm
v001
2017-04-04 14:30:54+01:00/app/bundle/programs/server /app/bundle
v001
2017-04-04 14:30:57+01:00
v001
2017-04-04 14:30:57+01:00> fibers@1.0.15 install /app/bundle/programs/server/node_modules/fibers
v001
2017-04-04 14:30:57+01:00> node build.js || nodejs build.js
v001
2017-04-04 14:30:57+01:00
v001
2017-04-04 14:30:57+01:00`linux-x64-46` exists; testing
v001
2017-04-04 14:30:57+01:00Binary is fine; exiting
v001
2017-04-04 14:30:57+01:00
v001
2017-04-04 14:30:57+01:00> meteor-dev-bundle@0.0.0 install /app/bundle/programs/server
v001
2017-04-04 14:30:57+01:00> node npm-rebuild.js
v001
2017-04-04 14:30:57+01:00
v001
2017-04-04 14:30:59+01:00
v001
2017-04-04 14:30:59+01:00> bcrypt@1.0.2 install /app/bundle/programs/server/npm/node_modules/bcrypt
v001
2017-04-04 14:30:59+01:00> node-pre-gyp install --fallback-to-build
v001
2017-04-04 14:30:59+01:00
v001
2017-04-04 14:30:59+01:00sh: 1: node-pre-gyp: Permission denied
v001
2017-04-04 14:30:59+01:00npm ERR! code ELIFECYCLE
v001
2017-04-04 14:30:59+01:00npm ERR! errno 126
v001
2017-04-04 14:30:59+01:00npm ERR! bcrypt@1.0.2 install: `node-pre-gyp install --fallback-to-build`
v001
2017-04-04 14:30:59+01:00npm ERR! Exit status 126
v001
2017-04-04 14:30:59+01:00npm ERR!
v001
2017-04-04 14:30:59+01:00npm ERR! Failed at the bcrypt@1.0.2 install script 'node-pre-gyp install --fallback-to-build'.
v001
2017-04-04 14:30:59+01:00npm ERR! Make sure you have the latest version of node.js and npm installed.
v001
2017-04-04 14:30:59+01:00npm ERR! If you do, this is most likely a problem with the bcrypt package,
v001
2017-04-04 14:30:59+01:00npm ERR! not with npm itself.
v001
2017-04-04 14:30:59+01:00npm ERR! Tell the author that this fails on your system:
v001
2017-04-04 14:30:59+01:00npm ERR! node-pre-gyp install --fallback-to-build
v001
2017-04-04 14:30:59+01:00npm ERR! You can get information on how to open an issue for this project with:
v001
2017-04-04 14:30:59+01:00npm ERR! npm bugs bcrypt
v001
2017-04-04 14:30:59+01:00npm ERR! Or if that isn't available, you can get their info via:
v001
2017-04-04 14:30:59+01:00npm ERR! npm owner ls bcrypt
v001
2017-04-04 14:30:59+01:00npm ERR! There is likely additional logging output above.
v001
2017-04-04 14:30:59+01:00
v001
2017-04-04 14:30:59+01:00npm ERR! A complete log of this run can be found in:
v001
2017-04-04 14:30:59+01:00npm ERR! /root/.npm/_logs/2017-04-04T13_30_59_051Z-debug.log
v001
2017-04-04 14:30:59+01:00npm WARN meteor-dev-bundle@0.0.0 No description
v001
2017-04-04 14:30:59+01:00npm WARN meteor-dev-bundle@0.0.0 No repository field.
v001
2017-04-04 14:30:59+01:00npm WARN meteor-dev-bundle@0.0.0 No license field.
v001
2017-04-04 14:30:59+01:00npm ERR! code ELIFECYCLE
v001
2017-04-04 14:30:59+01:00npm ERR! errno 126
v001
2017-04-04 14:30:59+01:00npm ERR! meteor-dev-bundle@0.0.0 install: `node npm-rebuild.js`
v001
2017-04-04 14:30:59+01:00npm ERR! Exit status 126
v001
2017-04-04 14:30:59+01:00npm ERR!
v001
2017-04-04 14:30:59+01:00npm ERR! Failed at the meteor-dev-bundle@0.0.0 install script 'node npm-rebuild.js'.
v001
2017-04-04 14:30:59+01:00npm ERR! Make sure you have the latest version of node.js and npm installed.
v001
2017-04-04 14:30:59+01:00npm ERR! If you do, this is most likely a problem with the meteor-dev-bundle package,
v001
2017-04-04 14:30:59+01:00npm ERR! not with npm itself.
v001
2017-04-04 14:30:59+01:00npm ERR! Tell the author that this fails on your system:
v001
2017-04-04 14:30:59+01:00npm ERR! node npm-rebuild.js
v001
2017-04-04 14:30:59+01:00npm ERR! You can get information on how to open an issue for this project with:
v001
2017-04-04 14:30:59+01:00npm ERR! npm bugs meteor-dev-bundle
v001
2017-04-04 14:30:59+01:00npm ERR! Or if that isn't available, you can get their info via:
v001
2017-04-04 14:30:59+01:00npm ERR! npm owner ls meteor-dev-bundle
v001
2017-04-04 14:30:59+01:00npm ERR! There is likely additional logging output above.
v001
2017-04-04 14:30:59+01:00
v001
2017-04-04 14:30:59+01:00npm ERR! A complete log of this run can be found in:
v001
2017-04-04 14:30:59+01:00npm ERR! /root/.npm/_logs/2017-04-04T13_30_59_085Z-debug.log
v001
2017-04-04 14:30:59+01:00Removing intermediate container 8343d60fdba8
v001
2017-04-04 14:30:59+01:00Failed to build version 1. Retry scheduled at 04 Apr 17 13:30 UTC.
v001
2017-04-04 14:31:15+01:00Building version 1.
v001
2017-04-04 14:31:15+01:00Step 1 : FROM meteor/galaxy-app@sha256:399572dee64f909fff88db6ea9aafbf13b1070a708f345b53bbbfa21bbfb5b5b
v001
2017-04-04 14:31:15+01:00 ---> 7fc7aff21a31
v001
2017-04-04 14:31:15+01:00Step 2 : RUN /b3906f52429
v001
2017-04-04 14:31:15+01:00 ---> [Warning] Your kernel does not support swap limit capabilities, memory limited without swap.
v001
2017-04-04 14:31:15+01:00 ---> Running in 6e737664cd4c
v001
2017-04-04 14:31:15+01:00+ set -ex
v001
2017-04-04 14:31:15+01:00+ cd /app
v001
2017-04-04 14:31:15+01:00+ tar xz -m
v001
2017-04-04 14:31:15+01:00+ curl -sS 'Signature=8133dc923da63a9a78b3d1864248429640a438c77c55f40591bddb3906f52429'
v001
2017-04-04 14:31:17+01:00+ cd /app/bundle
v001
2017-04-04 14:31:17+01:00+ export NODE_VERSION
v001
2017-04-04 14:31:17+01:00++ /app/select_node_version.sh
v001
2017-04-04 14:31:17+01:00+ NODE_VERSION=4.7.3
v001
2017-04-04 14:31:17+01:00+ /app/install_node.sh
v001
2017-04-04 14:31:17+01:00Installing node version 4.7.3 to /node-v4.7.3-linux-x64
v001
2017-04-04 14:31:17+01:00+ curl -SLO https://nodejs.org/dist/v4.7.3/node-v4.7.3-linux-x64.tar.gz
v001
2017-04-04 14:31:17+01:00 % Total % Received % Xferd Average Speed Time Time Time Current
v001
2017-04-04 14:31:17+01:00 Dload Upload Total Spent Left Speed
v001
2017-04-04 14:31:18+01:00
 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
 0 11.6M 0 99k 0 0 158k 0 0:01:14 --:--:-- 0:01:14 158k
100 11.6M 100 11.6M 0 0 8076k 0 0:00:01 0:00:01 --:--:-- 8078k
v001
2017-04-04 14:31:18+01:00+ tar -xzf node-v4.7.3-linux-x64.tar.gz -C /
v001
2017-04-04 14:31:19+01:00+ rm node-v4.7.3-linux-x64.tar.gz
v001
2017-04-04 14:31:19+01:00+ export PATH=/node-v4.7.3-linux-x64/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
v001
2017-04-04 14:31:19+01:00+ PATH=/node-v4.7.3-linux-x64/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
v001
2017-04-04 14:31:19+01:00+ npm -g install npm@latest
v001
2017-04-04 14:31:26+01:00/node-v4.7.3-linux-x64/bin/npm -> /node-v4.7.3-linux-x64/lib/node_modules/npm/bin/npm-cli.js
v001
2017-04-04 14:31:27+01:00npm@4.4.4 /node-v4.7.3-linux-x64/lib/node_modules/npm
v001
2017-04-04 14:31:27+01:00+ pushd programs/server
v001
2017-04-04 14:31:27+01:00/app/bundle/programs/server /app/bundle
v001
2017-04-04 14:31:27+01:00+ npm install --unsafe-perm
v001
2017-04-04 14:31:30+01:00
v001
2017-04-04 14:31:30+01:00> fibers@1.0.15 install /app/bundle/programs/server/node_modules/fibers
v001
2017-04-04 14:31:30+01:00> node build.js || nodejs build.js
v001
2017-04-04 14:31:30+01:00
v001
2017-04-04 14:31:30+01:00`linux-x64-46` exists; testing
v001
2017-04-04 14:31:30+01:00Binary is fine; exiting
v001
2017-04-04 14:31:30+01:00
v001
2017-04-04 14:31:30+01:00> meteor-dev-bundle@0.0.0 install /app/bundle/programs/server
v001
2017-04-04 14:31:30+01:00> node npm-rebuild.js
v001
2017-04-04 14:31:30+01:00
v001
2017-04-04 14:31:31+01:00
v001
2017-04-04 14:31:31+01:00> bcrypt@1.0.2 install /app/bundle/programs/server/npm/node_modules/bcrypt
v001
2017-04-04 14:31:31+01:00> node-pre-gyp install --fallback-to-build
v001
2017-04-04 14:31:31+01:00
v001
2017-04-04 14:31:31+01:00sh: 1: node-pre-gyp: Permission denied
v001
2017-04-04 14:31:31+01:00npm ERR! code ELIFECYCLE
v001
2017-04-04 14:31:31+01:00npm ERR! errno 126
v001
2017-04-04 14:31:31+01:00npm ERR! bcrypt@1.0.2 install: `node-pre-gyp install --fallback-to-build`
v001
2017-04-04 14:31:31+01:00npm ERR! Exit status 126
v001
2017-04-04 14:31:31+01:00npm ERR!
v001
2017-04-04 14:31:31+01:00npm ERR! Failed at the bcrypt@1.0.2 install script 'node-pre-gyp install --fallback-to-build'.
v001
2017-04-04 14:31:31+01:00npm ERR! Make sure you have the latest version of node.js and npm installed.
v001
2017-04-04 14:31:31+01:00npm ERR! If you do, this is most likely a problem with the bcrypt package,
v001
2017-04-04 14:31:31+01:00npm ERR! not with npm itself.
v001
2017-04-04 14:31:31+01:00npm ERR! Tell the author that this fails on your system:
v001
2017-04-04 14:31:31+01:00npm ERR! node-pre-gyp install --fallback-to-build
v001
2017-04-04 14:31:31+01:00npm ERR! You can get information on how to open an issue for this project with:
v001
2017-04-04 14:31:31+01:00npm ERR! npm bugs bcrypt
v001
2017-04-04 14:31:31+01:00npm ERR! Or if that isn't available, you can get their info via:
v001
2017-04-04 14:31:31+01:00npm ERR! npm owner ls bcrypt
v001
2017-04-04 14:31:31+01:00npm ERR! There is likely additional logging output above.
v001
2017-04-04 14:31:31+01:00
v001
2017-04-04 14:31:31+01:00npm ERR! A complete log of this run can be found in:
v001
2017-04-04 14:31:31+01:00npm ERR! /root/.npm/_logs/2017-04-04T13_31_31_712Z-debug.log
v001
2017-04-04 14:31:31+01:00npm WARN meteor-dev-bundle@0.0.0 No description
v001
2017-04-04 14:31:31+01:00npm WARN meteor-dev-bundle@0.0.0 No repository field.
v001
2017-04-04 14:31:31+01:00npm WARN meteor-dev-bundle@0.0.0 No license field.
v001
2017-04-04 14:31:31+01:00npm ERR! code ELIFECYCLE
v001
2017-04-04 14:31:31+01:00npm ERR! errno 126
v001
2017-04-04 14:31:31+01:00npm ERR! meteor-dev-bundle@0.0.0 install: `node npm-rebuild.js`
v001
2017-04-04 14:31:31+01:00npm ERR! Exit status 126
v001
2017-04-04 14:31:31+01:00npm ERR!
v001
2017-04-04 14:31:31+01:00npm ERR! Failed at the meteor-dev-bundle@0.0.0 install script 'node npm-rebuild.js'.
v001
2017-04-04 14:31:31+01:00npm ERR! Make sure you have the latest version of node.js and npm installed.
v001
2017-04-04 14:31:31+01:00npm ERR! If you do, this is most likely a problem with the meteor-dev-bundle package,
v001
2017-04-04 14:31:31+01:00npm ERR! not with npm itself.
v001
2017-04-04 14:31:31+01:00npm ERR! Tell the author that this fails on your system:
v001
2017-04-04 14:31:31+01:00npm ERR! node npm-rebuild.js
v001
2017-04-04 14:31:31+01:00npm ERR! You can get information on how to open an issue for this project with:
v001
2017-04-04 14:31:31+01:00npm ERR! npm bugs meteor-dev-bundle
v001
2017-04-04 14:31:31+01:00npm ERR! Or if that isn't available, you can get their info via:
v001
2017-04-04 14:31:31+01:00npm ERR! npm owner ls meteor-dev-bundle
v001
2017-04-04 14:31:31+01:00npm ERR! There is likely additional logging output above.
v001
2017-04-04 14:31:31+01:00
v001
2017-04-04 14:31:31+01:00npm ERR! A complete log of this run can be found in:
v001
2017-04-04 14:31:31+01:00npm ERR! /root/.npm/_logs/2017-04-04T13_31_31_743Z-debug.log
v001
2017-04-04 14:31:32+01:00Removing intermediate container 6e737664cd4c
v001
2017-04-04 14:31:32+01:00Failed to build version 1. Retry scheduled at 04 Apr 17 13:31 UTC.
v001
2017-04-04 14:31:49+01:00Building version 1.
v001
2017-04-04 14:31:49+01:00Step 1 : FROM meteor/galaxy-app@sha256:399572dee64f909fff88db6ea9aafbf13b1070a708f345b53bbbfa21bbfb5b5b
v001
2017-04-04 14:31:49+01:00 ---> 7fc7aff21a31
v001
2017-04-04 14:31:49+01:00Step 2 : Signature=9765c86d86190407837ca8300eeeafbe93a384af17fe6b5e4419e82cd42ba1dc
v001
2017-04-04 14:31:49+01:00 ---> [Warning] Your kernel does not support swap limit capabilities, memory limited without swap.
v001
2017-04-04 14:31:49+01:00 ---> Running in 3e45a0daae17
v001
2017-04-04 14:31:49+01:00+ set -ex
v001
2017-04-04 14:31:49+01:00+ cd /app
v001
2017-04-04 14:31:49+01:00+ tar xz -m
v001
2017-04-04 14:31:49+01:00+ curl -sS 'https://eu-west-1-galaxy-bundles.s3-eu-west-1.amazonaws.com/bundles/srejQ9tdPW5zMEvNf/20170404-132725/bundle.6KB6FZKZHE7v8ig94.tgz?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJ73MF4INKDN2D76A%2F20170404%2Feu-west-1%2Fs3%2Faws4_request&X-Amz-Date=20170404T133149Z&X-Amz-Expires=900&X-Amz-SignedHeaders=host&X-Amz-Signature=9765c86d86190407837ca8300eeeafbe93a384af17fe6b5e4419e82cd42ba1dc'
v001
2017-04-04 14:31:51+01:00+ cd /app/bundle
v001
2017-04-04 14:31:51+01:00+ export NODE_VERSION
v001
2017-04-04 14:31:51+01:00++ /app/select_node_version.sh
v001
2017-04-04 14:31:51+01:00+ NODE_VERSION=4.7.3
v001
2017-04-04 14:31:51+01:00+ /app/install_node.sh
v001
2017-04-04 14:31:51+01:00Installing node version 4.7.3 to /node-v4.7.3-linux-x64
v001
2017-04-04 14:31:51+01:00+ curl -SLO https://nodejs.org/dist/v4.7.3/node-v4.7.3-linux-x64.tar.gz
v001
2017-04-04 14:31:51+01:00 % Total % Received % Xferd Average Speed Time Time Time Current
v001
2017-04-04 14:31:51+01:00 Dload Upload Total Spent Left Speed
v001
2017-04-04 14:31:53+01:00
 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
 3 11.6M 3 447k 0 0 555k 0 0:00:21 --:--:-- 0:00:21 554k
100 11.6M 100 11.6M 0 0 8035k 0 0:00:01 0:00:01 --:--:-- 8039k
v001
2017-04-04 14:31:53+01:00+ tar -xzf node-v4.7.3-linux-x64.tar.gz -C /
v001
2017-04-04 14:31:53+01:00+ rm node-v4.7.3-linux-x64.tar.gz
v001
2017-04-04 14:31:53+01:00+ export PATH=/node-v4.7.3-linux-x64/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
v001
2017-04-04 14:31:53+01:00+ PATH=/node-v4.7.3-linux-x64/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
v001
2017-04-04 14:31:53+01:00+ npm -g install npm@latest
v001
2017-04-04 14:32:00+01:00/node-v4.7.3-linux-x64/bin/npm -> /node-v4.7.3-linux-x64/lib/node_modules/npm/bin/npm-cli.js
v001
2017-04-04 14:32:01+01:00npm@4.4.4 /node-v4.7.3-linux-x64/lib/node_modules/npm
v001
2017-04-04 14:32:01+01:00+ pushd programs/server
v001
2017-04-04 14:32:01+01:00+ npm install --unsafe-perm
v001
2017-04-04 14:32:01+01:00/app/bundle/programs/server /app/bundle
v001
2017-04-04 14:32:04+01:00
v001
2017-04-04 14:32:04+01:00> fibers@1.0.15 install /app/bundle/programs/server/node_modules/fibers
v001
2017-04-04 14:32:04+01:00> node build.js || nodejs build.js
v001
2017-04-04 14:32:04+01:00
v001
2017-04-04 14:32:04+01:00`linux-x64-46` exists; testing
v001
2017-04-04 14:32:04+01:00Binary is fine; exiting
v001
2017-04-04 14:32:04+01:00
v001
2017-04-04 14:32:04+01:00> meteor-dev-bundle@0.0.0 install /app/bundle/programs/server
v001
2017-04-04 14:32:04+01:00> node npm-rebuild.js
v001
2017-04-04 14:32:04+01:00
v001
2017-04-04 14:32:05+01:00
v001
2017-04-04 14:32:05+01:00> bcrypt@1.0.2 install /app/bundle/programs/server/npm/node_modules/bcrypt
v001
2017-04-04 14:32:05+01:00> node-pre-gyp install --fallback-to-build
v001
2017-04-04 14:32:05+01:00
v001
2017-04-04 14:32:05+01:00sh: 1: node-pre-gyp: Permission denied
v001
2017-04-04 14:32:05+01:00npm ERR! code ELIFECYCLE
v001
2017-04-04 14:32:05+01:00npm ERR! errno 126
v001
2017-04-04 14:32:05+01:00npm ERR! bcrypt@1.0.2 install: `node-pre-gyp install --fallback-to-build`
v001
2017-04-04 14:32:05+01:00npm ERR! Exit status 126
v001
2017-04-04 14:32:05+01:00npm ERR!
v001
2017-04-04 14:32:05+01:00npm ERR! Failed at the bcrypt@1.0.2 install script 'node-pre-gyp install --fallback-to-build'.
v001
2017-04-04 14:32:05+01:00npm ERR! Make sure you have the latest version of node.js and npm installed.
v001
2017-04-04 14:32:05+01:00npm ERR! If you do, this is most likely a problem with the bcrypt package,
v001
2017-04-04 14:32:05+01:00npm ERR! not with npm itself.
v001
2017-04-04 14:32:05+01:00npm ERR! Tell the author that this fails on your system:
v001
2017-04-04 14:32:05+01:00npm ERR! node-pre-gyp install --fallback-to-build
v001
2017-04-04 14:32:05+01:00npm ERR! You can get information on how to open an issue for this project with:
v001
2017-04-04 14:32:05+01:00npm ERR! npm bugs bcrypt
v001
2017-04-04 14:32:05+01:00npm ERR! Or if that isn't available, you can get their info via:
v001
2017-04-04 14:32:05+01:00npm ERR! npm owner ls bcrypt
v001
2017-04-04 14:32:05+01:00npm ERR! There is likely additional logging output above.
v001
2017-04-04 14:32:05+01:00
v001
2017-04-04 14:32:05+01:00npm ERR! A complete log of this run can be found in:
v001
2017-04-04 14:32:05+01:00npm ERR! /root/.npm/_logs/2017-04-04T13_32_05_720Z-debug.log
v001
2017-04-04 14:32:05+01:00npm WARN meteor-dev-bundle@0.0.0 No description
v001
2017-04-04 14:32:05+01:00npm WARN meteor-dev-bundle@0.0.0 No repository field.
v001
2017-04-04 14:32:05+01:00npm WARN meteor-dev-bundle@0.0.0 No license field.
v001
2017-04-04 14:32:05+01:00npm ERR! code ELIFECYCLE
v001
2017-04-04 14:32:05+01:00npm ERR! errno 126
v001
2017-04-04 14:32:05+01:00npm ERR! meteor-dev-bundle@0.0.0 install: `node npm-rebuild.js`
v001
2017-04-04 14:32:05+01:00npm ERR! Exit status 126
v001
2017-04-04 14:32:05+01:00npm ERR!
v001
2017-04-04 14:32:05+01:00npm ERR! Failed at the meteor-dev-bundle@0.0.0 install script 'node npm-rebuild.js'.
v001
2017-04-04 14:32:05+01:00npm ERR! Make sure you have the latest version of node.js and npm installed.
v001
2017-04-04 14:32:05+01:00npm ERR! If you do, this is most likely a problem with the meteor-dev-bundle package,
v001
2017-04-04 14:32:05+01:00npm ERR! not with npm itself.
v001
2017-04-04 14:32:05+01:00npm ERR! Tell the author that this fails on your system:
v001
2017-04-04 14:32:05+01:00npm ERR! node npm-rebuild.js
v001
2017-04-04 14:32:05+01:00npm ERR! You can get information on how to open an issue for this project with:
v001
2017-04-04 14:32:05+01:00npm ERR! npm bugs meteor-dev-bundle
v001
2017-04-04 14:32:05+01:00npm ERR! Or if that isn't available, you can get their info via:
v001
2017-04-04 14:32:05+01:00npm ERR! npm owner ls meteor-dev-bundle
v001
2017-04-04 14:32:05+01:00npm ERR! There is likely additional logging output above.
v001
2017-04-04 14:32:05+01:00
v001
2017-04-04 14:32:05+01:00npm ERR! A complete log of this run can be found in:
v001
2017-04-04 14:32:05+01:00npm ERR! /root/.npm/_logs/2017-04-04T13_32_05_750Z-debug.log
v001
2017-04-04 14:32:06+01:00Removing intermediate container 3e45a0daae17
v001
2017-04-04 14:32:06+01:00Failed to build version 1. Maximum retries reached.
2

Are you deploying from a Windows computer, by chance? Also, what version of Meteor are you deploying from?

3

Fixed! I am deploying from Windows 10. Meteor version is 1.4.3.2. I was able to fix the issue by running meteor npm install --save bcrypt@0.8.7

4

Having another issue while deploying to Galaxy.

/app/bundle/programs/server/node_modules/fibers/future.js:313
79tq
2017-04-04 20:45:50+01:00	throw(ex);
79tq
2017-04-04 20:45:50+01:00	^
79tq
2017-04-04 20:45:51+01:00MongoError: authentication fail
79tq
2017-04-04 20:45:51+01:00 at Object.Future.wait (/app/bundle/programs/server/node_modules/fibers/future.js:449:15)
79tq
2017-04-04 20:45:51+01:00 at new MongoConnection (packages/mongo/mongo_driver.js:211:27)
79tq
2017-04-04 20:45:51+01:00 at [object Object]._.extend._startTailing (packages/mongo/oplog_tailing.js:200:33)
79tq
2017-04-04 20:45:51+01:00 at new OplogHandle (packages/mongo/oplog_tailing.js:76:8)
79tq
2017-04-04 20:45:51+01:00 at new MongoConnection (packages/mongo/mongo_driver.js:214:25)
79tq
2017-04-04 20:45:51+01:00 at new MongoInternals.RemoteCollectionDriver (packages/mongo/remote_collection_driver.js:4:16)
79tq
2017-04-04 20:45:51+01:00 at Object.<anonymous> (packages/mongo/remote_collection_driver.js:38:10)
79tq
2017-04-04 20:45:51+01:00 at Object.defaultRemoteCollectionDriver (packages/underscore.js:784:19)
79tq
2017-04-04 20:45:51+01:00 at new Mongo.Collection (packages/mongo/collection.js:99:40)
79tq
2017-04-04 20:45:51+01:00 at AccountsServer.AccountsCommon (packages/accounts-base/accounts_common.js:23:18)
79tq
2017-04-04 20:45:51+01:00 - - - - -
79tq
2017-04-04 20:45:51+01:00 at Function.MongoError.create (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/error.js:31:11)
79tq
2017-04-04 20:45:51+01:00 at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/topologies/replset.js:1170:38
79tq
2017-04-04 20:45:51+01:00 at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/connection/pool.js:730:7
79tq
2017-04-04 20:45:51+01:00 at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/connection/pool.js:706:20
79tq
2017-04-04 20:45:51+01:00 at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/auth/scram.js:191:18
79tq
2017-04-04 20:45:51+01:00 at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/connection/pool.js:455:18
79tq
2017-04-04 20:45:51+01:00 at nextTickCallbackWith0Args (node.js:436:9)
79tq
2017-04-04 20:45:51+01:00 at process._tickCallback (node.js:365:13)
79tq
2017-04-04 20:45:51+01:00Application exited with code: 1
79tq
2017-04-04 20:45:55+01:00The container has crashed. A new container will be started to replace it.
5

Glad that fixed it for you! For what it’s worth, if you see that node-pre-gyp: Permission denied error again, I believe I fixed that with this commit: https://github.com/meteor/meteor/commit/17a786eb36a110f7936d2d62f2558d8ef74f43c8 which would be available in Meteor 1.4.4 RC2 (release candidate).

Your new error looks a bit more straight-forward:

MongoError: authentication fail

You’ll probably want to consult the Galaxy Guide for proper settings for your MONGO_URL. Also, feel free to contact Galaxy Support through your Galaxy Dashboard!

1 Like
6

Thanks, I will do that now.

7

Fixed everything! Turns out I omitted the &authSource=admin from the Oplog URI. mLab didn’t include it either. The Galaxy Doc has it. Thanks @abernix

1 Like
8

Could you please provide the full URI that you got to work? I’m having the same issue with mLab and am going nuts.

Thanks!

-Bill

9

@fernaceman Are you getting the same exact error? What query parameters do you have on your MONGO_URL and MONGO_OPLOG_URL? (for example, authSource=admin, replicaSet=..., etc.)

10

Here’s how I got it working using the settings.json file: create a db user and an oplog user, replace as appropriate below.

"MONGO_URL": "mongodb://{username}:{password}@ds151560-a0.mlab.com:51560,ds151560-a1.mlab.com:51560/{dbname}?replicaSet=rs-ds151560",

"MONGO_OPLOG_URL": "mongodb://{oplog-user-username}:{oplog-user-password}@ds151560-a0.mlab.com:51560,ds151560-a1.mlab.com:51560/local?replicaSet=rs-ds151560&authSource=admin"

11

Do I need to create a special Oplog user to do this? Or will a standard admin user work when utilizing the MONGO_OPLOG_URL setting?

HERE IS THE EXACT ERROR I AM GETTING:

2017-06-08 14:00:05-04:00Application process starting, version 8
tj29
2017-06-08 14:00:13-04:00
tj29
2017-06-08 14:00:13-04:00/app/bundle/programs/server/node_modules/fibers/future.js:313
tj29
2017-06-08 14:00:13-04:00 throw(ex);
tj29
2017-06-08 14:00:13-04:00 ^
tj29
2017-06-08 14:00:13-04:00MongoError: authentication fail
tj29
2017-06-08 14:00:13-04:00 at Object.Future.wait (/app/bundle/programs/server/node_modules/fibers/future.js:449:15)
tj29
2017-06-08 14:00:13-04:00 at new MongoConnection (packages/mongo/mongo_driver.js:211:27)
tj29
2017-06-08 14:00:13-04:00 at new MongoInternals.RemoteCollectionDriver (packages/mongo/remote_collection_driver.js:4:16)
tj29
2017-06-08 14:00:13-04:00 at Object. (packages/mongo/remote_collection_driver.js:38:10)
tj29
2017-06-08 14:00:13-04:00 at Object.defaultRemoteCollectionDriver (packages/underscore.js:784:19)
tj29
2017-06-08 14:00:13-04:00 at new Mongo.Collection (packages/mongo/collection.js:99:40)
tj29
2017-06-08 14:00:13-04:00 at AccountsServer.AccountsCommon (packages/accounts-base/accounts_common.js:23:18)
tj29
2017-06-08 14:00:13-04:00 at new AccountsServer (packages/accounts-base/accounts_server.js:18:5)
tj29
2017-06-08 14:00:13-04:00 at meteorInstall.node_modules.meteor.accounts-base.server_main.js (packages/accounts-base/server_main.js:9:12)
tj29
2017-06-08 14:00:13-04:00 at fileEvaluate (packages/modules-runtime.js:197:9)
tj29
2017-06-08 14:00:13-04:00 - - - - -
tj29
2017-06-08 14:00:13-04:00 at Function.MongoError.create (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/error.js:31:11)
tj29
2017-06-08 14:00:13-04:00 at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/topologies/replset.js:1170:38
tj29
2017-06-08 14:00:13-04:00 at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/connection/pool.js:730:7
tj29
2017-06-08 14:00:13-04:00 at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/connection/pool.js:706:20
tj29
2017-06-08 14:00:13-04:00 at finish (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/auth/scram.js:163:16)
tj29
2017-06-08 14:00:13-04:00 at handleEnd (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/auth/scram.js:173:7)
tj29
2017-06-08 14:00:13-04:00 at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/auth/scram.js:273:11
tj29
2017-06-08 14:00:13-04:00 at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/connection/pool.js:455:18
tj29
2017-06-08 14:00:13-04:00 at nextTickCallbackWith0Args (node.js:489:9)
tj29
2017-06-08 14:00:13-04:00 at process._tickCallback (node.js:418:13)
tj29
2017-06-08 14:00:13-04:00Application exited with code: 1

Thanks.

-BIll

12

I have pasted the exact error I am getting below. It seems related to me, but I could be wrong.

13

I pasted the exact error below. I changed all the credentials to match my mLab settings, but used your solution as a template.

14

I do think mLab requires a separate user for oplog access as indicated by this document for more information and the separate differentiation made by {oplog-user-username}:{oplog-user-password} above.

If that doesn’t help, perhaps try not setting MONGO_OPLOG_URL at all (temporarily), to isolate whether the problem is with MONGO_URL or MONGO_OPLOG_URL.

15

Giving it a go now, thank you for the help. I think we’re on to something!

16

Still getting the same error. :frowning: I know it has to do with the OPLOG url…as I didn’t even have it in my settings before and was receiving the same error.

17

Just to be clear: If you didn’t have it (MONGO_OPLOG_URL) in your settings before and you were still getting the error, that would indicate that the problem is not with MONGO_OPLOG_URL but rather with MONGO_URL.

18

Interesting…I see your point.

19

Yes, you’ll have to create an OPLOG user to obtain credentials. I had this same issue with OPLOG and even after I created an oplog user, I was still experiencing the same issue. Once the database is created, you need to add two users to it: one to access the primary database, and another to access the Oplog. This is pretty straighforward. After a while, it went away. JUST MAKE SURE THE OPLOG USER is ReadOnly by ticking the checkbox. More here: https://themeteorchef.com/tutorials/setting-up-mongodb-oplog-tailing

20

That’s exactly what I had to do-I had to create a new, separate user to be able to access the proper authentication.

-Bill

1 Like