Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trialMoe Khatib
5,293 PointsHeroku db:migrate Error
I am still a rails beginner and I am trying to deploy an app to heroku but when trying to run the:
heroku run rake db:migrate
I am getting an error:
PG::DataCorrupted: ERROR: could not read block 6 in file "base/18350/12684": read only 0 of 8192 bytes
: CREATE TABLE "searches" ("id" serial primary key, "city_id" integer, "num_weeks" integer, "num_seats" integer, "start_date" date, "student_name" character varying(255), "program_id" integer, "user_id" integer, "created_at" timestamp, "updated_at" timestamp)
rake aborted!
StandardError: An error has occurred, this and all later migrations canceled:
Here is the migration:
class CreateSearches < ActiveRecord::Migration
def change
create_table :searches do |t|
t.integer :city_id
t.integer :num_weeks
t.integer :num_seats
t.date :start_date
t.string :student_name
t.integer :program_id
t.integer :user_id
t.timestamps
end
end
end
I am not quite sure what is going on, any help would be appreciate it.
2 Answers
Stone Preston
42,016 Pointshmm this post on stack overflow might suggest its a problem with Heroku. several people getting the same error around the same time.
Iyad Horani
Courses Plus Student 6,141 PointsI was having the same issue yesterday and contacted heroku support team, the database is working again, bellow is the response
Unfortunately, it looks like there was an issue with your database last night which caused an outage for a couple hours, however it's since been recovered by one of our on-call database engineers. This issue wasn't caused by you at all, it was a hardware failure on the host server.
Hope this helps.
Moe Khatib
5,293 PointsMoe Khatib
5,293 PointsThank you Stone, I will keep an eye on it.
Stone Preston
42,016 PointsStone Preston
42,016 Pointsyou might also keep an eye on heroku's status