Cannot deploy to Galaxy

help
1

Hello, forum.

I was trying to deploy the app to Galaxy, but got following logs:

2017-02-14 17:12:48+02:00Building version 61.
v061
2017-02-14 17:12:48+02:00Step 1 : FROM meteor/galaxy-app@sha256:399572dee64f909fff88db6ea9aafbf13b1070a708f345b53bbbfa21bbfb5b5b
v061
2017-02-14 17:12:48+02:00 —> 7fc7aff21a31
v061
2017-02-14 17:12:48+02:00Step 2 : RUN /bin/bash -x /app/setup.sh https://eu-west-1-galaxy-bundles.s3-eu-west-1.amazonaws.com/bundles/XeuvvxTqHYhGkNjej/20170214-151055/bundle.k78c5y9WgzTWQ3Hve.tgz?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJ73MF4INKDN2D76A%2F20170214%2Feu-west-1%2Fs3%2Faws4_request&X-Amz-Date=20170214T151248Z&X-Amz-Expires=900&X-Amz-SignedHeaders=host&X-Amz-Signature=5212d09e186528ff592a51b2509e03abc46cbbef2a870d283a2a293ee412e782
v061
2017-02-14 17:12:48+02:00 —> [Warning] Your kernel does not support swap limit capabilities, memory limited without swap.
v061
2017-02-14 17:12:48+02:00 —> Running in 84c58dead2e1
v061
2017-02-14 17:12:49+02:00+ set -ex
v061
2017-02-14 17:12:49+02:00+ cd /app
v061
2017-02-14 17:12:49+02:00+ curl -sS 'https://eu-west-1-galaxy-bundles.s3-eu-west-1.amazonaws.com/bundles/XeuvvxTqHYhGkNjej/20170214-151055/bundle.k78c5y9WgzTWQ3Hve.tgz?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJ73MF4INKDN2D76A%2F20170214%2Feu-west-1%2Fs3%2Faws4_request&X-Amz-Date=20170214T151248Z&X-Amz-Expires=900&X-Amz-SignedHeaders=host&X-Amz-Signature=5212d09e186528ff592a51b2509e03abc46cbbef2a870d283a2a293ee412e782’
v061
2017-02-14 17:12:49+02:00+ tar xz -m
v061
2017-02-14 17:12:50+02:00+ cd /app/bundle
v061
2017-02-14 17:12:50+02:00+ export NODE_VERSION
v061
2017-02-14 17:12:50+02:00++ /app/select_node_version.sh
v061
2017-02-14 17:12:50+02:00+ NODE_VERSION=4.6.1
v061
2017-02-14 17:12:50+02:00+ /app/install_node.sh
v061
2017-02-14 17:12:50+02:00node version 4.6.1 already installed.
v061
2017-02-14 17:12:50+02:00+ export PATH=/node-v4.6.1-linux-x64/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
v061
2017-02-14 17:12:50+02:00+ PATH=/node-v4.6.1-linux-x64/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
v061
2017-02-14 17:12:50+02:00+ npm -g install npm@latest
v061
2017-02-14 17:12:57+02:00/node-v4.6.1-linux-x64/bin/npm -> /node-v4.6.1-linux-x64/lib/node_modules/npm/bin/npm-cli.js
v061
2017-02-14 17:12:58+02:00npm@4.2.0 /node-v4.6.1-linux-x64/lib/node_modules/npm
v061
2017-02-14 17:12:58+02:00+ pushd programs/server
v061
2017-02-14 17:12:58+02:00+ npm install --unsafe-perm
v061
2017-02-14 17:12:58+02:00/app/bundle/programs/server /app/bundle
v061
2017-02-14 17:13:01+02:00
v061
2017-02-14 17:13:01+02:00> fibers@1.0.15 install /app/bundle/programs/server/node_modules/fibers
v061
2017-02-14 17:13:01+02:00> node build.js || nodejs build.js
v061
2017-02-14 17:13:01+02:00
v061
2017-02-14 17:13:01+02:00linux-x64-46 exists; testing
v061
2017-02-14 17:13:01+02:00Binary is fine; exiting
v061
2017-02-14 17:13:01+02:00
v061
2017-02-14 17:13:01+02:00> meteor-dev-bundle@0.0.0 install /app/bundle/programs/server
v061
2017-02-14 17:13:01+02:00> node npm-rebuild.js
v061
2017-02-14 17:13:01+02:00
v061
2017-02-14 17:13:03+02:00
v061
2017-02-14 17:13:03+02:00> bcrypt@1.0.2 install /app/bundle/programs/server/npm/node_modules/bcrypt
v061
2017-02-14 17:13:03+02:00> node-pre-gyp install --fallback-to-build
v061
2017-02-14 17:13:03+02:00
v061
2017-02-14 17:13:03+02:00sh: 1: node-pre-gyp: not found
v061
2017-02-14 17:13:03+02:00
v061
2017-02-14 17:13:03+02:00npm ERR! Linux 4.4.0-57-generic
v061
2017-02-14 17:13:03+02:00npm ERR! argv “/node-v4.6.1-linux-x64/bin/node” “/node-v4.6.1-linux-x64/bin/npm” “rebuild” “–no-bin-links” "–update-binary"
v061
2017-02-14 17:13:03+02:00npm ERR! node v4.6.1
v061
2017-02-14 17:13:03+02:00npm ERR! npm v4.2.0
v061
2017-02-14 17:13:03+02:00npm ERR! file sh
v061
2017-02-14 17:13:03+02:00npm ERR! code ELIFECYCLE
v061
2017-02-14 17:13:03+02:00npm ERR! errno ENOENT
v061
2017-02-14 17:13:03+02:00npm ERR! syscall spawn
v061
2017-02-14 17:13:03+02:00npm ERR! bcrypt@1.0.2 install: node-pre-gyp install --fallback-to-build
v061
2017-02-14 17:13:03+02:00npm ERR! spawn ENOENT
v061
2017-02-14 17:13:03+02:00npm ERR!
v061
2017-02-14 17:13:03+02:00npm ERR! Failed at the bcrypt@1.0.2 install script ‘node-pre-gyp install --fallback-to-build’.
v061
2017-02-14 17:13:03+02:00npm ERR! Make sure you have the latest version of node.js and npm installed.
v061
2017-02-14 17:13:03+02:00npm ERR! If you do, this is most likely a problem with the bcrypt package,
v061
2017-02-14 17:13:03+02:00npm ERR! not with npm itself.
v061
2017-02-14 17:13:03+02:00npm ERR! Tell the author that this fails on your system:
v061
2017-02-14 17:13:03+02:00npm ERR! node-pre-gyp install --fallback-to-build
v061
2017-02-14 17:13:03+02:00npm ERR! You can get information on how to open an issue for this project with:
v061
2017-02-14 17:13:03+02:00npm ERR! npm bugs bcrypt
v061
2017-02-14 17:13:03+02:00npm ERR! Or if that isn’t available, you can get their info via:
v061
2017-02-14 17:13:03+02:00npm ERR! npm owner ls bcrypt
v061
2017-02-14 17:13:03+02:00npm ERR! There is likely additional logging output above.
v061
2017-02-14 17:13:03+02:00
v061
2017-02-14 17:13:03+02:00npm ERR! Please include the following file with any support request:
v061
2017-02-14 17:13:03+02:00npm ERR! /root/.npm/_logs/2017-02-14T15_13_03_665Z-debug.log
v061
2017-02-14 17:13:03+02:00
v061
2017-02-14 17:13:03+02:00npm WARN meteor-dev-bundle@0.0.0 No description
v061
2017-02-14 17:13:03+02:00npm WARN meteor-dev-bundle@0.0.0 No repository field.
v061
2017-02-14 17:13:03+02:00npm WARN meteor-dev-bundle@0.0.0 No license field.
v061
2017-02-14 17:13:03+02:00npm ERR! Linux 4.4.0-57-generic
v061
2017-02-14 17:13:03+02:00npm ERR! argv “/node-v4.6.1-linux-x64/bin/node” “/node-v4.6.1-linux-x64/bin/npm” “install” "–unsafe-perm"
v061
2017-02-14 17:13:03+02:00npm ERR! node v4.6.1
v061
2017-02-14 17:13:03+02:00npm ERR! npm v4.2.0
v061
2017-02-14 17:13:03+02:00npm ERR! code ELIFECYCLE
v061
2017-02-14 17:13:03+02:00npm ERR! errno 1
v061
2017-02-14 17:13:03+02:00npm ERR! meteor-dev-bundle@0.0.0 install: node npm-rebuild.js
v061
2017-02-14 17:13:03+02:00npm ERR! Exit status 1
v061
2017-02-14 17:13:03+02:00npm ERR!
v061
2017-02-14 17:13:03+02:00npm ERR! Failed at the meteor-dev-bundle@0.0.0 install script ‘node npm-rebuild.js’.
v061
2017-02-14 17:13:03+02:00npm ERR! Make sure you have the latest version of node.js and npm installed.
v061
2017-02-14 17:13:03+02:00npm ERR! If you do, this is most likely a problem with the meteor-dev-bundle package,
v061
2017-02-14 17:13:03+02:00npm ERR! not with npm itself.
v061
2017-02-14 17:13:03+02:00npm ERR! Tell the author that this fails on your system:
v061
2017-02-14 17:13:03+02:00npm ERR! node npm-rebuild.js
v061
2017-02-14 17:13:03+02:00npm ERR! You can get information on how to open an issue for this project with:
v061
2017-02-14 17:13:03+02:00npm ERR! npm bugs meteor-dev-bundle
v061
2017-02-14 17:13:03+02:00npm ERR! Or if that isn’t available, you can get their info via:
v061
2017-02-14 17:13:03+02:00npm ERR! npm owner ls meteor-dev-bundle
v061
2017-02-14 17:13:03+02:00npm ERR! There is likely additional logging output above.
v061
2017-02-14 17:13:03+02:00
v061
2017-02-14 17:13:03+02:00npm ERR! Please include the following file with any support request:
v061
2017-02-14 17:13:03+02:00npm ERR! /root/.npm/_logs/2017-02-14T15_13_03_735Z-debug.log
v061
2017-02-14 17:13:04+02:00Removing intermediate container 84c58dead2e1
v061
2017-02-14 17:13:04+02:00Failed to build version 61. Maximum retries reached.

On a local computer that works fine.

2

I’m having the same issue after adding bcrypt@1.0.2… any luck fixing it?

3

This solution worked for me.

Thanks for writing in. I believe you’re being affected by the issue linked below:

https://github.com/meteor/meteor/issues/8136

As stated there, there is a workaround: you should be able to use the command

meteor npm install --save bcrypt@0.8.7

This should resolve the issue with no loss of functionality. Please try doing this, and let us know the outcome.