Heroku was unable to connect to the server: "Connection refused" when deploying Rails 3.2.3 application on the cedar stack

Question

Since yesterday, it worked, but this morning I can’t understand why my heroku application cannot connect to the shared database. I can't even do 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 simply updated their status at https://status.heroku.com/ with incident 375: https://status.heroku.com/incidents/375

... I think I just need to wait.

- UPDATE ---

After 3 hours, the error message changed to:

 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. He worked already yesterday.

Dedicated production databases should be involved. We continue to restore the common development database and beta database of Crane and Kappa. Varnish remains temporarily disabled on the Bamboo HTTP stack.

Yes, apparently, just waiting for an answer here.