流星应用程序成功部署到heroku。当我转到网址时出现heroku错误答案

【问题标题】：meteor app deployed to heroku successfully. heroku errors when I goes to the url流星应用程序成功部署到heroku。当我转到网址时出现heroku错误
【发布时间】：2016-06-14 09:06:53
【问题描述】：

这些是错误日志：

Heroku 本地运行非常好。有谁知道这些错误日志的含义以及我需要做些什么来修复它？

谢谢。

我将节点版本更改为 0.10.45，因为我听说 heroku 需要运行流星应用程序。

事情发生了变化，但我现在收到了一个 npm 错误。我相信 npm 版本是 2.1+。

请注意，由于我没有在应用程序中使用 mongo db，因此我没有在 heroku 配置中包含 mongo:labs 设置。这也会破坏事物吗？

   2016-06-13T03:56:13.082236+00:00 app[web.1]: npm ERR! Or if that isn't available, you can get their info via:
2016-06-13T03:56:13.082363+00:00 app[web.1]: npm ERR! 
2016-06-13T03:56:13.085838+00:00 app[web.1]: npm ERR!     /app/npm-debug.log
2016-06-13T03:56:13.861094+00:00 heroku[web.1]: State changed from starting to crashed
2016-06-13T03:56:15.460115+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=keela.herokuapp.com request_id=eb256901-593c-43a0-be3e-e4347daecf40 fwd="206.108.215.194" dyno= connect= service= status=503 bytes=
2016-06-13T03:56:13.082236+00:00 app[web.1]: npm ERR! Or if that isn't available, you can get their info via:
2016-06-13T03:56:13.082494+00:00 app[web.1]: npm ERR!     npm owner ls keela
2016-06-13T03:56:13.085156+00:00 app[web.1]: 
2016-06-13T03:56:13.085479+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2016-06-13T03:56:13.861094+00:00 heroku[web.1]: State changed from starting to crashed
2016-06-13T03:56:13.846631+00:00 heroku[web.1]: Process exited with status 1
2016-06-13T03:56:15.460115+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=keela.herokuapp.com request_id=eb256901-593c-43a0-be3e-e4347daecf40 fwd="206.108.215.194" dyno= connect= service= status=503 bytes=
2016-06-13T03:56:13.082236+00:00 app[web.1]: npm ERR! Or if that isn't available, you can get their info via:
2016-06-13T03:56:13.082363+00:00 app[web.1]: npm ERR! 
2016-06-13T03:56:13.846631+00:00 heroku[web.1]: Process exited with status 1
2016-06-13T03:56:15.460115+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=keela.herokuapp.com request_id=eb256901-593c-43a0-be3e-e4347daecf40 fwd="206.108.215.194" dyno= connect= service= status=503 bytes=
2016-06-13T03:56:13.082236+00:00 app[web.1]: npm ERR! Or if that isn't available, you can get their info via:
2016-06-13T03:56:13.082363+00:00 app[web.1]: npm ERR! 
2016-06-13T03:56:13.082494+00:00 app[web.1]: npm ERR!     npm owner ls keela
2016-06-13T03:56:13.085156+00:00 app[web.1]: 
2016-06-13T03:56:13.082702+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
2016-06-13T03:56:13.085479+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2016-06-13T03:56:13.085838+00:00 app[web.1]: npm ERR!     /app/npm-debug.log
2016-06-13T03:56:13.846631+00:00 heroku[web.1]: Process exited with status 1
2016-06-13T03:56:16.056881+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=keela.herokuapp.com request_id=45e1c2db-39c7-427f-b115-5a5927267642 fwd="206.108.215.194" dyno= connect= service= status=503 bytes=
2016-06-13T03:56:13.082236+00:00 app[web.1]: npm ERR! Or if that isn't available, you can get their info via:
2016-06-13T03:56:13.082494+00:00 app[web.1]: npm ERR!     npm owner ls keela
2016-06-13T03:56:13.082702+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
2016-06-13T03:56:13.085838+00:00 app[web.1]: npm ERR!     /app/npm-debug.log
2016-06-13T03:56:13.861094+00:00 heroku[web.1]: State changed from starting to crashed
2016-06-13T03:56:13.846631+00:00 heroku[web.1]: Process exited with status 1
2016-06-13T03:56:15.460115+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=keela.herokuapp.com request_id=eb256901-593c-43a0-be3e-e4347daecf40 fwd="206.108.215.194" dyno= connect= service= status=503 bytes=

这些是来自终端的 heroku 日志：

2016-06-13T03:56:05.528129+00:00 heroku[web.1]: State changed from crashed to starting
2016-06-13T03:56:06.563040+00:00 heroku[web.1]: Starting process with command `npm start`
2016-06-13T03:56:08.477065+00:00 app[web.1]:
2016-06-13T03:56:08.477075+00:00 app[web.1]: > keela@ start /app
2016-06-13T03:56:08.477108+00:00 app[web.1]: > meteor run
2016-06-13T03:56:08.477109+00:00 app[web.1]:
2016-06-13T03:56:08.480791+00:00 app[web.1]: sh: 1: meteor: not found
2016-06-13T03:56:08.484354+00:00 app[web.1]:
2016-06-13T03:56:08.488227+00:00 app[web.1]: npm ERR! Linux 3.13.0-85-generic
2016-06-13T03:56:08.488707+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start"
2016-06-13T03:56:08.488728+00:00 app[web.1]: npm ERR! node v0.10.45
2016-06-13T03:56:08.488892+00:00 app[web.1]: npm ERR! npm  v2.15.1
2016-06-13T03:56:08.489008+00:00 app[web.1]: npm ERR! file sh
2016-06-13T03:56:08.489134+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2016-06-13T03:56:08.489268+00:00 app[web.1]: npm ERR! errno ENOENT
2016-06-13T03:56:08.489383+00:00 app[web.1]: npm ERR! syscall spawn
2016-06-13T03:56:08.489490+00:00 app[web.1]: npm ERR! keela@ start: `meteor run`
2016-06-13T03:56:08.489846+00:00 app[web.1]: npm ERR! spawn ENOENT
2016-06-13T03:56:08.489945+00:00 app[web.1]: npm ERR!
2016-06-13T03:56:08.490043+00:00 app[web.1]: npm ERR! Failed at the keela@ start script 'meteor run'.
2016-06-13T03:56:08.490119+00:00 app[web.1]: npm ERR! This is most likely a problem with the keela package,
2016-06-13T03:56:08.490220+00:00 app[web.1]: npm ERR! not with npm itself.
2016-06-13T03:56:08.490296+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system:
2016-06-13T03:56:08.490540+00:00 app[web.1]: npm ERR!     meteor run
2016-06-13T03:56:08.490622+00:00 app[web.1]: npm ERR! You can get information on how to open an issue for this project with:
2016-06-13T03:56:08.490726+00:00 app[web.1]: npm ERR!     npm bugs keela
2016-06-13T03:56:08.490821+00:00 app[web.1]: npm ERR! Or if that isn't available, you can get their info via:
2016-06-13T03:56:08.490919+00:00 app[web.1]: npm ERR!
2016-06-13T03:56:08.490999+00:00 app[web.1]: npm ERR!     npm owner ls keela
2016-06-13T03:56:08.491174+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
2016-06-13T03:56:08.493551+00:00 app[web.1]:
2016-06-13T03:56:08.493856+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2016-06-13T03:56:08.494156+00:00 app[web.1]: npm ERR!     /app/npm-debug.log
2016-06-13T03:56:09.185720+00:00 heroku[web.1]: State changed from starting to crashed
2016-06-13T03:56:09.186797+00:00 heroku[web.1]: State changed from crashed to starting
2016-06-13T03:56:09.168263+00:00 heroku[web.1]: Process exited with status 1
2016-06-13T03:56:10.415088+00:00 heroku[web.1]: Starting process with command `npm start`

【问题讨论】：

可能是因为 Node.js 版本不兼容，Meteor 仍然使用 0.10.x 而你使用 5.x。解决这个问题的一个好方法是使用 Docker。查看github.com/meteorhacks/meteord
您使用哪个构建包？
我使用的构建包是这个：github.com/jordansissel/heroku-buildpack-meteor 谢谢，我会看看 docker.... 还有其他方法吗？
我把node的版本改成0.10.45还是坏了。但我现在有新的错误。

标签： meteor heroku

【解决方案1】：

Buildpacks 或流星 Heroku 仍然非常不稳定。我必须通过 buildpack 站点的 cmets 才能使用 buildpack 的分支。

你也是正确的，流星仍然使用 0.10.41+ 版本的节点。我通过使用 nvm 将我的节点版本更改为 0.10.45 来改变这一点。

同样使用 2.1.1 的 npm 版本

确保也为这些设置配置您的 package.json！

Heroku 错误日志非常模糊，让我头疼。

【讨论】：