Heroku代码= H10 desc =“App崩溃” - 无法弄清楚它崩溃的原因

时间:2013-06-18 23:08:56

标签: heroku heroku-postgres

我一直在寻找这个问题一段时间,并且在我的情况下找不到任何似乎适用的东西。我一直在盯着这些日志,我看不出是什么问题。

这在以前的部署过程中发生过,但似乎总是自行解决。现在这只是自己发生的(没有部署),我无法摆脱它。尝试恢复到以前版本的应用程序,但似乎我被卡住了。我重置了dyno并且还完成了rake db:migrate。

日志中有一些重复的东西,但我只是不知道从中读取什么。任何人都知道问题出在哪里?任何指导将不胜感激。请参阅下面的日志。

Jun 18 15:51:54 snapclass-production app/heroku-postgres:  source=HEROKU_POSTGRESQL_WHITE measure.current_transaction=1077 measure.db_size=6153016bytes measure.tables=0 measure.active-connections=3 measure.waiting-connections=0 measure.index-cache-hit-rate=0.99981 measure.table-cache-hit-rate=0.99349
Jun 18 15:52:06 snapclass-production heroku/router:  at=error code=H10 desc="App crashed" method=GET path=/ host=www.snapclass.com fwd="46.165.195.139" dyno= connect= service= status=503 bytes= 
Jun 18 15:52:07 snapclass-production heroku/router:  at=error code=H10 desc="App crashed" method=GET path=/ host=www.snapclass.com fwd="178.255.152.2" dyno= connect= service= status=503 bytes= 
Jun 18 15:52:12 snapclass-production app/postgres:  [47-1]  [] LOG:  checkpoint starting: time 
Jun 18 15:52:13 snapclass-production app/postgres:  [48-1]  [] LOG:  checkpoint complete: wrote 0 buffers (0.0%); 0 transaction log file(s) added, 0 removed, 0 recycled; write=0.000 s, sync=0.000 s, total=0.334 s; sync files=0, longest=0.000 s, average=0.000 s 
Jun 18 15:52:51 snapclass-production app/heroku-postgres:  source=HEROKU_POSTGRESQL_WHITE measure.current_transaction=1077 measure.db_size=6153016bytes measure.tables=0 measure.active-connections=3 measure.waiting-connections=0 measure.index-cache-hit-rate=0.99994 measure.table-cache-hit-rate=0.99997 
Jun 18 15:53:06 snapclass-production heroku/router:  at=error code=H10 desc="App crashed" method=GET path=/ host=www.snapclass.com fwd="95.141.32.46" dyno= connect= service= status=503 bytes= 
Jun 18 15:53:48 snapclass-production app/heroku-postgres:  source=HEROKU_POSTGRESQL_WHITE measure.current_transaction=1077 measure.db_size=6153016bytes measure.tables=0 measure.active-connections=3 measure.waiting-connections=0 measure.index-cache-hit-rate=0.97826 measure.table-cache-hit-rate=0.99999 
Jun 18 15:54:06 snapclass-production heroku/router:  at=error code=H10 desc="App crashed" method=GET path=/ host=www.snapclass.com fwd="95.211.217.68" dyno= connect= service= status=503 bytes= 
Jun 18 15:54:17 snapclass-production heroku/router:  at=error code=H10 desc="App crashed" method=GET path=/ host=www.snapclass.com fwd="205.197.158.210" dyno= connect= service= status=503 bytes= 
Jun 18 15:54:17 snapclass-production heroku/router:  at=error code=H10 desc="App crashed" method=GET path=/favicon.ico host=www.snapclass.com fwd="205.197.158.210" dyno= connect= service= status=503 bytes= 
Jun 18 15:54:25 snapclass-production heroku/router:  at=error code=H10 desc="App crashed" method=GET path=/ host=demosidney.snapclass.com fwd="202.46.61.33" dyno= connect= service= status=503 bytes=  
Jun 18 15:54:44 snapclass-production heroku/web.1:  State changed from crashed to starting 
Jun 18 15:54:44 snapclass-production app/heroku-postgres:  source=HEROKU_POSTGRESQL_WHITE measure.current_transaction=1077 measure.db_size=6153016bytes measure.tables=0 measure.active-connections=3 measure.waiting-connections=0 measure.index-cache-hit-rate=0.98897 measure.table-cache-hit-rate=0.99087 
Jun 18 15:54:48 snapclass-production heroku/web.1:  Starting process with command `bundle exec thin start -R config.ru -e $RAILS_ENV -p 50180` 
Jun 18 15:55:40 snapclass-production app/heroku-postgres:  source=HEROKU_POSTGRESQL_WHITE measure.current_transaction=1077 measure.db_size=6153016bytes measure.tables=0 measure.active-connections=3 measure.waiting-connections=0 measure.index-cache-hit-rate=0.99926 measure.table-cache-hit-rate=0.99996 
Jun 18 15:55:50 snapclass-production heroku/web.1:  Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch 
Jun 18 15:55:50 snapclass-production heroku/web.1:  Stopping process with SIGKILL 
Jun 18 15:55:51 snapclass-production heroku/web.1:  Process exited with status 137 
Jun 18 15:55:51 snapclass-production heroku/web.1:  State changed from starting to crashed 
Jun 18 15:55:52 snapclass-production heroku/router:  at=error code=H10 desc="App crashed" method=GET path=/ host=demosidney.snapclass.com fwd="119.63.193.130" dyno= connect= service= status=503 bytes= 
Jun 18 15:55:52 snapclass-production heroku/router:  at=error code=H10 desc="App crashed" method=GET path=/snapclasses/sat-prep-math/register host=www.snapclass.com fwd="173.199.115.115" dyno= connect= service= status=503 bytes= 
Jun 18 15:55:53 snapclass-production heroku/router:  at=error code=H10 desc="App crashed" method=GET path=/ host=www.snapclass.com fwd="23.21.36.78" dyno= connect= service= status=503 bytes= 
Jun 18 15:55:54 snapclass-production heroku/router:  at=error code=H10 desc="App crashed" method=GET path=/ host=www.snapclass.com fwd="23.22.98.102" dyno= connect= service= status=503 bytes= 
Jun 18 15:55:54 snapclass-production heroku/router:  at=error code=H10 desc="App crashed" method=GET path=/ host=www.snapclass.com fwd="91.109.115.41" dyno= connect= service= status=503 bytes= 
Jun 18 15:56:06 snapclass-production heroku/router:  at=error code=H10 desc="App crashed" method=GET path=/ host=www.snapclass.com fwd="174.34.224.167" dyno= connect= service= status=503 bytes= 

7 个答案:

答案 0 :(得分:18)

请尝试以下步骤:

- git push heroku master # if not done
- heroku run rake db:migrate
- heroku restart

等几分钟......

答案 1 :(得分:10)

在我的情况下,这是因为我正在硬编码要使用的端口,

我改变了这个,它起作用了

app.listen(process.env.PORT || 3000);

答案 2 :(得分:4)

创建一个heroku帐户

 $heroku create

验证你的git configration是否正常

$git remote -v

将Git仓库与现有应用程序相关联

$heroku git:remote -a herokuapp-name

执行push to master

$git push heroku master

要使数据库正常工作,您必须迁移到生产数据库

$heroku run bundle exec rake db:migrate

然后重启

heroku restart

最终浏览到您的位置

答案 3 :(得分:0)

您需要在本地编译资产。 我经常跑

bundle exec rake assets:precompile 

然后提交并推送到heroku。

答案 4 :(得分:0)

我在package.json中的主条目指向错误的目录。确保它指向构建输出目录。对于我的情况,我的服务器文件位于 / bin 文件夹中,因此我设置了package.json

{
  "main": "build/bin/www.js"
  "scripts": {
    "start": "node ."
  }
}

答案 5 :(得分:0)

在我的情况下,我正在使用babel在ES6上进行快速处理,将babel导入devDependency后( Heroku忽略了生产中的devDependencies ),然后将它们纳入对我有用的依赖中。 >

"dependencies": {
    "@babel/register": "^7.8.3",
    "@babel/core": "^7.8.4",
    "@babel/preset-env": "^7.8.4"
}

答案 6 :(得分:0)

我也遇到了这个错误,总的来说,这个错误意味着它不能与您的依赖项一起使用,原因之一可能是依赖项的旧版本。我通过以下两个步骤解决了这个问题: 1)我手动更新了所有依赖项。 2)我将Flask API从app.py更改为err.py(使用其他名称可能会有所帮助,但这不是必需的。

这对我有用。 希望对您有帮助!