Heroku could not connect to server: 'Connection refused' when deploying a Rails 3.2.3 app on cedar stack [closed]

Question

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.

Closed 8 years ago.

Since yesterday it worked, but this morning, I can't figure out why, my app on heroku is unable to connect to the shared DB. I can't even do a simple:

$ heroku run rake db:reset

(I'm on a cedar stack). And this is the console trace dump:

** Invoke db:reset (first_time)
** Invoke environment (first_time)
** Execute environment
rake aborted!
could not connect to server: Connection refused
    Is the server running on host "ec2-107-22-222-231.compute-1.amazonaws.com" and accepting
    TCP/IP connections on port 5432?
/app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.3/lib/active_record/connection_adapters/postgresql_adapter.rb:1194:in `initialize'
/app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.3/lib/active_record/connection_adapters/postgresql_adapter.rb:1194:in `new'
/app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.3/lib/active_record/connection_adapters/postgresql_adapter.rb:1194:in `connect'
/app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.3/lib/active_record/connection_adapters/postgresql_adapter.rb:329:in `initialize'
...
Tasks: TOP => db:reset => environment

Any idea, please?

--UPDATE---

They just updated their status at https://status.heroku.com/ with incident 375: https://status.heroku.com/incidents/375

...I guess I just have to wait.

--UPDATE---

After 3 hours the error message changed into:

could not translate host name "ec2-107-22-222-231.compute-1.amazonaws.com" to address: Name or service not known (PG::Error)

At least now I know for sure that Heroku guys are working.

Answer 1

Same problem here. It was working 'til yesterday.

Dedicated production databases should be operational. We're continuing recovery of shared development databases and Crane and Kappa beta databases. Varnish remains temporarily disabled on the Bamboo HTTP stack.

Yeah, apparently just waiting is the answer here.