名称解析暂时失败(PG :: ConnectionBad)

吓人的

我在Heroku EU中托管了Rails 4应用程序。

过了两天,我几乎无法启动Heroku控制台。100次尝试中有90次以如下错误结束:

scaryguy@ubuntu:~/Sites/xxxxx.com$ heroku run console
Running `console` attached to terminal... up, run.9208
/app/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.0/lib/active_record/connection_adapters/postgresql_adapter.rb:825:in `initialize': could not translate host name "ec2-54-221-224-138.compute-1.amazonaws.com" to address: Temporary failure in name resolution (PG::ConnectionBad)
    from /app/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.0/lib/active_record/connection_adapters/postgresql_adapter.rb:825:in `new'
    from /app/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.0/lib/active_record/connection_adapters/postgresql_adapter.rb:825:in `connect'
    from /app/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.0/lib/active_record/connection_adapters/postgresql_adapter.rb:542:in `initialize'
    from /app/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.0/lib/active_record/connection_adapters/postgresql_adapter.rb:41:in `new'
    from /app/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.0/lib/active_record/connection_adapters/postgresql_adapter.rb:41:in `postgresql_connection'
    from /app/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.0/lib/active_record/connection_adapters/abstract/connection_pool.rb:440:in `new_connection'
    from /app/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.0/lib/active_record/connection_adapters/abstract/connection_pool.rb:450:in `checkout_new_connection'
    from /app/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.0/lib/active_record/connection_adapters/abstract/connection_pool.rb:421:in `acquire_connection'
    from /app/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.0/lib/active_record/connection_adapters/abstract/connection_pool.rb:356:in `block in checkout'
    from /app/vendor/ruby-2.0.0/lib/ruby/2.0.0/monitor.rb:211:in `mon_synchronize'
    from /app/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.0/lib/active_record/connection_adapters/abstract/connection_pool.rb:355:in `checkout'
    from /app/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.0/lib/active_record/connection_adapters/abstract/connection_pool.rb:265:in `block in connection'
    from /app/vendor/ruby-2.0.0/lib/ruby/2.0.0/monitor.rb:211:in `mon_synchronize'
    from /app/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.0/lib/active_record/connection_adapters/abstract/connection_pool.rb:264:in `connection'
    from /app/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.0/lib/active_record/connection_adapters/abstract/connection_pool.rb:546:in `retrieve_connection'
    from /app/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.0/lib/active_record/connection_handling.rb:79:in `retrieve_connection'
    from /app/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.0/lib/active_record/connection_handling.rb:53:in `connection'
    from /app/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.0/lib/active_record/model_schema.rb:203:in `table_exists?'
    from /app/vendor/bundle/ruby/2.0.0/gems/acts-as-taggable-on-2.4.1/lib/acts_as_taggable_on/acts_as_taggable_on/cache.rb:5:in `included'
    from /app/vendor/bundle/ruby/2.0.0/gems/acts-as-taggable-on-2.4.1/lib/acts_as_taggable_on/taggable.rb:98:in `include'
    from /app/vendor/bundle/ruby/2.0.0/gems/acts-as-taggable-on-2.4.1/lib/acts_as_taggable_on/taggable.rb:98:in `taggable_on'
    from /app/vendor/bundle/ruby/2.0.0/gems/acts-as-taggable-on-2.4.1/lib/acts_as_taggable_on/taggable.rb:39:in `acts_as_taggable_on'
    from /app/vendor/bundle/ruby/2.0.0/gems/acts-as-taggable-on-2.4.1/lib/acts_as_taggable_on/taggable.rb:15:in `acts_as_taggable'
    from /app/app/models/article.rb:6:in `<class:Article>'
    from /app/app/models/article.rb:1:in `<top (required)>'
    from /app/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.0/lib/active_support/dependencies.rb:228:in `require'
    from /app/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.0/lib/active_support/dependencies.rb:228:in `block in require'
    from /app/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.0/lib/active_support/dependencies.rb:213:in `load_dependency'
    from /app/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.0/lib/active_support/dependencies.rb:228:in `require'
    from /app/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.0/lib/active_support/dependencies.rb:329:in `require_or_load'
    from /app/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.0/lib/active_support/dependencies.rb:288:in `depend_on'
    from /app/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.0/lib/active_support/dependencies.rb:206:in `require_dependency'
    from /app/vendor/bundle/ruby/2.0.0/gems/railties-4.0.0/lib/rails/engine.rb:465:in `block (2 levels) in eager_load!'
    from /app/vendor/bundle/ruby/2.0.0/gems/railties-4.0.0/lib/rails/engine.rb:464:in `each'
    from /app/vendor/bundle/ruby/2.0.0/gems/railties-4.0.0/lib/rails/engine.rb:464:in `block in eager_load!'
    from /app/vendor/bundle/ruby/2.0.0/gems/railties-4.0.0/lib/rails/engine.rb:462:in `each'
    from /app/vendor/bundle/ruby/2.0.0/gems/railties-4.0.0/lib/rails/engine.rb:462:in `eager_load!'
    from /app/vendor/bundle/ruby/2.0.0/gems/railties-4.0.0/lib/rails/engine.rb:347:in `eager_load!'
    from /app/vendor/bundle/ruby/2.0.0/gems/railties-4.0.0/lib/rails/application/finisher.rb:56:in `each'
    from /app/vendor/bundle/ruby/2.0.0/gems/railties-4.0.0/lib/rails/application/finisher.rb:56:in `block in <module:Finisher>'
    from /app/vendor/bundle/ruby/2.0.0/gems/railties-4.0.0/lib/rails/initializable.rb:30:in `instance_exec'
    from /app/vendor/bundle/ruby/2.0.0/gems/railties-4.0.0/lib/rails/initializable.rb:30:in `run'
    from /app/vendor/bundle/ruby/2.0.0/gems/railties-4.0.0/lib/rails/initializable.rb:55:in `block in run_initializers'
    from /app/vendor/ruby-2.0.0/lib/ruby/2.0.0/tsort.rb:150:in `block in tsort_each'
    from /app/vendor/ruby-2.0.0/lib/ruby/2.0.0/tsort.rb:183:in `block (2 levels) in each_strongly_connected_component'
    from /app/vendor/ruby-2.0.0/lib/ruby/2.0.0/tsort.rb:219:in `each_strongly_connected_component_from'
    from /app/vendor/ruby-2.0.0/lib/ruby/2.0.0/tsort.rb:182:in `block in each_strongly_connected_component'
    from /app/vendor/ruby-2.0.0/lib/ruby/2.0.0/tsort.rb:180:in `each'
    from /app/vendor/ruby-2.0.0/lib/ruby/2.0.0/tsort.rb:180:in `each_strongly_connected_component'
    from /app/vendor/ruby-2.0.0/lib/ruby/2.0.0/tsort.rb:148:in `tsort_each'
    from /app/vendor/bundle/ruby/2.0.0/gems/railties-4.0.0/lib/rails/initializable.rb:54:in `run_initializers'
    from /app/vendor/bundle/ruby/2.0.0/gems/railties-4.0.0/lib/rails/application.rb:215:in `initialize!'
    from /app/vendor/bundle/ruby/2.0.0/gems/railties-4.0.0/lib/rails/railtie/configurable.rb:30:in `method_missing'
    from /app/config/environment.rb:5:in `<top (required)>'
    from /app/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.0/lib/active_support/dependencies.rb:228:in `require'
    from /app/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.0/lib/active_support/dependencies.rb:228:in `block in require'
    from /app/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.0/lib/active_support/dependencies.rb:213:in `load_dependency'
    from /app/vendor/bundle/ruby/2.0.0/gems/activesupport-4.0.0/lib/active_support/dependencies.rb:228:in `require'
    from /app/vendor/bundle/ruby/2.0.0/gems/railties-4.0.0/lib/rails/application.rb:189:in `require_environment!'
    from /app/vendor/bundle/ruby/2.0.0/gems/railties-4.0.0/lib/rails/commands.rb:63:in `<top (required)>'
    from bin/rails:4:in `require'
    from bin/rails:4:in `<main>'

我想知道这是否取决于我?还是这是一个很大的错误,Heroku认为不会再次在其状态页面上发出通知。我不确定,因为我在安装新的Ubuntu时遇到了困难。某些CA购物车问题...但是我现在可以连接到任何人...好吧,我不确定。

我昨天在Heroku开了张票,七个小时后,他们的回答是“问题仍然存在吗?”。

吓人的

在我将虚拟机和物理操作系统的DNS设置更改为使用Google DNS之后,一切都已修复!!!!

全部都是DNS问题...

我不知道是谁对此情况负责?是我的ISP提供商吗?我要生谁的气??

这是常规的Google DNS设置:

8.8.8.8
8.8.4.4

本文收集自互联网,转载请注明来源。

如有侵权,请联系[email protected] 删除。

编辑于
0

我来说两句

0条评论
登录后参与评论

相关文章

来自分类Dev

PG :: ConnectionBad错误

来自分类Dev

PG :: ConnectionBad:严重:用户“ alphauser”的密码身份验证失败

来自分类Dev

码头工人-PG :: ConnectionBad

来自分类Dev

capistrano,rails,PG :: ConnectionBad:fe_sendauth:未提供密码

来自分类Dev

PG :: ConnectionBad:无法连接到服务器(heroku)

来自分类Dev

PG :: ConnectionBad:无法连接到服务器:连接被拒绝

来自分类Dev

PG :: ConnectionBad严重:角色“ Myname”不存在

来自分类Dev

PG :: ConnectionBad:无法连接到服务器:连接被拒绝

来自分类Dev

PG :: ConnectionBad fe_sendauth:未提供密码

来自分类Dev

capistrano,rails,PG :: ConnectionBad:fe_sendauth:未提供密码

来自分类Dev

Heroku PG::ConnectionBad: FATAL: 不允许角色“xxxxxxxxxxx”登录

来自分类Dev

PG::ConnectionBad:致命:用户“rails_dev”的身份验证失败

来自分类Dev

生产中的 Rails 5:PG::ConnectionBad:致命:用户“postgres”与 Docker 的密码身份验证失败

来自分类Dev

重现`名称解析暂时失败`

来自分类Dev

Heroku + Rails + PG:ActiveRecord :: StatementInvalid(PG :: ConnectionBad:PQconsumeInput()SSL连接已意外关闭

来自分类Dev

netcat nc:getnameinfo:名称解析暂时失败

来自分类Dev

Rails-Postgres-无法连接到服务器:连接被拒绝(PG :: ConnectionBad)

来自分类Dev

频繁的PG :: ConnectionBad:RDS和rails / activerecord的连接关闭错误

来自分类Dev

PG :: ConnectionBad严重:不允许角色“ BetBook3”登录

来自分类Dev

Rails:fe_sendauth:没有提供来自Ruby的密码(PG :: ConnectionBad),但在Rails中可以

来自分类Dev

PG :: ConnectionBad:运行导出DATABASE_URL = postgres:// $(whoami)后无法翻译主机名错误

来自分类Dev

无法连接到服务器:没有这样的文件或目录(PG :: ConnectionBad)

来自分类Dev

耙子流产了!PG :: ConnectionBad:fe_sendauth:未提供密码sinatra

来自分类Dev

PostgreSQL数据库迁移错误:PG :: ConnectionBad:fe_sendauth:未提供密码

来自分类Dev

Rails 每当 rake 中止时!PG::ConnectionBad: fe_sendauth: 没有提供密码

来自分类Dev

耙子中止!PG::ConnectionBad: fe_sendauth: 没有提供密码

来自分类Dev

瑞克任务中收到“ ActiveRecord :: StatementInvalid:PG :: ConnectionBad:PQconsumeInput()无法从服务器接收数据:连接超时”

来自分类Dev

Heroku rake 中止(PG::ConnectionBad:无法连接到服务器:没有这样的文件或目录)

来自分类Dev

升级到Debian Buster后,名称解析暂时失败

Related 相关文章

  1. 1

    PG :: ConnectionBad错误

  2. 2

    PG :: ConnectionBad:严重:用户“ alphauser”的密码身份验证失败

  3. 3

    码头工人-PG :: ConnectionBad

  4. 4

    capistrano,rails,PG :: ConnectionBad:fe_sendauth:未提供密码

  5. 5

    PG :: ConnectionBad:无法连接到服务器(heroku)

  6. 6

    PG :: ConnectionBad:无法连接到服务器:连接被拒绝

  7. 7

    PG :: ConnectionBad严重:角色“ Myname”不存在

  8. 8

    PG :: ConnectionBad:无法连接到服务器:连接被拒绝

  9. 9

    PG :: ConnectionBad fe_sendauth:未提供密码

  10. 10

    capistrano,rails,PG :: ConnectionBad:fe_sendauth:未提供密码

  11. 11

    Heroku PG::ConnectionBad: FATAL: 不允许角色“xxxxxxxxxxx”登录

  12. 12

    PG::ConnectionBad:致命:用户“rails_dev”的身份验证失败

  13. 13

    生产中的 Rails 5:PG::ConnectionBad:致命:用户“postgres”与 Docker 的密码身份验证失败

  14. 14

    重现`名称解析暂时失败`

  15. 15

    Heroku + Rails + PG:ActiveRecord :: StatementInvalid(PG :: ConnectionBad:PQconsumeInput()SSL连接已意外关闭

  16. 16

    netcat nc:getnameinfo:名称解析暂时失败

  17. 17

    Rails-Postgres-无法连接到服务器:连接被拒绝(PG :: ConnectionBad)

  18. 18

    频繁的PG :: ConnectionBad:RDS和rails / activerecord的连接关闭错误

  19. 19

    PG :: ConnectionBad严重:不允许角色“ BetBook3”登录

  20. 20

    Rails:fe_sendauth:没有提供来自Ruby的密码(PG :: ConnectionBad),但在Rails中可以

  21. 21

    PG :: ConnectionBad:运行导出DATABASE_URL = postgres:// $(whoami)后无法翻译主机名错误

  22. 22

    无法连接到服务器:没有这样的文件或目录(PG :: ConnectionBad)

  23. 23

    耙子流产了!PG :: ConnectionBad:fe_sendauth:未提供密码sinatra

  24. 24

    PostgreSQL数据库迁移错误:PG :: ConnectionBad:fe_sendauth:未提供密码

  25. 25

    Rails 每当 rake 中止时!PG::ConnectionBad: fe_sendauth: 没有提供密码

  26. 26

    耙子中止!PG::ConnectionBad: fe_sendauth: 没有提供密码

  27. 27

    瑞克任务中收到“ ActiveRecord :: StatementInvalid:PG :: ConnectionBad:PQconsumeInput()无法从服务器接收数据:连接超时”

  28. 28

    Heroku rake 中止(PG::ConnectionBad:无法连接到服务器:没有这样的文件或目录)

  29. 29

    升级到Debian Buster后,名称解析暂时失败

热门标签

归档