Databases
StackOverflow2013
Postsdbo
POPerforming `mup deploy` a second time crashes Meteor.js
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPerforming `mup deploy` a second time crashes Meteor.js
    primarykey
    data
    text
    <p>The first execution of <code>mup depoly</code> works fine. However doing <code>mup deploy</code> a second time or running <code>mup reconfig</code> will cause Meteor.js to crash. </p> <pre><code>Bundling Started: /var/www/test-app Started TaskList: Deploying App [localhost] uploading bundle [localhost] uploading bundle: SUCCESS [localhost] setting up env vars [localhost] setting up env vars: SUCCESS [localhost] uploading settings.json [localhost] uploading settings.json: SUCCESS [localhost] calling deploy script [localhost] calling deploy script: FAILED -----------------------------------STDERR----------------------------------- Warning: Permanently added 'localhost' (ECDSA) to the list of known hosts. npm WARN package.json http-proxy@1.0.0 No repository field. npm http GET https://registry.npmjs.org/fibers npm http 304 https://registry.npmjs.org/fibers % 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) couldn't connect to host reverted back to the previous version due to the latest version didn't pick up! -----------------------------------STDOUT----------------------------------- &gt; fibers@1.0.1 install /opt/meteor/tmp/bundle/programs/server/node_modules/fibers &gt; node ./build.js `linux-x64-v8-3.14` exists; testing Binary is fine; exiting fibers@1.0.1 node_modules/fibers meteor stop/waiting meteor start/running, process 4087 meteor stop/waiting meteor start/running, process 4112 ---------------------------------------------------------------------------- Completed TaskList: Deploying App </code></pre> <p>Meteor isn't running after the command has finished running. Would like to know if anyone have solved this problem. Thanks!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USAthena Wisdom
    1. USAthena Wisdom
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COFrom the `STDERR` it might be that your server has a bit of internet trouble. It couldn't download something, try again and see if it fixes itself
      singulars
      1. POPerforming `mup deploy` a second time crashes Meteor.js
      1. USAkshat
    2. CO@Akshat I tried `curl https://registry.npmjs.org/fibers -k` and was able to download fibers. However `mup deploy` still gave the same error
      singulars
      1. POPerforming `mup deploy` a second time crashes Meteor.js
      1. USAthena Wisdom
    3. COIts not likely thats the url its fetching. Its some part of fibers. If you look inside that file you're curling it contains more files
      singulars
      1. POPerforming `mup deploy` a second time crashes Meteor.js
      1. USAkshat
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload