Wie Meteor App auf Ubuntu mithilfe von MUPX mit MONGO_URL bereitstellen?

Question

Ich versuche Meteor App auf Ubuntu14.04/AWS mit mupx zu implementieren.

Hier ist meine Umgebung.

Server

Knoten: v5.10.0, npm: 3.8.9, Ubuntu: 14,04

Kunde

Knoten: V5.5.0, npm: 3.8.8, Mac : Version 10.11.014

mupx setup -> alles sieht gut aus. mupx deploy -> Überprüfen der Bereitstellung: FAILED passiert.

hier einloggen

-----------------------------------STDERR----------------------------------- 
pm 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 
npm WARN cannot run in wd meteor-dev-bundle@0.0.0 node npm-rebuild.js (wd=/bundle/bundle/programs/server) 
=> Starting meteor app on port:80 

=> Redeploying previous version of the app 

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

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

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

Als ich "mupx Protokolle --tail = 50" tat Ich habe ...

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

[52.39.5.187] => Starting meteor app on port:80 
[52.39.5.187] npm WARN deprecated npm -g install npm@latest-2 
npm WARN deprecated 
npm WARN deprecated To upgrade to the latest stable version, run: 
npm WARN deprecated 
npm 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 
npm WARN cannot run in wd meteor-dev-bundle@0.0.0 node npm-rebuild.js (wd=/bundle/bundle/programs/server) 

/bundle/bundle/programs/server/node_modules/fibers/future.js:300 
         throw(ex); 
          ^
[object Object] 
npm WARN deprecated This version of npm lacks support for important features, 
npm WARN deprecated such as scoped packages, offered by the primary npm 
npm WARN deprecated registry. Consider upgrading to at least npm@2, if not the 
npm WARN deprecated latest stable version. To upgrade to npm@2, run: 
npm WARN deprecated 
npm WARN deprecated npm -g install npm@latest-2 
npm WARN deprecated 
npm WARN deprecated To upgrade to the latest stable version, run: 
npm WARN deprecated 
npm 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 
[52.39.5.187] 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 
npm WARN cannot run in wd meteor-dev-bundle@0.0.0 node npm-rebuild.js (wd=/bundle/bundle/programs/server) 
[52.39.5.187] => Starting meteor app on port:80 

Mein mup.json ist

{ 
    // Server authentication info 
    "servers": [ 
    { 
     "host": "xxx.xxx.xxx.xxx", 
     "username": "__username___", 
     "pem": "__path_to_pem__", 
     "env": {} 
    } 
    ], 

    // Install MongoDB on the server. Does not destroy the local MongoDB on future setups 
    "setupMongo": false, 

    // Application name (no spaces). 
    "appName": "__app_name__", 

    // Location of app (local directory). This can reference '~' as the users home directory. 
    // i.e., "app": "~/Meteor/my-app", 
    // This is the same as the line below. 
    "app": "__path_to_app_source__", 

    // Configure environment 
    // ROOT_URL must be set to your correct domain (https or http) 
    "env": { 
    "PORT": 1342, 
    "ROOT_URL": "https://xxx.xxx.xxx", 
    "MONGO_URL": "mongodb://__user__:__pass__@192.168.0.3:27017/__dbname__" 
    }, 

    // Meteor Up checks if the app comes online just after the deployment. 
    // Before mup checks that, it will wait for the number of seconds configured below. 
    "deployCheckWaitTime": 120, 

    // show a progress bar while uploading. 
    // Make it false when you deploy using a CI box. 
    "enableUploadProgressBar": true 
} 

Ich habe MongoDB manuell vorbereitet.

Ich verbrachte den ganzen Tag hier, also wenn jemand mir einen Hinweis geben, werde ich das zu schätzen wissen. Danke,

Answer 1

Ich fand eine Lösung. Dies passiert, weil ich AWS und Docker nicht kenne.

Meine Sicherheitsgruppe hat verhindert, dass der Docker-Prozess auf Mongo zugreift. Alles, was ich tun musste, war Docker IP-Adresse Zugriff auf Mongo zu ermöglichen.

Vielen Dank.

Answer 2

Ich stelle viele Probleme, die von mup zu mupx wechseln. Dieses Problem scheinen im Zusammenhang mit dieser zu: https://github.com/arunoda/meteor-up/issues/958

I deployCheckWaitTime bis 600 und sehen, ob dies das Problem beheben, weil die App es und begann im Einsatz zu erhöhen, wurde woud versuchen, wie Sie von Ihrem Protokoll sehen:

[52.39.5.187] => Starting meteor app on port:80 

nach der Anwendung bereitgestellt wird, mupx eine Prüfung zu machen, wenn alles funktioniert nach n Sekunden durch deployCheckWaitTime Option angegeben, um zu sehen, so ist es nicht, wenn Sie beim Start langen Server-Betrieb im Hauptthread haben.