subject:"Re\: Database migration error"

Re: Database migration error

2012-12-07 Thread Harper

Hi Andrew,

Yes, I was just making sure that the HEROKU_POSTGRESQL_color_URL was stored
as the primary database in DATABASE_URL. Just followed the instructions
here.https://devcenter.heroku.com/articles/heroku-postgresql#establish-primary-db

I ended up destroying and re-deploying my app, and for some reason I had no
problems migrating the db this time. Unplug it, and plug it back in, I
guess.

Harper

On Thursday, December 6, 2012 12:15:51 PM UTC-5, Andrew Lorente wrote:

Hi Harper,

I'm just looking for clarification on what you mean when you say I also
made sure to store it in the DATABASE_URL config var per Heroku's
instructions. What is it that you put there? Just your
HEROKU_POSTGRESQL_color_URL, or something else?

Andrew

On Thu, Dec 6, 2012 at 5:16 AM, Harper harpe...@gmail.com
javascript:wrote:

Thanks for the suggestion Neil, unfortunately I'm still getting the
database migration error!

On Wednesday, December 5, 2012 9:03:35 AM UTC-5, Neil Middleton wrote:

I've only seen this once before and found that removing the PG add-on
and re-adding it worked.

--
Neil

On Wednesday, 5 December 2012 at 13:50, Harper wrote:

I'm deploying an app to Heroku for the first time and keep receiving an
error when trying to migrate my database. I've looked at all the relevant
Heroku docs and asked around at Stack Overflow, but still no luck.

After pushing the code up (which is successful), I run the heroku run
rake db:migrate command and see the following:

rake aborted! FATAL: role is not permitted to log in,
followed by the trace which I've posted here.http://pastebin.com/U5PVUqxc

According to the guide on postgres
errorshttps://devcenter.heroku.com/articles/postgres-logs-errors#fatal-role-rolename,

this error means I don't have a database provisioned. But I know that I do,
because running heroku addons | grep POSTGRES returns the database/plan
the app is using. I also made sure to store it in the DATABASE_URL config
var per Heroku's instructions.

I haven't a clue what is going on, can anyone offer suggestions? Thank
you.

--
You received this message because you are subscribed to the Google
Groups Heroku group.

To unsubscribe from this group, send email to
heroku+un...@**googlegroups.com

For more options, visit this group at
http://groups.google.com/**group/heroku?hl=en_US?hl=enhttp://groups.google.com/group/heroku?hl=en_US?hl=en

--
You received this message because you are subscribed to the Google
Groups Heroku group.

To unsubscribe from this group, send email to
heroku+un...@googlegroups.com javascript:
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en_US?hl=en

--
You received this message because you are subscribed to the Google
Groups Heroku group.

To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en_US?hl=en

Re: Database migration error

2012-12-06 Thread Harper

Thanks for the suggestion Neil, unfortunately I'm still getting the 
database migration error!

On Wednesday, December 5, 2012 9:03:35 AM UTC-5, Neil Middleton wrote:

 I've only seen this once before and found that removing the PG add-on and 
 re-adding it worked.

 -- 
 Neil

 On Wednesday, 5 December 2012 at 13:50, Harper wrote:

 I'm deploying an app to Heroku for the first time and keep receiving an 
 error when trying to migrate my database. I've looked at all the relevant 
 Heroku docs and asked around at Stack Overflow, but still no luck.

 After pushing the code up (which is successful), I run the heroku run 
 rake db:migrate command and see the following:

 rake aborted! FATAL: role  is not permitted to log in, followed 
 by the trace which I've posted here. http://pastebin.com/U5PVUqxc

 According to the guide on postgres 
 errorshttps://devcenter.heroku.com/articles/postgres-logs-errors#fatal-role-rolename,
  
 this error means I don't have a database provisioned. But I know that I do, 
 because running heroku addons | grep POSTGRES returns the database/plan 
 the app is using. I also made sure to store it in the DATABASE_URL config 
 var per Heroku's instructions.

 I haven't a clue what is going on, can anyone offer suggestions? Thank you.


  -- 
 You received this message because you are subscribed to the Google
 Groups Heroku group.
  
 To unsubscribe from this group, send email to
 heroku+un...@googlegroups.com javascript:
 For more options, visit this group at
 http://groups.google.com/group/heroku?hl=en_US?hl=en
  
  
  

-- 
You received this message because you are subscribed to the Google
Groups Heroku group.

To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en_US?hl=en

Re: Database migration error

2012-12-06 Thread Andrew Lorente

Hi Harper,

Andrew

On Thu, Dec 6, 2012 at 5:16 AM, Harper harper.h...@gmail.com wrote:

Thanks for the suggestion Neil, unfortunately I'm still getting the
database migration error!

On Wednesday, December 5, 2012 9:03:35 AM UTC-5, Neil Middleton wrote:

I've only seen this once before and found that removing the PG add-on and
re-adding it worked.

--
Neil

On Wednesday, 5 December 2012 at 13:50, Harper wrote:

After pushing the code up (which is successful), I run the heroku run
rake db:migrate command and see the following:

rake aborted! FATAL: role is not permitted to log in,
followed by the trace which I've posted here.http://pastebin.com/U5PVUqxc

According to the guide on postgres
errorshttps://devcenter.heroku.com/articles/postgres-logs-errors#fatal-role-rolename,
this error means I don't have a database provisioned. But I know that I do,
because running heroku addons | grep POSTGRES returns the database/plan
the app is using. I also made sure to store it in the DATABASE_URL config
var per Heroku's instructions.