Meteor Up deploy failure

I’m trying to deploy to my droplet on Digital Ocean. I have setup the droplet without issues, and have gone on to the deployment stage. When deploying, the final stage fails, and I don’t have the experience or knowledge to figure this out myself.

Here’s the output in full:

Started TaskList: Deploy app 'csgopilot' (linux)
[46.101.226.82] - Uploading bundle
[46.101.226.82] - Uploading bundle: SUCCESS
[46.101.226.82] - Setting up Environment Variables
[46.101.226.82] - Setting up Environment Variables: SUCCESS
[46.101.226.82] - Invoking deployment process
[46.101.226.82] x Invoking deployment process: FAILED

    -----------------------------------STDERR-----------------------------------
    e_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--release"
    gyp ERR! cwd /opt/csgopilot/tmp/bundle/programs/server/node_modules/fibers
    gyp ERR! node -v v4.1.0
    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 "/usr/local/bin/node" "/usr/local/bin/npm" "install"
    npm ERR! node v4.1.0
    npm ERR! npm  v2.14.3
    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/csgopilot/tmp/bundle/programs/server/npm-debug.log
    -----------------------------------STDOUT-----------------------------------
    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, mkdirp@0.5.1, difflet@0.2.6, glob@4.5.3, runforcover@0.0.2)
    make: Entering directory `/opt/csgopilot/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
    make: Leaving directory `/opt/csgopilot/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt/build'

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

    make: Entering directory `/opt/csgopilot/tmp/bundle/programs/server/node_modules/fibers/build'
      CXX(target) Release/obj.target/fibers/src/fibers.o
    make: Leaving directory `/opt/csgopilot/tmp/bundle/programs/server/node_modules/fibers/build'
    ----------------------------------------------------------------------------

here’s my config with a few placeholders ->

{
// Server authentication info
"servers": [
{
  "host": "<HOSTADDRESS>",
  "username": "<USERNAME>",
  //"password": "pwd"
  // 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": "0.10.40",

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

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

// Configure environment
"env": {
"ROOT_URL": "http://<URL>"
},

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

any ideas? :sunny:

try “deployCheckWaitTime”: 90

unfortunately didn’t change anything :confused:

and why not mupx (new npm install) instead of mup? but with the same mup.json config

figured mup was more reliable than mupx… might try it tonight

From my testing mupx is indeed much more stable and easier. Lots of fixes on that are very useful compared to mup.

1 Like