不能heroku运行耙数据库通过我的应用程序迁移 [英] Can't heroku run rake db migrate through my app

查看:98
本文介绍了不能heroku运行耙数据库通过我的应用程序迁移的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

这是我第一次遇到这样的错误:

 运行连接到终端的`rake db:migrate` ...起,跑8524 
! Heroku客户端内部错误。
!搜索帮助:https://help.heroku.com
!或者报告一个错误:https://github.com/heroku/heroku/issues/new

错误:操作超时 - connect(2)(Errno :: ETIMEDOUT)
Backtrace :/usr/local/heroku/lib/heroku/client/rendezvous.rb:39:in`initialize'
/usr/local/heroku/lib/heroku/client/rendezvous.rb:39:in`open '
/usr/local/heroku/lib/heroku/client/rendezvous.rb:39:in'block in start'
/usr/local/heroku/ruby/lib/ruby/1.9.1 /timeout.rb:68:in`timeout'
/usr/local/heroku/lib/heroku/client/rendezvous.rb:31:in`start'
/ usr / local / heroku / lib /heroku/command/run.rb:113:in`rendezvous_session'
/usr/local/heroku/lib/heroku/command/run.rb:100:in`run_attached'
/ usr / local /heroku/lib/heroku/command/run.rb:21:in`index'
/usr/local/heroku/lib/heroku/command.rb:206:in`run'
/ usr /local/heroku/lib/heroku/cli.rb :28:在`start'
/ usr / local / heroku / bin / heroku:24:在< main>'

命令:heroku run rake db:migrate --app oppcis
版本:heroku-toolbelt / 2.35.0(x86_64-darwin10.8.0)ruby / 1.9.3

我一直在使用heroku一段时间......在大回归之后,我遇到了这个错误。



我已经过时了现在的Heroku新闻。



我希望有人可以给我一个建议,解决方案或涉及的问题。

谢谢。



编辑:



日志显示...

  2013-02-15T08:38:00 + 00:00 heroku [api]:用命令`bundle exec rake db:migrate`由ssalamat.peg@gmail启动进程。 com 
2013-02-15T08:38:03 + 00:00 heroku [run.6510]:等待客户
2013-02-15T08:38:03 + 00:00 heroku [run.6510] :用命令`bundle exec rake db:migrate`启动进程
2013-02-15T08:38:04 + 00:00 heroku [run.6510]:状态从开始变为
2013-02-15T08:38:33 + 00:00 heroku [run.6510]:错误R13(附加错误) - >无法附加到进程
2013-02-15T08:38:34 + 00:00 heroku [run.6510]:进程退出状态128
2013-02-15T08:38:34 + 00: 00 heroku [run.6510]:状态从上升到完成


解决方案

尝试在后台运行它

  heroku run:detached rake db:migrate 

code>

您也可以尝试 heroku疑难解答,因为它似乎是连接问题。

  heroku run rails console 
telnet rendezvous.runtime.heroku.com 5000

如果不起作用,您可能有一个防火墙阻止您与heroku的连接。

it is my first time to encounter such error(s):

Running `rake db:migrate` attached to terminal... up, run.8524
 !    Heroku client internal error.
 !    Search for help at: https://help.heroku.com
 !    Or report a bug at: https://github.com/heroku/heroku/issues/new

    Error:       Operation timed out - connect(2) (Errno::ETIMEDOUT)
    Backtrace:   /usr/local/heroku/lib/heroku/client/rendezvous.rb:39:in `initialize'
                 /usr/local/heroku/lib/heroku/client/rendezvous.rb:39:in `open'
                 /usr/local/heroku/lib/heroku/client/rendezvous.rb:39:in `block in start'
                 /usr/local/heroku/ruby/lib/ruby/1.9.1/timeout.rb:68:in `timeout'
                 /usr/local/heroku/lib/heroku/client/rendezvous.rb:31:in `start'
                 /usr/local/heroku/lib/heroku/command/run.rb:113:in `rendezvous_session'
                 /usr/local/heroku/lib/heroku/command/run.rb:100:in `run_attached'
                 /usr/local/heroku/lib/heroku/command/run.rb:21:in `index'
                 /usr/local/heroku/lib/heroku/command.rb:206:in `run'
                 /usr/local/heroku/lib/heroku/cli.rb:28:in `start'
                 /usr/local/heroku/bin/heroku:24:in `<main>'

    Command:     heroku run rake db:migrate --app oppcis
    Version:     heroku-toolbelt/2.35.0 (x86_64-darwin10.8.0) ruby/1.9.3

I've been out for awhile in using heroku... and after the big comeback, I encountered this error.

I am outdated already in terms of present Heroku news.

I hope somebody could give me a suggestion, solution or issues involved.

Thanks.

EDIT:

The logs says...

2013-02-15T08:38:00+00:00 heroku[api]: Starting process with command `bundle exec rake db:migrate` by ssalamat.peg@gmail.com
2013-02-15T08:38:03+00:00 heroku[run.6510]: Awaiting client
2013-02-15T08:38:03+00:00 heroku[run.6510]: Starting process with command `bundle exec rake db:migrate`
2013-02-15T08:38:04+00:00 heroku[run.6510]: State changed from starting to up
2013-02-15T08:38:33+00:00 heroku[run.6510]: Error R13 (Attach error) -> Failed to attach to process
2013-02-15T08:38:34+00:00 heroku[run.6510]: Process exited with status 128
2013-02-15T08:38:34+00:00 heroku[run.6510]: State changed from up to complete

解决方案

Try to run it in the "background"

 heroku run:detached rake db:migrate

You can also try heroku troubleshooting, as it appears to be a connection problem.

heroku run rails console
telnet rendezvous.runtime.heroku.com 5000

If it doesn't work, you probably have a firewall blocking your connection to heroku.

这篇关于不能heroku运行耙数据库通过我的应用程序迁移的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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