arunoda / meteor-up-legacy

Production Quality Meteor Deployments
MIT License
2.26k stars 394 forks source link

mup deploy fail. #721

Open ghost opened 9 years ago

ghost commented 9 years ago

I have update to the latest meteor version. I have successfully run mup setup on a new ubuntun 14.04 server on digital ocean.

This is the error I am getting after mup deploy

x Invoking deployment process: FAILED

-----------------------------------STDERR-----------------------------------
ejs/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--release"
gyp ERR! cwd /opt/meteor/tmp/bundle/programs/server/node_modules/fibers
gyp ERR! node -v v4.2.1
gyp ERR! node-gyp -v v3.0.3
gyp ERR! not ok 
Build failed
npm ERR! Linux 3.13.0-57-generic
npm ERR! argv "/opt/nodejs/bin/node" "/usr/bin/npm" "install"
npm ERR! node v4.2.1
npm ERR! npm  v2.14.7
npm ERR! code ELIFECYCLE

npm ERR! fibers@1.0.5 install: `node ./build.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the fibers@1.0.5 install script 'node ./build.js'.
npm ERR! This is most likely a problem with the fibers package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node ./build.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls fibers
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /opt/meteor/tmp/bundle/programs/server/npm-debug.log
-----------------------------------STDOUT-----------------------------------
 > ./bcrypt: npm install due to binary npm modules
bindings@1.0.0 node_modules/bindings

nodeunit@0.9.1 node_modules/nodeunit
└── tap@0.7.1 (inherits@2.0.1, buffer-equal@0.0.1, slide@1.1.6, deep-equal@1.0.1, yamlish@0.0.7, nopt@3.0.4, difflet@0.2.6, glob@4.5.3, mkdirp@0.5.1, runforcover@0.0.2)

> fibers@1.0.5 install /opt/meteor/tmp/bundle/programs/server/node_modules/fibers
> node ./build.js

make: Entering directory `/opt/meteor/tmp/bundle/programs/server/node_modules/fibers/build'

this is my mup.json

{ // Server authentication info "servers": [ { "host": "**", "username": "root", "password": "******" // or pem file (ssh based authentication) //"pem": "~/.ssh/id_rsa" } ],

// Install MongoDB in the server, does not destroy local MongoDB on future setup "setupMongo": true,

// WARNING: Node.js is required! Only skip if you already have Node.js installed on server. "setupNode": true,

// WARNING: If nodeVersion omitted will setup 0.10.36 by default. Do not use v, only version number. "nodeVersion": "4.2.1",

// Install PhantomJS in the server "setupPhantom": true,

// Show a progress bar during the upload of the bundle to the server. // Might cause an error in some rare cases if set to true, for instance in Shippable CI "enableUploadProgressBar": true,

// Application name (No spaces) "appName": "meteor",

// Location of app (local directory) "app": "../neutrl-vodka",

// Configure environment "env": { "ROOT_URL": "http://myapp.com" },

// Meteor Up checks if the app comes online just after the deployment // before mup checks that, it will wait for no. of seconds configured below "deployCheckWaitTime": 15 }

this is what i get for mup logs -f

[45.55.138.144] tail: [45.55.138.144] cannot open ‘/var/log/upstart/meteor.log’ for reading[45.55.138.144] : No such file or directory[45.55.138.144]

MasterJames commented 9 years ago

First off I think that it's 0.10.40 that's the best version of nodejs to work with meteor 1.2.? . But I would try the development branch mupx because it looks like a build compatibility issue and mupx using docker so it's more universally compatible.

Also noting the error says this is where to learn more... /opt/meteor/tmp/bundle/programs/server/npm-debug.log Being an npm issue updating it and the other stuff might also help 'npm update'.