PG :: ConnectionBad,无法连接到服务器

问题描述 投票:1回答:1

我在使用Rails应用程序时遇到问题,其他几个正在研究中。 我只是克隆了存储库,而执行rails db:migrate或尝试到达页面(在服务器运行时)都会导致此错误:

Started GET "/" for 127.0.0.1 at 2017-06-18 11:58:41 +0100

PG::ConnectionBad (could not connect to server: Cannot assign requested address (0x00002741/10049)
    Is the server running on host "0.0.0.0" and accepting
    TCP/IP connections on port 6543?
):

pg-0.19.0-x64 (mingw32) lib/pg.rb:45:in 'initialize'
pg-0.19.0-x64 (mingw32) lib/pg.rb:45:in 'new'
pg-0.19.0-x64 (mingw32) lib/pg.rb:45:in 'connect'
activerecord (5.1.1) lib/active_record/connection_adapters/postgresql_adapter.rb:701:in 'connect'
activerecord (5.1.1) lib/active_record/connection_adapters/postgresql_adapter.rb:220:in 'initialize'
activerecord (5.1.1) lib/active_record/connection_adapters/postgresql_adapter.rb:38:in 'new'
activerecord (5.1.1) lib/active_record/connection_adapters/postgresql_adapter.rb:38:in 'postgresql_connection'
activerecord (5.1.1) lib/active_record/connection_adapters/abstract/connection_pool.rb:759:in 'new_connection'
activerecord (5.1.1) lib/active_record/connection_adapters/abstract/connection_pool.rb:803:in 'checkout_new_connection'
activerecord (5.1.1) lib/active_record/connection_adapters/abstract/connection_pool.rb:782:in 'try_to_checkout_new_connection'
activerecord (5.1.1) lib/active_record/connection_adapters/abstract/connection_pool.rb:743:in 'acquire_connection'
activerecord (5.1.1) lib/active_record/connection_adapters/abstract/connection_pool.rb:500:in 'checkout'
activerecord (5.1.1) lib/active_record/connection_adapters/abstract/connection_pool.rb:374:in 'connection'
activerecord (5.1.1) lib/active_record/connection_adapters/abstract/connection_pool.rb:931:in 'retrieve_connection'
activerecord (5.1.1) lib/active_record/connection_handling.rb:116:in 'retrieve_connection'
activerecord (5.1.1) lib/active_record/connection_handling.rb:88:in 'connection'
activerecord (5.1.1) lib/active_record/migration.rb:562:in 'connection'
activerecord (5.1.1) lib/active_record/migration.rb:553:in 'call'
actionpack (5.1.1) lib/action_dispatch/middleware/callbacks.rb:26:in 'block in call'
activesupport (5.1.1) lib/active_support/callbacks.rb:97:in 'run_callbacks'
actionpack (5.1.1) lib/action_dispatch/middleware/callbacks.rb:24:in 'call'
actionpack (5.1.1) lib/action_dispatch/middleware/executor.rb:12:in 'call'
actionpack (5.1.1) lib/action_dispatch/middleware/debug_exceptions.rb:59:in 'call'
web-console (3.5.1) lib/web_console/middleware.rb:135:in 'call_app'
web-console (3.5.1) lib/web_console/middleware.rb:28:in 'block in call'
web-console (3.5.1) lib/web_console/middleware.rb:18:in 'catch'
web-console (3.5.1) lib/web_console/middleware.rb:18:in 'call'
actionpack (5.1.1) lib/action_dispatch/middleware/show_exceptions.rb:31:in 'call'
railties (5.1.1) lib/rails/rack/logger.rb:36:in 'call_app'
railties (5.1.1) lib/rails/rack/logger.rb:24:in 'block in call'
activesupport (5.1.1) lib/active_support/tagged_logging.rb:69:in 'block in tagged'
activesupport (5.1.1) lib/active_support/tagged_logging.rb:26:in 'tagged'
activesupport (5.1.1) lib/active_support/tagged_logging.rb:69:in 'tagged'
railties (5.1.1) lib/rails/rack/logger.rb:24:in 'call'
sprockets-rails (3.2.0) lib/sprockets/rails/quiet_assets.rb:13:in 'call'
actionpack (5.1.1) lib/action_dispatch/middleware/remote_ip.rb:79:in 'call'
actionpack (5.1.1) lib/action_dispatch/middleware/request_id.rb:25:in 'call'
rack (2.0.3) lib/rack/method_override.rb:22:in 'call'
rack (2.0.3) lib/rack/runtime.rb:22:in 'call'
activesupport (5.1.1) lib/active_support/cache/strategy/local_cache_middleware.rb:27:in 'call'
actionpack (5.1.1) lib/action_dispatch/middleware/executor.rb:12:in 'call'
actionpack (5.1.1) lib/action_dispatch/middleware/static.rb:125:in 'call'
rack (2.0.3) lib/rack/sendfile.rb:111:in 'call'
railties (5.1.1) lib/rails/engine.rb:522:in 'call'
puma (3.9.1) lib/puma/configuration.rb:224:in 'call'
puma (3.9.1) lib/puma/server.rb:602:in 'handle_request'
puma (3.9.1) lib/puma/server.rb:435:in 'process_client'
puma (3.9.1) lib/puma/server.rb:299:in 'block in run'
puma (3.9.1) lib/puma/thread_pool.rb:120:in 'call'
puma (3.9.1) lib/puma/thread_pool.rb:120:in 'block in spawn_thread'

我读过类似的文章,都说过要重新启动postgres,但是在Windows上有点混乱,所以我重新启动了笔记本电脑,但没有解决任何问题。 我也尝试过重新克隆仓库。

请注意,其他Rails项目也可以工作,这使我认为这与database.yml有关,但我真的不知道该怎么做。 干杯

ruby-on-rails database connection
1个回答
2
投票

确保您的postgresql服务正在运行,然后确保已创建应用程序所需的数据库,可以执行rake db:create

另请参阅您的database.yml。 默认配置是这样的

development:
<<: *default
database: yourappname_development

在那里,您还可以添加连接到Postgres所需的信息,例如,

port: 
username: 
password: 
hostname: 

您可以从另一个正在运行的Rails应用程序中举例

© www.soinside.com 2019 - 2024. All rights reserved.