Will meteor warning prevent deployment from success?

[ycswaves]

Hi @arunoda, thx for another great Meteor tool! However, I have problem deploying my Meteor project. I failed at the stage of Invoking deployment and here is error message returned by mup logs -n 400

Meteor._wrapAsync has been renamed to Meteor.wrapAsync
 >> stepping down to gid: meteoruser
 >> stepping down to uid: meteor user

I guess it's because of one of the package I use still using the old code, but I want to know if this is the reason that my deployment fail, is there any workaround for this?

[arunoda]

No it's an issue. Try to run your app first locally. If that didn't work try to debug it: https://github.com/arunoda/meteor-up#verbose-output

On Sunday, November 16, 2014, ycswaves notifications@github.com wrote:

Hi @arunoda https://github.com/arunoda, thx for another great Meteor tool! However, I have problem deploying my Meteor project. I failed at the stage of Invoking deployment and here is error message returned by mup logs -n 400

Meteor._wrapAsync has been renamed to Meteor.wrapAsync

stepping down to gid: meteoruser stepping down to uid: meteor user

I guess it's because of one of the package I use still using the old code, but I want to know if this is the reason that my deployment fail, is there any workaround for this?

— Reply to this email directly or view it on GitHub https://github.com/arunoda/meteor-up/issues/176.

[ycswaves]

Below is the error msg from my Terminal:

-----------------------------------STDERR-----------------------------------
      '-I',
    gyp info spawn args   '/opt/yihome/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt/build/config.gypi',
    gyp info spawn args   '-I',
    gyp info spawn args   '/usr/share/node-gyp/addon.gypi',
    gyp info spawn args   '-I',
    gyp info spawn args   '/usr/include/nodejs/common.gypi',
    gyp info spawn args   '-Dlibrary=shared_library',
    gyp info spawn args   '-Dvisibility=default',
    gyp info spawn args   '-Dnode_root_dir=/usr/include/nodejs',
    gyp info spawn args   '-Dmodule_root_dir=/opt/yihome/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt',
    gyp info spawn args   '--depth=.',
    gyp info spawn args   '--generator-output',
    gyp info spawn args   'build',
    gyp info spawn args   '-Goutput_dir=.' ]
    gyp info spawn make
    gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
    gyp info ok 
    npm WARN package.json meteor-dev-bundle@0.0.0 No description
    npm WARN package.json meteor-dev-bundle@0.0.0 No repository field.
    npm WARN package.json meteor-dev-bundle@0.0.0 No README data
    -----------------------------------STDOUT-----------------------------------
    tory `/opt/yihome/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt/build'
      CXX(target) Release/obj.target/bcrypt_lib/src/blowfish.o
      CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt.o
      CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt_node.o
      SOLINK_MODULE(target) Release/obj.target/bcrypt_lib.node
      SOLINK_MODULE(target) Release/obj.target/bcrypt_lib.node: Finished
      COPY Release/bcrypt_lib.node
    make: Leaving directory `/opt/yihome/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt/build'

    > fibers@1.0.1 install /opt/yihome/tmp/bundle/programs/server/node_modules/fibers
    > node ./build.js

    `linux-x64-v8-3.14` exists; testing
    Binary is fine; exiting
    underscore@1.5.2 node_modules/underscore

    semver@2.2.1 node_modules/semver

    source-map-support@0.2.5 node_modules/source-map-support
    └── source-map@0.1.29 (amdefine@0.1.0)

    fibers@1.0.1 node_modules/fibers
    yihome stop/waiting
    yihome start/running, process 3392
    Waiting for MongoDB to initialize. (5 minutes)
    ----------------------------------------------------------------------------

From the last line, it seems MongoDB fail to initialise? Here's my environment config:

"env": {
    "PORT": 80,
    "ROOT_URL": "http://yiho.me",
    "MONGO_URL": "mongodb://localhost:27017/yihome"
  }

And when I ssh to my EC2 and do mongo yihome, I can see my collections with some pre populated data already there, so the MongoDB is already running right?

[ycswaves]

Solved eventually. I noticed that my node version on EC2(Ubuntu 14.02) is 0.10.25, and then I upgraded to 0.10.33, nom to 1.4.3 and then I install a few npm packages, that Meteor-up reported missing, manually on my EC2 and now it's up and running

[semikolon]

This is maybe the same problem as https://github.com/arunoda/meteor-up/issues/201 which is unsolved - except for if you update nodejs manually?

[ycswaves]

Hi, @semikolon , i don't think it's the same problem. In my case, i haven't update to meteor 1.0 yet and i believe it's because of i messed up with my EC2 environment.

[jamesgibson14]

I had to update node manually on my remote server to .33 and then `mup deploy' worked.

[arunoda]

You don't need to update it manually. Change it on the mup.json Then do mup setup and deploy again with mup deploy

[jamesgibson14]

Hi Arunoda, I did change the mup.json but for some reason it didn't work, it has in the past though. I might have been something on my remote server.

[surielmx]

Hi, I have the same problem This si my configuration: { // Server authentication info "servers": [ { "host": "ec2-x-x-x-x.us-west-1.compute.amazonaws.com", "username": "ubuntu", //"password": "password" // or pem file (ssh based authentication) "pem": "~/Downloads/pemname.pem" } ],

// 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": "0.10.33",

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

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

// Location of app (local directory) "app": "/Users/Suriel/Documents/proyectos/xxx",

// Configure environment "env": { "PORT": 80, "ROOT_URL": "http://x.x.x.x/appname", "MONGO_URL": "mongodb://localhost:27017/" },

// 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 }

-----------------------------------STDERR----------------------------------- p info spawn args '/opt/leaderboard/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt/build/config.gypi', gyp info spawn args '-I', gyp info spawn args '/usr/share/node-gyp/addon.gypi', gyp info spawn args '-I', gyp info spawn args '/usr/include/nodejs/common.gypi', gyp info spawn args '-Dlibrary=shared_library', gyp info spawn args '-Dvisibility=default', gyp info spawn args '-Dnode_root_dir=/usr/include/nodejs', gyp info spawn args '-Dmodule_root_dir=/opt/leaderboard/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt', gyp info spawn args '--depth=.', gyp info spawn args '--generator-output', gyp info spawn args 'build', gyp info spawn args '-Goutput_dir=.' ] gyp info spawn make gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ] gyp info ok npm WARN package.json meteor-dev-bundle@0.0.0 No description npm WARN package.json meteor-dev-bundle@0.0.0 No repository field. npm WARN package.json meteor-dev-bundle@0.0.0 No README data -----------------------------------STDOUT----------------------------------- npm-bcrypt/node_modules/bcrypt/build'

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

`linux-x64-v8-3.14` exists; testing
Binary is fine; exiting
ansi-regex@0.2.1 node_modules/ansi-regex

ansi-styles@1.1.0 node_modules/ansi-styles

chalk@0.5.1 node_modules/chalk

escape-string-regexp@1.0.3 node_modules/escape-string-regexp

strip-ansi@0.3.0 node_modules/strip-ansi

supports-color@0.2.0 node_modules/supports-color

has-ansi@0.1.0 node_modules/has-ansi

eachline@2.3.3 node_modules/eachline

type-of@2.0.1 node_modules/type-of

amdefine@1.0.0 node_modules/amdefine

asap@2.0.3 node_modules/asap

underscore@1.5.2 node_modules/underscore

meteor-promise@0.5.0 node_modules/meteor-promise

promise@7.0.4 node_modules/promise

source-map-support@0.3.2 node_modules/source-map-support

semver@4.1.0 node_modules/semver

source-map@0.1.32 node_modules/source-map

fibers@1.0.5 node_modules/fibers
Waiting for MongoDB to initialize. (5 minutes)
----------------------------------------------------------------------------

how can fix it?

[MasterJames]

Try updating everything like meteor to 1.2 (which I suspect you did) and use node 0.10.40 which is the one compatible with meteor or 1.2.

[surielmx]

I could finally. Some reasons is because I created a new instance on aws, so the deploy was from scratch, updated node to 0.10.40 on mup.json. Thank you.