Galaxy builds failing - `node-pre-gyp`


#1

Anyone else having this issue? It’s bombing out at the node-pre-gyp step. I did a local build from scratch and it worked just fine.

I emailed support, but I don’t know how quick the turnaround on this will be.

2016-08-02 16:32:07-07:00+ su meteor -c 'PATH='\''/node-v4.4.7-linux-x64/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin'\'' npm install'
build
2016-08-02 16:32:07-07:00+ pushd programs/server
build
2016-08-02 16:32:07-07:00/app/bundle/programs/server /app/bundle
build
2016-08-02 16:32:17-07:00> node build.js || nodejs build.js
build
2016-08-02 16:32:17-07:00> fibers@1.0.13 install /app/bundle/programs/server/node_modules/fibers
build
2016-08-02 16:32:17-07:00
build
2016-08-02 16:32:17-07:00
build
2016-08-02 16:32:17-07:00`linux-x64-v8-4.5` exists; testing
build
2016-08-02 16:32:17-07:00Binary is fine; exiting
build
2016-08-02 16:32:17-07:00
build
2016-08-02 16:32:17-07:00> meteor-dev-bundle@0.0.0 install /app/bundle/programs/server
build
2016-08-02 16:32:17-07:00> node npm-rebuild.js
build
2016-08-02 16:32:17-07:00
build
2016-08-02 16:32:19-07:00
build
2016-08-02 16:32:19-07:00
build
2016-08-02 16:32:19-07:00> bcrypt@0.8.7 install /app/bundle/programs/server/npm/node_modules/meteor/npm-bcrypt/node_modules/bcrypt
build
2016-08-02 16:32:19-07:00> node-gyp rebuild
build
2016-08-02 16:32:23-07:00make: Entering directory `/app/bundle/programs/server/npm/node_modules/meteor/npm-bcrypt/node_modules/bcrypt/build'
build
2016-08-02 16:32:23-07:00 CXX(target) Release/obj.target/bcrypt_lib/src/blowfish.o
build
2016-08-02 16:32:24-07:00 CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt.o
build
2016-08-02 16:32:24-07:00 CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt_node.o
build
2016-08-02 16:32:28-07:00 SOLINK_MODULE(target) Release/obj.target/bcrypt_lib.node
build
2016-08-02 16:32:28-07:00 COPY Release/bcrypt_lib.node
build
2016-08-02 16:32:28-07:00make: Leaving directory `/app/bundle/programs/server/npm/node_modules/meteor/npm-bcrypt/node_modules/bcrypt/build'
build
2016-08-02 16:32:28-07:00bindings@1.2.1 /app/bundle/programs/server/npm/node_modules/meteor/npm-bcrypt/node_modules/bindings
build
2016-08-02 16:32:28-07:00bcrypt@0.8.7 /app/bundle/programs/server/npm/node_modules/meteor/npm-bcrypt/node_modules/bcrypt
build
2016-08-02 16:32:28-07:00nan@2.3.5 /app/bundle/programs/server/npm/node_modules/meteor/npm-bcrypt/node_modules/nan
build
2016-08-02 16:32:47-07:00
build
2016-08-02 16:32:47-07:00> fsevents@1.0.14 install /app/bundle/programs/server/npm/node_modules/fsevents
build
2016-08-02 16:32:47-07:00> node-pre-gyp install --fallback-to-build
build
2016-08-02 16:32:47-07:00
build
2016-08-02 16:32:47-07:00sh: 1: node-pre-gyp: not found
build
2016-08-02 16:32:47-07:00
build
2016-08-02 16:32:47-07:00npm ERR! file sh
build
2016-08-02 16:32:47-07:00npm ERR! Linux 4.4.0-28-generic
build
2016-08-02 16:32:47-07:00npm ERR! argv "/node-v4.4.7-linux-x64/bin/node" "/node-v4.4.7-linux-x64/bin/npm" "rebuild" "--no-bin-links" "--update-binary"
build
2016-08-02 16:32:47-07:00npm ERR! node v4.4.7
build
2016-08-02 16:32:47-07:00npm ERR! npm v3.10.5
build
2016-08-02 16:32:47-07:00npm ERR! code ELIFECYCLE
build
2016-08-02 16:32:47-07:00npm ERR! errno ENOENT
build
2016-08-02 16:32:47-07:00npm ERR! syscall spawn
build
2016-08-02 16:32:47-07:00npm ERR! fsevents@1.0.14 install: `node-pre-gyp install --fallback-to-build`
build
2016-08-02 16:32:47-07:00npm ERR! spawn ENOENT
build
2016-08-02 16:32:47-07:00npm ERR!
build
2016-08-02 16:32:47-07:00npm ERR! Tell the author that this fails on your system:
build
2016-08-02 16:32:47-07:00npm ERR! Failed at the fsevents@1.0.14 install script 'node-pre-gyp install --fallback-to-build'.
build
2016-08-02 16:32:47-07:00npm ERR! Make sure you have the latest version of node.js and npm installed.
build
2016-08-02 16:32:47-07:00npm ERR! If you do, this is most likely a problem with the fsevents package,
build
2016-08-02 16:32:47-07:00npm ERR! not with npm itself.
build
2016-08-02 16:32:47-07:00npm ERR! node-pre-gyp install --fallback-to-build
build
2016-08-02 16:32:47-07:00npm ERR! You can get information on how to open an issue for this project with:
build
2016-08-02 16:32:47-07:00npm ERR! npm bugs fsevents
build
2016-08-02 16:32:47-07:00npm ERR! Or if that isn't available, you can get their info via:
build
2016-08-02 16:32:47-07:00npm ERR! npm owner ls fsevents
build
2016-08-02 16:32:47-07:00npm ERR! There is likely additional logging output above.
build
2016-08-02 16:32:47-07:00
build
2016-08-02 16:32:47-07:00npm ERR! Please include the following file with any support request:
build
2016-08-02 16:32:47-07:00npm ERR! /app/bundle/programs/server/npm/npm-debug.log
build
2016-08-02 16:32:47-07:00
build
2016-08-02 16:32:47-07:00npm ERR! Linux 4.4.0-28-generic
build
2016-08-02 16:32:47-07:00npm WARN meteor-dev-bundle@0.0.0 No description
build
2016-08-02 16:32:47-07:00npm WARN meteor-dev-bundle@0.0.0 No repository field.
build
2016-08-02 16:32:47-07:00npm WARN meteor-dev-bundle@0.0.0 No license field.
build
2016-08-02 16:32:47-07:00npm ERR! argv "/node-v4.4.7-linux-x64/bin/node" "/node-v4.4.7-linux-x64/bin/npm" "install"
build
2016-08-02 16:32:47-07:00npm ERR! Exit status 1
build
2016-08-02 16:32:47-07:00npm ERR! node v4.4.7
build
2016-08-02 16:32:47-07:00npm ERR! npm v3.10.5
build
2016-08-02 16:32:47-07:00npm ERR! code ELIFECYCLE
build
2016-08-02 16:32:47-07:00npm ERR! meteor-dev-bundle@0.0.0 install: `node npm-rebuild.js`
build
2016-08-02 16:32:47-07:00npm ERR!
build
2016-08-02 16:32:47-07:00npm ERR! Failed at the meteor-dev-bundle@0.0.0 install script 'node npm-rebuild.js'.
build
2016-08-02 16:32:47-07:00npm ERR! Make sure you have the latest version of node.js and npm installed.
build
2016-08-02 16:32:47-07:00npm ERR! If you do, this is most likely a problem with the meteor-dev-bundle package,
build
2016-08-02 16:32:47-07:00npm ERR! Tell the author that this fails on your system:
build
2016-08-02 16:32:47-07:00npm ERR! not with npm itself.
build
2016-08-02 16:32:47-07:00npm ERR! There is likely additional logging output above.
build
2016-08-02 16:32:47-07:00npm ERR! node npm-rebuild.js
build
2016-08-02 16:32:47-07:00npm ERR! You can get information on how to open an issue for this project with:
build
2016-08-02 16:32:47-07:00npm ERR! npm bugs meteor-dev-bundle
build
2016-08-02 16:32:47-07:00npm ERR! Or if that isn't available, you can get their info via:
build
2016-08-02 16:32:47-07:00npm ERR! npm owner ls meteor-dev-bundle
build
2016-08-02 16:32:47-07:00
build
2016-08-02 16:32:47-07:00npm ERR! Please include the following file with any support request:
build
2016-08-02 16:32:47-07:00npm ERR! /app/bundle/programs/server/npm-debug.log
build
2016-08-02 16:32:48-07:00Removing intermediate container 3417d29b8af5

Meteor 1.4.2.3 deploy error. node-pre-gyp: not found
#3

Nope, no special scripts here. And I don’t have any special npm pre-build scripts or anything.


#5

What do you mean exactly?


#6

16 hours have passed, no response from Galaxy support. I’ve got pressure from clients, asking me why I can’t deploy, and all I can do is shrug. I understand a 24-hr turnaround time is reasonable, but maybe MDG should keep a close eye out for emails that could potentially be bugs in Galaxy, and address those ASAP?

EDIT: Ok, the 24-hr turnaround doesn’t happen till Sept 1st. However, I feel like there are two levels of support for any given SaaS:

  1. Support for the people who are confused and need help with basic stuff.
  2. One business day turnaround support for when things are broken that are expected to work. This is just going on the principle that, if a customer is paying for something, they do expect it to work. IMO bugs shouldn’t fall under the support level above, where a customer could wait 2-3 days to hear back.

UPDATE: I’m betting this is a meteor CLI tool bug (which generates the bundles). I can replicate this same issue on an EC2 instance.


#7

Did you try to build from a totally different development machine or even different platform?
Dit you run a meteor reset?

That post of @aadams is missing?


Some parts of it seem to be hosted on S3, could it be that you might include a newer version in your package file which is still available on S3? Maybe it’s some kind of a version conflict which you can override to make your app working again?

Did you run meteor npm install https://guide.meteor.com/using-npm-packages.html#installing-npm or do you have your own npm version?


#8

It’s a bug: https://github.com/meteor/meteor/issues/7568


#9

Ahh, good you found it but feel sorry for you still not being able to deploy! Hope some hot fix happens soon!


#10

Fixed!! Well, that was dumb. Somewhere along the line I must’ve done npm i --save @kadira/storybook (vs --save-dev) and so Galaxy was trying to build webpack and failing.

So, a word of caution to anyone else encountering deployment issues: always check package.json first and foremost!

In fact, it might be good for MDG to update this page:

And add something to this effect. I was totally puzzled because everything was building fine on my box, so I wasn’t even sure how to troubleshoot.