Heroku引导超时(错误R10) [英] Heroku Boot Timeout (Error R10)

查看:113
本文介绍了Heroku引导超时(错误R10)的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述



  2012-05-06T22:41每次启动我的应用程序时,它都无法超过60秒的时间点:11 + 00:00 heroku [web.1]:使用SIGKILL 
停止进程2012-05-06T22:41:11 + 00:00 heroku [web.1]:错误R10(引导超时) - > Web进程无法在启动后的60秒内绑定到$ PORT
2012-05-06T22:41:11 + 00:00 heroku [web.1]:进程已退出,状态为137
2012-05- 06T22:41:12 + 00:00 heroku [web.1]:状态从开始变为崩溃

这是我的 Procfile

  web:bundle exec thin start  - p $ PORT 

任何回应都将得到彻底赞赏。

com / dblock / heroku-forwardrel =noreferrer> https://github.com/dblock/heroku-forward 。


Every time I launch my app it cannot get past the 60 second point without:

2012-05-06T22:41:11+00:00 heroku[web.1]: Stopping process with SIGKILL
2012-05-06T22:41:11+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
2012-05-06T22:41:11+00:00 heroku[web.1]: Process exited with status 137
2012-05-06T22:41:12+00:00 heroku[web.1]: State changed from starting to crashed

Here is my Procfile:

web: bundle exec thin start -p $PORT

Any responses will be thoroughly appreciated.

解决方案

If your app does take longer than 60 seconds for "good" reasons, you can work around the 60s boot time limit with https://github.com/dblock/heroku-forward.

这篇关于Heroku引导超时(错误R10)的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆