Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Upgrading to 1.3.1 - mup deploy failed: "Prepare Bundle: FAILED"

See original GitHub issue

Get this error after upgrading to 1.3.1 and adding custom ssl certificates.

meteor: {
   ...
},
proxy:{
  domains: 'domain_name.com',
  ssl: {
    crt: './bundle.crt',
    key: './private.key',
    forceSSL: true
  }
}

mup setup - ok mup reconfig - ok mup deploy - failed

x Prepare Bundle: FAILED
   
   -----------------------------------STDERR-----------------------------------
   The command '/bin/sh -c cd  /built_app/programs/server &&      ROOT_URL=https://mydomainname.com  MONGO_URL=mongodb://localhost/meteor  VIRTUAL_HOST=mydomainname.com  HTTPS_METHOD=redirect  &&     npm install --unsafe-perm' returned a non-zero code: 137
   -----------------------------------STDOUT-----------------------------------
   se
   bitbot
   Sending build context to Docker daemon   84.8MB
   Step 1/4 : FROM abernix/meteord:base
   # Executing 1 build trigger...
   Step 1/1 : ENV NODE_VERSION ${NODE_VERSION:-4.8.3}
    ---> Using cache
    ---> ddce4fc7da07
   Step 2/4 : RUN mkdir /built_app
    ---> Using cache
    ---> 97ed41186e0a
   Step 3/4 : COPY ./ /built_app
    ---> Using cache
    ---> 025f7fc4c40f
   Step 4/4 : RUN cd  /built_app/programs/server &&      ROOT_URL=https://mydomainname.com  MONGO_URL=mongodb://localhost/meteor  VIRTUAL_HOST=mydomainname.com  HTTPS_METHOD=redirect  &&     npm install --unsafe-perm
    ---> Running in 393523b4657a
   
   > fibers@1.0.15 install /built_app/programs/server/node_modules/fibers
   > node build.js || nodejs build.js
   
   `linux-x64-46` exists; testing
   Binary is fine; exiting
   
   > meteor-dev-bundle@0.0.0 install /built_app/programs/server
   > node npm-rebuild.js
   
   
   > websocket@1.0.24 install /built_app/programs/server/npm/node_modules/websocket
   > (node-gyp rebuild 2> builderror.log) || (exit 0)
   
   Killed
   bitbot
   ----------------------------------------------------------------------------

Issue Analytics

State:
Created 6 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

3reactions

zoderncommented, Aug 30, 2017

It ran out of memory while running npm install.

Prepare Bundle might take more memory compared to how it used to run npm install. You could try setting meteor.docker.prepareBundle to false in your config.

Other options are to create a swap file, or increase the server’s ram.

0reactions

zhukovspcommented, Sep 2, 2017

@zodern Yes. I’ll try to make new deploy again and open new issue with more specified info.

Top Results From Across the Web

Meteor-up terminates after running deploy - Stack Overflow

prepareBundle in mup.js and setting it to false . I dealt with the same error a few weeks ago and with this workaround...

[SOLVED] Mup-classic errors - help - Meteor forums

For some reason the fork of mup won't deploy (install works), I get the following error: Invoking deployment process: FAILED ...

Getting Started - Meteor Up

If it failed due to a network error while uploading the bundle, you can run mup deploy --cached-build . It will then skip...

https://raw.githubusercontent.com/zodern/meteor-up...

1.5.9 - June 27, 2022 - Update @zodern/nodemiral ## 1.5.8 - April 20, 2022 - Update nginx - Improve output from prepare bundle...

Meteor Up 1.5 - zodern

The slowest parts of the deploy process done per server are uploading the bundle and running Prepare Bundle. Previously, when deploying to multiple...