Verifying Deployment: FAILED

[dominicarrojado]

Previous instance I don't have a problem redeploying. I created a new instance in EC2 and I'm getting this error.

Verifying Deployment: FAILED

    -----------------------------------STDERR-----------------------------------
    e/lib/connection/connection.js:170:10)
        at Socket.g (events.js:260:16)
        at emitNone (events.js:67:13)

    > meteor-dev-bundle@0.0.0 install /bundle/bundle/programs/server
    > node npm-rebuild.js

    {
      "meteor-dev-bundle": "0.0.0",
      "npm": "3.10.5",
      "ares": "1.10.1-DEV",
      "http_parser": "2.5.2",
      "icu": "56.1",
      "modules": "46",
      "node": "4.4.7",
      "openssl": "1.0.2h",
      "uv": "1.8.0",
      "v8": "4.5.103.36",
      "zlib": "1.2.8"
    }
    npm WARN meteor-dev-bundle@0.0.0 No description
    npm WARN meteor-dev-bundle@0.0.0 No repository field.
    npm WARN meteor-dev-bundle@0.0.0 No license field.
    => Starting meteor app on port:80
    Note: you are using a pure-JavaScript implementation of bcrypt.
    While this implementation will work correctly, it is known to be
    approximately three times slower than the native implementation.
    In order to use the native implementation instead, run

      meteor npm install --save bcrypt

    in the root directory of your application.

    => Redeploying previous version of the app

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

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

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

[dominicarrojado]

I now have a new error:

-----------------------------------STDERR-----------------------------------
      at Function._.each._.forEach (/bundle/bundle/programs/server/node_modules/underscore/underscore.js:79:11)

    > meteor-dev-bundle@0.0.0 install /bundle/bundle/programs/server
    > node npm-rebuild.js

    {
      "meteor-dev-bundle": "0.0.0",
      "npm": "3.10.5",
      "ares": "1.10.1-DEV",
      "http_parser": "2.5.2",
      "icu": "56.1",
      "modules": "46",
      "node": "4.4.7",
      "openssl": "1.0.2h",
      "uv": "1.8.0",
      "v8": "4.5.103.36",
      "zlib": "1.2.8"
    }
    npm WARN meteor-dev-bundle@0.0.0 No description
    npm WARN meteor-dev-bundle@0.0.0 No repository field.
    npm WARN meteor-dev-bundle@0.0.0 No license field.
    => Starting meteor app on port:80
    Note: you are using a pure-JavaScript implementation of bcrypt.
    While this implementation will work correctly, it is known to be
    approximately three times slower than the native implementation.
    In order to use the native implementation instead, run

      meteor npm install --save bcrypt

    in the root directory of your application.

    => Redeploying previous version of the app

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

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

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

[kyle-rader]

This is most often because the verification is not waiting long enough for the app to finish starting up. See my issue #265

[kyle-rader]

@mroftalp Are you trying to deploy your app and run it behind a reverse proxy (like Nginx)?

[dominicarrojado]

@kyle-rader Is it because there's a comment in the mup.js? I haven't tried removing the comments, I'll try again later. No, I'm not running it behind a reverse proxy

[kyle-rader]

@mroftalp If the comment is proper JS then I wouldn't think that would cause an issue.
Easy enough to test though (I'd say worth doing).

[ivandaho]

Have the same/similar issue - see #267 (comment)

I think it's due to 1.4.1 adding the warning message for bcrypt? Mup verifies it fine if i have the wait time set longer. Even with a short wait time, the app deploys without problems even with failed verification

[dominicarrojado]

Fixed by removing comments in mup.js

[wwlweihai]

I have solved most error in deploy process, and write a file about the deploy.You can see at meteor-deploy
notice: it is chinese!

Hope this helps

[avishaan]

@wwlweihai your link is not active

[blainehansen]

I'm having this same problem (I've documented it here on this SO post), and removing the comments didn't make any difference.

[avishaan]

@blainehansen, can you post your entire log?

[kyle-rader]

I discovered my verification error was because my deploy account was using
the zsh shell and the verification uses some bash specific commands, so it
immediately failed.
On Fri, Sep 23, 2016 at 1:45 PM Avishaan notifications@github.com wrote:

@blainehansen https://github.com/blainehansen, can you post your entire
log?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#280 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEiP3MuOzpIa7BxLREFU_uHxu8R1nAVQks5qtDpvgaJpZM4J2aCE
.

Kyle W. Rader

kyle@kylerader.ninja

425.241.7977
kylerader.ninja

[blainehansen]

Check out my answer to the SO post it turned out to be the ROOT_URL option needing the http:// protocol included.

[blainehansen]

All the npm output about packages and versions and everything is a red herring and is throwing you off I think. Get more of the log (mup logs --tail=200 or maybe even longer) and try to find the real error message. In my case it was the Error: $ROOT_URL, if specified, must be an URL that mattered, and everything else was just happening because the server was flapping around trying unsuccessfully to restart.

[avishaan]

@blainehansen definitely, for me it was trying to run make and didn't have build-essentials. That's why you really have to look at the entire logs

@kyle-rader that seems odd, I thought most bash stuff was still compatible with zsh (i'm using zsh here)