meteor up deployment failed

[prakash36cs]

Hi ,

Im facing issue when going to deploy my meteor up with AWS.

Its showing following error: $mupx setup

Meteor Up: Production Quality Meteor Deployments

Configuration file : mup.json Settings file : settings.json

“ Checkout Kadira! It's the best way to monitor performance of your app. Visit: https://kadira.io/mup ”

Started TaskList: Setup (linux) [ec2-xxxxxxxxxxxxxxxxxxxxxxxx.compute.amazonaws.com] - Installing Docker [ec2-xxxxxxxxxxxxxxxxxxxxxxxx.compute.amazonaws.com] - Installing Docker: SUCCESS [ec2-xxxxxxxxxxxxxxxxxxxxxxxx.compute.amazonaws.com] - Setting up Environment [ec2-xxxxxxxxxxxxxxxxxxxxxxxx.compute.amazonaws.com] - Setting up Environment: SUCCESS [ec2-xxxxxxxxxxxxxxxxxxxxxxxx.compute.amazonaws.com] - Copying MongoDB configuration [ec2-xxxxxxxxxxxxxxxxxxxxxxxx.compute.amazonaws.com] - Copying MongoDB configuration: SUCCESS [ec2-xxxxxxxxxxxxxxxxxxxxxxxx.compute.amazonaws.com] - Installing MongoDB [ec2-xxxxxxxxxxxxxxxxxxxxxxxx.compute.amazonaws.com] - Installing MongoDB: SUCCESS

D:\working\15march\qxmedics\myDevelopment>mupx deploy

Meteor Up: Production Quality Meteor Deployments

Configuration file : mup.json Settings file : settings.json

“ Checkout Kadira! It's the best way to monitor performance of your app. Visit: https://kadira.io/mup ”

Meteor app path : D:\working\version1 Using buildOptions : {}

Started TaskList: Deploy app 'Qxmedics' (linux) [ec2-xxxxxxxxxxxxxxxxxxxxxxxx.compute.amazonaws.com] - Uploading bundle [ec2-xxxxxxxxxxxxxxxxxxxxxxxx.compute.amazonaws.com] - Uploading bundle: SUCCESS [ec2-xxxxxxxxxxxxxxxxxxxxxxxx.compute.amazonaws.com] - Sending environment variables [ec2-xxxxxxxxxxxxxxxxxxxxxxxx.compute.amazonaws.com] - Sending environment variables: SUCCESS [ec2-xxxxxxxxxxxxxxxxxxxxxxxx.compute.amazonaws.com] - Initializing start script [ec2-xxxxxxxxxxxxxxxxxxxxxxxx.compute.amazonaws.com] - Initializing start script: SUCCESS [ec2-xxxxxxxxxxxxxxxxxxxxxxxx.compute.amazonaws.com] - Invoking deployment process [ec2-xxxxxxxxxxxxxxxxxxxxxxxx.compute.amazonaws.com] - Invoking deployment process: SUCCESS [ec2-xxxxxxxxxxxxxxxxxxxxxxxx.compute.amazonaws.com] - Verifying deployment [ec2-xxxxxxxxxxxxxxxxxxxxxxxx.compute.amazonaws.com] x Verifying deployment: FAILED

    -----------------------------------STDERR-----------------------------------
     WARN deprecated   npm -g install npm@latest
    npm WARN deprecated
    npm WARN deprecated (Depending on how Node.js was installed on your system, you
    npm WARN deprecated may need to prefix the preceding commands with `sudo`, or if
    npm WARN deprecated on Windows, run them from an Administrator prompt.)
    npm WARN deprecated
    npm WARN deprecated If you're running the version of npm bundled with
    npm WARN deprecated Node.js 0.10 LTS, be aware that the next version of 0.10 LTS
    npm WARN deprecated will be bundled with a version of npm@2, which has some small
    npm WARN deprecated backwards-incompatible changes made to `npm run-script` and
    npm WARN deprecated semver behavior.
    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

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

    => Redeploying previous version of the app

    -----------------------------------STDOUT-----------------------------------

    To see more logs type 'mup logs --tail=50'

    ----------------------------------------------------------------------------`

Please help me out

[MasterJames]

Extending the deploy wait time usually helps here in the verify phase try 120 Otherwise please post your settings file contents Mayne that will reveal something. Ubuntu 14+ is the only supported target platform. Stick to mupx not mup unless you want to try the new version at kadirahq/meteor-up Use setting node 0.10.40 and potentially update everything.

[prakash36cs]

Hi James,

I tried wait time 60, 120 and then 600 ... but its not working.

My last updated mup.json is

`{ // Server authentication info "servers": [ { "host": "ec2-XXXXXXXXXXX.us-west-2.compute.amazonaws.com", "username": "ubuntu", //"password": "password" // or pem file (ssh based authentication) "pem": "D:/Ubuntu.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.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": "abc",

// Location of app (local directory) "app": "D:/working/version1",

// Configure environment "env": { "PORT":80, "ROOT_URL": "ec2-XXXXXXXXXXXXX.us-west-2.compute.amazonaws.com", "MONGO_URL": "mongodb://localhost:27017/meteor" },

// 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": 600 } `

[MasterJames]

Are you using the latest version of meteor? Maybe some odd packages? If you SSH into the machine can you tell if there's meteor running etc. There's also an extended DEBUG=* mupx deploy command (careful with spacing) that gets extra logging info https://github.com/arunoda/meteor-up/tree/mupx#verbose-output See also https://github.com/arunoda/meteor-up/tree/mupx#check-logs

[prakash36cs]

Im using METEOR@1.3.2.4

[tomtom87]

I'm using Meteor 1.3.2.4 got the same error here

mupx deploy

Meteor Up: Production Quality Meteor Deployments
------------------------------------------------
Configuration file : mup.json
Settings file      : settings.json

Meteor app path    : /Users/tom/web/trusu
Using buildOptions : {}

Started TaskList: Deploy app 'trusu' (linux)
[119.81.157.91] - Uploading bundle
[119.81.157.91] - Uploading bundle: SUCCESS
[119.81.157.91] - Sending environment variables
[119.81.157.91] - Sending environment variables: SUCCESS
[119.81.157.91] - Initializing start script
[119.81.157.91] - Initializing start script: SUCCESS
[119.81.157.91] - Invoking deployment process
[119.81.157.91] - Invoking deployment process: SUCCESS
[119.81.157.91] - Verifying deployment
[119.81.157.91] x Verifying deployment: FAILED

    -----------------------------------STDERR-----------------------------------
      npm -g install npm@latest
    npm WARN deprecated 
    npm WARN deprecated (Depending on how Node.js was installed on your system, you
    npm WARN deprecated may need to prefix the preceding commands with `sudo`, or if
    npm WARN deprecated on Windows, run them from an Administrator prompt.)
    npm WARN deprecated 
    npm WARN deprecated If you're running the version of npm bundled with
    npm WARN deprecated Node.js 0.10 LTS, be aware that the next version of 0.10 LTS
    npm WARN deprecated will be bundled with a version of npm@2, which has some small
    npm WARN deprecated backwards-incompatible changes made to `npm run-script` and
    npm WARN deprecated semver behavior.
    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

    > fibers@1.0.8 install /bundle/bundle/programs/server/node_modules/fibers
    > node build.js || nodejs build.js

    => Redeploying previous version of the app

    -----------------------------------STDOUT-----------------------------------

    To see more logs type 'mup logs --tail=50'

    ----------------------------------------------------------------------------

[MichaelJCole]

Found this from here

I use mupx for deploys on DigitalOcean's Ubuntu 14.04_64 without problems.

This shouldn't be a problem: npm -g install npm@latest unless node installed wrong.

Maybe your app is really broken? Have you tried deploying the todo app? What happens?

[DerMarcus]

Hi,

this "npm WARN deprecated" error is reported pretty often. I am facing that issue now too. Mostly the recommendation is to increase the "deployCheckWaitTime".

I did the same, but it was not working. After analyzing the issue further I found a simple reason on our side: the server does not have a connection to the internet.

Probably increasing the deployCheckWaitTime is helpfull for slow internet connections. But if your server does not have a internet connection the error is thrown for sure. I simple double checked that by plugin in and out the wire of our server.

Does somebody have a solution to deploy with mupx for ubuntu servers which are completely offline?

Thanks