Geek Answers Handbook

Heroku db: migrate aborted

I am new to Ruby on Rails and heroku. I followed the steps in the video tutorial. I don’t think I did something else. However, I cannot run rake db: migrate on heroku while everything is working on my localhost: 3000. You can also talk in detail about the GEMFILE.lock and GEMFILE functions.

$ heroku run rake db:migrate Running `rake db:migrate` attached to terminal... up, run.9550 DEPRECATION WARNING: You have Rails 2.3-style plugins in vendor/plugins! Support for these plugins will be removed in Rails 4.0. Move them out and bundle them in your Gemfile, or fold them in to your app as lib/myplugin/* and config/initializers/myplugin.rb. See the release notes for more on this: http://weblog.rubyonrails.org/2012/1/4/rails-3-2-0-rc2-has-been-released. (called from <top (required)> at /app/Rakefile:7) DEPRECATION WARNING: You have Rails 2.3-style plugins in vendor/plugins! Support for these plugins will be removed in Rails 4.0. Move them out and bundle them in your Gemfile, or fold them in to your app as lib/myplugin/* and config/initializers/myplugin.rb. See the release notes for more on this: http://weblog.rubyonrails.org/2012/1/4/rails-3-2-0-rc2-has-been-released. (called from <top (required)> at /app/Rakefile:7) Connecting to database specified by DATABASE_URL rake aborted! could not translate host name "ec2-54-225-69-193.compute-1.amazonaws.com" to address: Temporary failure in name resolution /app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.13/lib/active_record/connection_adapters/postgresql_adapter.rb:1216:in `initialize' /app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.13/lib/active_record/connection_adapters/postgresql_adapter.rb:1216:in `new' /app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.13/lib/active_record/connection_adapters/postgresql_adapter.rb:1216:in `connect' /app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.13/lib/active_record/connection_adapters/postgresql_adapter.rb:324:in `initialize' /app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.13/lib/active_record/connection_adapters/postgresql_adapter.rb:28:in `new' /app/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.13/lib/active_record/connection_adapters/postgresql_adapter.rb:28:in `postgresql_connection'

Relevant Content of My GEMFILE

 group :production do gem 'pg' end group :development, :test do gem 'sqlite3' end

Relevant contents of my GEMFILE.lock

  sqlite3 (1.3.7) thor (0.18.0) tilt (1.3.6) treetop (1.4.12) polyglot polyglot (>= 0.3.1) tzinfo (0.3.37) uglifier (1.3.0) execjs (>= 0.3.0) multi_json (~> 1.0, >= 1.0.2) PLATFORMS ruby DEPENDENCIES coffee-rails (~> 3.2.1) jquery-rails pg rails (= 3.2.13) sass-rails (~> 3.2.3) sqlite3 uglifier (>= 1.0.3)
+6
source share
3 answers

That nothing is related to your code or ruby ​​on rails.

This is a DNS error, if you have a rails and db application inside Heroku (which is the default), then try to reach heroku support and just keep trying, as soon as dns is updated, it should work, but just in case, try contacting Heroku Support. they must be able to quickly solve the problem.

+4
source

I assume this is a temporary error caused by a problem with Heroku and not with your project. I would try it again once in a while.

I find this article to be a good introduction to hows and whys gemfiles (and gemfile.locks).

+1
source

Sometimes, when you create a project, "server instances" simply do not work correctly, for some reason the hero does not manage to work correctly. I also banged my head against the wall for hours to find out that everything is working fine when I create a new repo and start over with a new copy to the hero. This is one of the reasons I walked away from Heroku and just went to the source and got Amazon EC2, which, as you can see from the above error, is exactly what Heroku uses.

+1
source

More articles:


All Articles