Failed to Build on Galaxy, doesn't say why...?


#1

Seriously not sure why this is happening. My app is loading fine on local, I go to deploy on Galaxy and it fails. I’m not sure how to go about fixing as the errors aren’t really helping me. I also don’t know how to find the file it mentions that reads the logs out I guess in a more verbose way. ANY help appreciated!

0060
2017-11-20 13:00:45-06:00Building version 60.
v0060
2017-11-20 13:00:45-06:00Step 1 : FROM meteor/galaxy-app@sha256:9fcf0b2ee698661a326b089f391e703b03eace088af33358cc23145573a0f10f
v0060
2017-11-20 13:00:45-06:00 ---> 0cce728e18a4
v0060
2017-11-20 13:00:45-06:00Step 2 : RUN /bin/bash -x /app/setup.sh https://prod-galaxy-bundles.s3.amazonaws.com/bundles/eZFQ7Xz8FQnhYELH7/20171120-185821/bundle.qfXKmhwYjvs778Wb2.tgz?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=XXXXXXXXXX%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20171120T190045Z&X-Amz-Expires=900&X-Amz-SignedHeaders=host&X-Amz-Signature=xXXXXXXXXXXXXX
v0060
2017-11-20 13:00:45-06:00 ---> [Warning] Your kernel does not support swap limit capabilities, memory limited without swap.
v0060
2017-11-20 13:00:45-06:00 ---> Running in 4d0a571ac4a6
v0060
2017-11-20 13:00:45-06:00+ set -ex
v0060
2017-11-20 13:00:45-06:00+ cd /app
v0060
2017-11-20 13:00:45-06:00+ tar xz -m
v0060
2017-11-20 13:00:45-06:00+ curl -sS 'https://prod-galaxy-bundles.s3.amazonaws.com/bundles/eZFQ7Xz8FQnhYELH7/20171120-185821/bundle.qfXKmhwYjvs778Wb2.tgz?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=XXXXXXXXXXXXX%2F20171120%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20171120T190045Z&X-Amz-Expires=900&X-Amz-SignedHeaders=host&X-Amz-Signature=XXXXXXXXXXXXXX'
v0060
2017-11-20 13:00:48-06:00+ cd /app/bundle
v0060
2017-11-20 13:00:48-06:00+ export NODE_VERSION
v0060
2017-11-20 13:00:48-06:00++ /app/select_node_version.sh
v0060
2017-11-20 13:00:48-06:00+ NODE_VERSION=4.8.6
v0060
2017-11-20 13:00:48-06:00+ /app/install_node.sh
v0060
2017-11-20 13:00:48-06:00Installing node version 4.8.6 to /node-v4.8.6-linux-x64
v0060
2017-11-20 13:00:48-06:00+ curl -sSLO https://nodejs.org/dist/v4.8.6/node-v4.8.6-linux-x64.tar.gz
v0060
2017-11-20 13:00:48-06:00+ tar -xzf node-v4.8.6-linux-x64.tar.gz -C /
v0060
2017-11-20 13:00:49-06:00+ rm node-v4.8.6-linux-x64.tar.gz
v0060
2017-11-20 13:00:49-06:00+ export PATH=/node-v4.8.6-linux-x64/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
v0060
2017-11-20 13:00:49-06:00+ PATH=/node-v4.8.6-linux-x64/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
v0060
2017-11-20 13:00:49-06:00++ /app/select_npm_version.sh
v0060
2017-11-20 13:00:49-06:00+ npm_version=4.6.1
v0060
2017-11-20 13:00:49-06:00+ npm -g install npm@4.6.1
v0060
2017-11-20 13:00:56-06:00/node-v4.8.6-linux-x64/bin/npm -> /node-v4.8.6-linux-x64/lib/node_modules/npm/bin/npm-cli.js
v0060
2017-11-20 13:00:57-06:00npm@4.6.1 /node-v4.8.6-linux-x64/lib/node_modules/npm
v0060
2017-11-20 13:00:57-06:00+ pushd programs/server
v0060
2017-11-20 13:00:57-06:00/app/bundle/programs/server /app/bundle
v0060
2017-11-20 13:00:57-06:00+ npm install --unsafe-perm
v0060
2017-11-20 13:01:00-06:00
v0060
2017-11-20 13:01:00-06:00> fibers@1.0.15 install /app/bundle/programs/server/node_modules/fibers
v0060
2017-11-20 13:01:00-06:00> node build.js || nodejs build.js
v0060
2017-11-20 13:01:00-06:00
v0060
2017-11-20 13:01:00-06:00`linux-x64-46` exists; testing
v0060
2017-11-20 13:01:01-06:00Binary is fine; exiting
v0060
2017-11-20 13:01:01-06:00
v0060
2017-11-20 13:01:01-06:00> meteor-dev-bundle@0.0.0 install /app/bundle/programs/server
v0060
2017-11-20 13:01:01-06:00> node npm-rebuild.js
v0060
2017-11-20 13:01:01-06:00
v0060
2017-11-20 13:01:03-06:00
v0060
2017-11-20 13:01:03-06:00> bcrypt@1.0.3 install /app/bundle/programs/server/npm/node_modules/bcrypt
v0060
2017-11-20 13:01:03-06:00> node-pre-gyp install --fallback-to-build
v0060
2017-11-20 13:01:03-06:00
v0060
2017-11-20 13:01:03-06:00[bcrypt] Success: "/app/bundle/programs/server/npm/node_modules/bcrypt/lib/binding/bcrypt_lib.node" is installed via remote
v0060
2017-11-20 13:01:04-06:00
v0060
2017-11-20 13:01:04-06:00> fibers@2.0.0 install /app/bundle/programs/server/npm/node_modules/fibers
v0060
2017-11-20 13:01:04-06:00> node build.js || nodejs build.js
v0060
2017-11-20 13:01:04-06:00
v0060
2017-11-20 13:01:06-06:00make: Entering directory `/app/bundle/programs/server/npm/node_modules/fibers/build'
v0060
2017-11-20 13:01:06-06:00 CXX(target) Release/obj.target/fibers/src/fibers.o
v0060
2017-11-20 13:01:06-06:00 CXX(target) Release/obj.target/fibers/src/coroutine.o
v0060
2017-11-20 13:01:07-06:00 CC(target) Release/obj.target/fibers/src/libcoro/coro.o
v0060
2017-11-20 13:01:07-06:00 SOLINK_MODULE(target) Release/obj.target/fibers.node
v0060
2017-11-20 13:01:07-06:00 COPY Release/fibers.node
v0060
2017-11-20 13:01:07-06:00make: Leaving directory `/app/bundle/programs/server/npm/node_modules/fibers/build'
v0060
2017-11-20 13:01:07-06:00Installed in `/app/bundle/programs/server/npm/node_modules/fibers/bin/linux-x64-46/fibers.node`
v0060
2017-11-20 13:01:08-06:00npm ERR! Invalid version: "https://registry.npmjs.org/balanced-match/-/balanced-match-0.4.2.tgz"
v0060
2017-11-20 13:01:08-06:00
v0060
2017-11-20 13:01:08-06:00npm ERR! A complete log of this run can be found in:
v0060
2017-11-20 13:01:08-06:00npm ERR! /root/.npm/_logs/2017-11-20T19_01_08_019Z-debug.log
v0060
2017-11-20 13:01:08-06:00npm WARN meteor-dev-bundle@0.0.0 No description
v0060
2017-11-20 13:01:08-06:00npm WARN meteor-dev-bundle@0.0.0 No repository field.
v0060
2017-11-20 13:01:08-06:00npm WARN meteor-dev-bundle@0.0.0 No license field.
v0060
2017-11-20 13:01:08-06:00npm ERR! code ELIFECYCLE
v0060
2017-11-20 13:01:08-06:00npm ERR! errno 1
v0060
2017-11-20 13:01:08-06:00npm ERR! meteor-dev-bundle@0.0.0 install: `node npm-rebuild.js`
v0060
2017-11-20 13:01:08-06:00npm ERR! Exit status 1
v0060
2017-11-20 13:01:08-06:00npm ERR!
v0060
2017-11-20 13:01:08-06:00npm ERR! Failed at the meteor-dev-bundle@0.0.0 install script.
v0060
2017-11-20 13:01:08-06:00npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
v0060
2017-11-20 13:01:08-06:00
v0060
2017-11-20 13:01:08-06:00npm ERR! A complete log of this run can be found in:
v0060
2017-11-20 13:01:08-06:00npm ERR! /root/.npm/_logs/2017-11-20T19_01_08_058Z-debug.log
v0060
2017-11-20 13:01:09-06:00Removing intermediate container 4d0a571ac4a6
v0060
2017-11-20 13:01:09-06:00Failed to build version 60. Maximum retries reached.

#2

I’ve seen this before, and I’m not 100% sure how I resolved it. For some reason, deleting my local node_modules folder and running meteor npm install to rebuild it comes to mind.


#3

So simple yet so effective! Thank you so much! @vigorwebsolutions