Earlier this week I got an email from Heroku that one of my postgres databases required maintenance. This is the email:
bot (Heroku Support)
Apr 25 14:02
Your database HEROKU_POSTGRESQL_COLOR_URL on <project_name> requires maintenance. During this period, your database credentials will become read-only. Once it has completed, your database URL will have changed, but we will update your app’s config variables accordingly. This automated maintenance is a necessary part of our Starter tier plans, Dev and Basic. Should you need more control over maintenance windows, a production database (Crane or higher) offers more control over database maintenance, as we are able to schedule them in advance and provide better tools for self-served maintenance. We expect maintenance to last just a few moments. We will update this ticket when maintenance begins, and again once it’s complete.
I’m fine with maintenance and the short notice. I do have a free plan in place as it is one of my many personal projects. What I found to be interesting is the following:
Once it has completed, your database URL will have changed, but we will update your app’s config variables accordingly.
I didn’t even know they could update the variables of my app without me! So I login to my Heroku account and see what the new credentials are, so I can update my project and check those changes into git.
Noted, copied, and pasted. Done. The new credentials are updated in my local project as well as my project origin. At this point I haven’t even checked to see if the website is even up yet. Turns out, it’s not up. The app keeps crashing. I check the logs with
heroku logs --tail and find something like following repeating:
2014-04-25T14:11:59+00:00 heroku[router]: at=error code=H10 desc=“App crashed” method=GET path=/ host=xxx.herokuapp.com fwd= dyno= queue= wait= connect= service= status=503 bytes=
The error message is not very helpful– yes I know the website keeps crashing, I can see that for myself! Even worse, googling it doesn’t yield any results to help fix my particular issue.
My initial thought was that this was an older rails project and something was outdated or something new was pushed accidentally. So after a long time of fiddling around with not just my code, error logs, various settings, Gemfile, etc– I notice something in the logs about a postgres connection failure with what appears to be my old credentials. I run the command
heroku config and get:
This is where I noticed that the values for
DATABASE_URL had the old credentials in it, while the
HEROKU_POSTGRESQL_COLOR_URL had the new values. So I updated
DATABASE_URL with the following command:
heroku pg:promote HEROKU_POSTGRESQL_COLOR_URL
See Heroku Postgres: Establish primary DB. Please replace COLOR in my variables with whatever is the name/color of you database.
This will update
DATABASE_URL to the new and correct credentials. After doing this my site was up and running again. This is something Heroku should have done automatically if they were going to make any changes on my behalf.
I hope this helps others, or even myself in the future!
Update 4/29/2014: A Heroku developer contacted me and looked into my problem for me. He stated that normally the DATABASE_URL will also get updated along with any changes. Although they weren’t able to find out why the changes didn’t propagate for me, they will monitor this kind situation in the future.