Mup issue on EC2 Ubuntu instance (solved)


#1

I checked github status just now: https://status.github.com/messages, and it says everything is operational. I did a mup setup, mup deploy again and get the following error.

I’m deploying to a standard AWS EC2 Ubuntu instance.

Invoking deployment process: FAILED

-----------------------------------STDERR-----------------------------------
e/ubuntu/.node-gyp/0.10.36',
gyp info spawn args   '-Dmodule_root_dir=/opt/my_app/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
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
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0curl: (7) Failed to connect to localhost port 80: Connection refused
Latest deployment failed! Reverted back to the previous version.
-----------------------------------STDOUT-----------------------------------
int-clients/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt/build’

> fibers@1.0.5 install /opt/my_app/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@4.1.0 node_modules/semver

fibers@1.0.5 node_modules/fibers

chalk@0.5.1 node_modules/chalk
├── ansi-styles@1.1.0
├── escape-string-regexp@1.0.3
├── supports-color@0.2.0
├── has-ansi@0.1.0 (ansi-regex@0.2.1)
└── strip-ansi@0.3.0 (ansi-regex@0.2.1)

eachline@2.3.3 node_modules/eachline
└── type-of@2.0.1

source-map-support@0.2.8 node_modules/source-map-support
└── source-map@0.1.32 (amdefine@0.1.0)
Waiting for MongoDB to initialize. (5 minutes)
connected
my-app stop/waiting
my-app start/running, process 17998
Waiting for 30 seconds while app is booting up
Checking is app booted or not?
my-app stop/waiting
my-app start/running, process 18226
----------------------------------------------------------------------------

My configuration file I’ve always used:

{
  "servers": [
    {
      "host": "staging.my-application.com",
      "username": "ubuntu",
      "pem": "/Users/username/Meteors/pem_file.pem"
    }
  ],
  "setupMongo": true,
  "setupNode": true,
  "nodeVersion": "0.10.36", 
  "setupPhantom": false,
  "appName": "application-name",
  "app": "/Users/username/Meteors/application_name",
  "env": {
    "ROOT_URL": "https://staging.my-site.com" // change to https
  },
  "ssl": {
    "pem": "./ssl.pem"
  },
  "deployCheckWaitTime": 30
}

I’ve have had this setup for months without issue.


#2

There was an exception being thrown on startup I caught in a try catch block – I was re-throwing the exception and the deployment was failing because of this.


#3

Hi @aadams Thank you for posting this! I have the same problem as you! How did you solve the problem?