当meteor部署到具有mupx的AWS ubuntu时，得到错误跟踪 [英] got error trace when meteor deploy to AWS ubuntu with mupx

问题描述

我试过流星部署来ubuntu的npm mupx。当我尝试部署到aws ubuntu，我有一个错误。这是我的错误代码，有什么想法吗？请帮助我。

  [**。**。**。*] 2016-08-04T08：04：44.262760219Z npm WARN已弃用此版本的npm不支持重要功能，
 [**。**。**。*] 2016-08-04T08：04：44.263078622Z npm WARN已弃用，如范围包，由主要npm 
 [**。**。**。*] 2016-08-04T08：04：44.263608859Z npm WARN弃用注册表。考虑升级到至少npm @ 2，如果不是
 [**。**。**。*] 2016-08-04T08：04：44.263841265Z npm WARN不推荐使用最新的稳定版本。要升级到npm @ 2，请运行：
 [**。**。**。*] 2016-08-04T08：04：44.264022091Z npm WARN已弃用
 [**。**。* *。*] 2016-08-04T08：04：44.264214145Z npm WARN已弃用npm -g install npm @ latest-2 
 [**。**。**。*] 2016-08-04T08：04： 44.264388418Z npm WARN已弃用
 [**。**。**。*] 2016-08-04T08：04：44.264582942Z npm WARN已弃用要升级到最新的稳定版本，请运行：
 [* *。**。**。*] 2016-08-04T08：04：44.264753708Z npm WARN弃用
 [**。**。**。*] 2016-08-04T08：04：44.264955187Z npm WARN已弃用npm -g install npm @ latest 
 [**。**。**。*] 2016-08-04T08：04：44.265132059Z npm WARN弃用
 [**。**。* *。*] 2016-08-04T08：04：44.265319246Z npm WARN已弃用（根据系统上如何安装Node.js，您可以
 [**。**。**。*] -04T08：04：44.265507812Z npm WARN弃用可能需要在前面的命令前缀为`sudo`，如果
 [**。**。**。*] 2016-08-04T08：04：44.265698699Z npm WARN在Windows中弃用，从管理员提示符处运行它们。）
 [**。**。**。*] 2016-08-04T08：04：44.265870846Z npm WARN弃用
 [**。**。**。*] 2016-08-04T08：04： 44.266053678Z npm WARN已弃用如果您正在运行与
捆绑在一起的npm版本[**。**。**。*] 2016-08-04T08：04：44.266249940Z npm WARN已弃用Node.js 0.10 LTS ，请注意，下一个版本的0.10 LTS 
 [**。**。**。*] 2016-08-04T08：04：44.266454393Z npm WARN已弃用将与npm @ 2的版本捆绑在一起，它有一些小
 [**。**。**。*] 2016-08-04T08：04：44.266764265Z npm WARN不建议使用npm run-script和
的向后不兼容更改[**。**。**。*] 2016-08-04T08：04：44.266962265Z npm WARN不推荐使用的行为。 
 [**。**。**。*] 2016-08-04T08：04：44.500691274Z npm WARN package.json meteor-dev-bundle@0.0.0没有描述
 [**。 **。**。*] 2016-08-04T08：04：44.504356284Z npm WARN package.json meteor-dev-bundle@0.0.0没有仓库字段。 
 [**。**。**。*] 2016-08-04T08：04：44.507612660Z npm WARN package.json meteor-dev-bundle@0.0.0没有README数据
 [** ** **。*] 2016-08-04T08：04：44.597973214Z npm WARN无法在wd中运行meteor-dev-bundle@0.0.0 node npm-rebuild.js（wd = / bundle / bundle / programs /服务器）
 [**。**。**。*] 2016-08-04T08：04：44.615599841Z =>在港口启动流星应用程序：80 
 [**。**。**。*] 2016-08-04T08：04：44.675588035Z 
 [**。**。**。*] 2016 -08-04T08：04：44.675961880Z assert.js：93 
 [**。**。**。*] 2016-08-04T08：04：44.676233801Z throw new assert.AssertionError（{
 [**。**。**。*] 2016-08-04T08：04：44.676351801Z ^ 
 [**。**。**。*] 2016-08-04T08：04：44.677859197Z AssertionError：undefined===function
 [**。**。**。*] 2016-08-04T08：04：44.677870250Z在wrapPathFunction（/ bundle / bundle / programs / server / mini -files.js：77：10）
 [**。**。**。*]在对象的 < anonymous>（/ bundle / bundle / programs /）中的08-08T08：04：44.677874284Z server / mini-files.js：108：24）
 [**。**。**。*] 2016-08-04T08：04：44.677892655Z在Module._compile（module.js：456：26 ）
 [**。**。**。*] 2016-08-04T08：04：44.677896149Z在Object.Module._extensions..js（module.js：474：10）
 [ **。**。*。*] 2016-08-04T08：04：44.677898899Z在Module.load（module.js：356：32）
 [**。**。**。*]在Function.Module._load中，版本为08-04T08：04：44.677901570Z （module.js：312：12）
 [**。**。**。*] 2016-08-04T08：04：44.677904229Z在Module.require（module.js：364：17）
 [**。**。**。*] 2016-08-04T08：04：44.677906984Z at require（module.js：380：17）
 [**。**。**。* ] 2016-08-04T08：04：44.677909741Z在Object。< anonymous> （/bundle/bundle/programs/server/boot.js:9:13）
 [**。**。**。*] 2016-08-04T08：04：44.677912674Z在Module._compile（module .js：456：26）
  

如果您对本次交易有任何想法，只需让我知道解！

解决方案

我今天刚刚遇到同样的事情几个小时。

您当前的部署具有节点版本v0.xx（MupX中的硬编码），Meteor 1.4需要v4.4.7。这是我所知道的主要原因。

我如何解决问题：我用mongodump备份，将其下载到我的电脑，从服务器中删除所有内容，由KadiraHQ（昨天更新）安装了 Mup ，并将此Docker映像包含在选项中：

  dockerImage：'abernix / meteord：base'
  

我做了mup部署然后 mongorestore 导入DB。

您还可以查看此问题，特别是abernix的评论。

请注意，对于pem和路径，Mup不允许您在路径中使用〜，并且不会给您一个可搜索的错误。您需要填写完整的网址：

  pem：'/Users/luna/.ssh/id_rsa'
  

希望这有帮助，让我知道你是否被困在某个地方。

I tried meteor deploy to aws ubuntu for npm mupx. When i try deploy to aws ubuntu , i got a error. here is my error code, any idea about this? please help me.

[**.**.**.*] 2016-08-04T08:04:44.262760219Z npm WARN deprecated This version of npm lacks support for important features,
[**.**.**.*] 2016-08-04T08:04:44.263078622Z npm WARN deprecated such as scoped packages, offered by the primary npm
[**.**.**.*] 2016-08-04T08:04:44.263608859Z npm WARN deprecated registry. Consider upgrading to at least npm@2, if not the
[**.**.**.*] 2016-08-04T08:04:44.263841265Z npm WARN deprecated latest stable version. To upgrade to npm@2, run:
[**.**.**.*] 2016-08-04T08:04:44.264022091Z npm WARN deprecated 
[**.**.**.*] 2016-08-04T08:04:44.264214145Z npm WARN deprecated   npm -g install npm@latest-2
[**.**.**.*] 2016-08-04T08:04:44.264388418Z npm WARN deprecated 
[**.**.**.*] 2016-08-04T08:04:44.264582942Z npm WARN deprecated To upgrade to the latest stable version, run:
[**.**.**.*] 2016-08-04T08:04:44.264753708Z npm WARN deprecated 
[**.**.**.*] 2016-08-04T08:04:44.264955187Z npm WARN deprecated   npm -g install npm@latest
[**.**.**.*] 2016-08-04T08:04:44.265132059Z npm WARN deprecated 
[**.**.**.*] 2016-08-04T08:04:44.265319246Z npm WARN deprecated (Depending on how Node.js was installed on your system, you
[**.**.**.*] 2016-08-04T08:04:44.265507812Z npm WARN deprecated may need to prefix the preceding commands with `sudo`, or if
[**.**.**.*] 2016-08-04T08:04:44.265698699Z npm WARN deprecated on Windows, run them from an Administrator prompt.)
[**.**.**.*] 2016-08-04T08:04:44.265870846Z npm WARN deprecated 
[**.**.**.*] 2016-08-04T08:04:44.266053678Z npm WARN deprecated If you're running the version of npm bundled with
[**.**.**.*] 2016-08-04T08:04:44.266249940Z npm WARN deprecated Node.js 0.10 LTS, be aware that the next version of 0.10 LTS
[**.**.**.*] 2016-08-04T08:04:44.266454393Z npm WARN deprecated will be bundled with a version of npm@2, which has some small
[**.**.**.*] 2016-08-04T08:04:44.266764265Z npm WARN deprecated backwards-incompatible changes made to `npm run-script` and
[**.**.**.*] 2016-08-04T08:04:44.266962265Z npm WARN deprecated semver behavior.
[**.**.**.*] 2016-08-04T08:04:44.500691274Z npm WARN package.json meteor-dev-bundle@0.0.0 No description
[**.**.**.*] 2016-08-04T08:04:44.504356284Z npm WARN package.json meteor-dev-bundle@0.0.0 No repository field.
[**.**.**.*] 2016-08-04T08:04:44.507612660Z npm WARN package.json meteor-dev-bundle@0.0.0 No README data
[**.**.**.*] 2016-08-04T08:04:44.597973214Z npm WARN cannot run in wd meteor-dev-bundle@0.0.0 node npm-rebuild.js (wd=/bundle/bundle/programs/server)
[**.**.**.*] 2016-08-04T08:04:44.615599841Z => Starting meteor app on port:80
[**.**.**.*] 2016-08-04T08:04:44.675588035Z 
[**.**.**.*] 2016-08-04T08:04:44.675961880Z assert.js:93
[**.**.**.*] 2016-08-04T08:04:44.676233801Z   throw new assert.AssertionError({
[**.**.**.*] 2016-08-04T08:04:44.676351801Z         ^
[**.**.**.*] 2016-08-04T08:04:44.677859197Z AssertionError: "undefined" === "function"
[**.**.**.*] 2016-08-04T08:04:44.677870250Z     at wrapPathFunction (/bundle/bundle/programs/server/mini-files.js:77:10)
[**.**.**.*] 2016-08-04T08:04:44.677874284Z     at Object.<anonymous> (/bundle/bundle/programs/server/mini-files.js:108:24)
[**.**.**.*] 2016-08-04T08:04:44.677892655Z     at Module._compile (module.js:456:26)
[**.**.**.*] 2016-08-04T08:04:44.677896149Z     at Object.Module._extensions..js (module.js:474:10)
[**.**.**.*] 2016-08-04T08:04:44.677898899Z     at Module.load (module.js:356:32)
[**.**.**.*] 2016-08-04T08:04:44.677901570Z     at Function.Module._load (module.js:312:12)
[**.**.**.*] 2016-08-04T08:04:44.677904229Z     at Module.require (module.js:364:17)
[**.**.**.*] 2016-08-04T08:04:44.677906984Z     at require (module.js:380:17)
[**.**.**.*] 2016-08-04T08:04:44.677909741Z     at Object.<anonymous> (/bundle/bundle/programs/server/boot.js:9:13)
[**.**.**.*] 2016-08-04T08:04:44.677912674Z     at Module._compile (module.js:456:26)

if you have any idea about this deal, just let me know any solution!

解决方案

I just struggled with the same thing today for a few hours.

Your current deployment has node version v0.x.x (hard coded in MupX) and Meteor 1.4 needs v4.4.7. Thats the main reason as far as I know.

How I solved the issue: I got a backup with mongodump, downloaded it to my computer, erased everything from the server, installed Mup by KadiraHQ (updated yesterday), did the setup and included this docker image in options:

dockerImage: 'abernix/meteord:base'

I did mup deploy then mongorestore to import the DB.

You can also check this issue and especially the comments by abernix.

Please note that for both pem and path, Mup doesn't let you use ~ in the paths and doesn't give you a searchable error. You need to write the full URL like this:

pem: '/Users/luna/.ssh/id_rsa'

Hope this helps and let me know if you get stuck somewhere.

这篇关于当meteor部署到具有mupx的AWS ubuntu时，得到错误跟踪的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！