#24838: Cannot run migrate with PostGIS on Heroku -- Django 1.8.2
-------------------------------+--------------------
     Reporter:  aschn          |      Owner:  nobody
         Type:  Uncategorized  |     Status:  new
    Component:  Uncategorized  |    Version:  1.8
     Severity:  Normal         |   Keywords:
 Triage Stage:  Unreviewed     |  Has patch:  0
Easy pickings:  0              |      UI/UX:  0
-------------------------------+--------------------
 When upgrading to Django 1.8.1 with PostGIS on Heroku last week, I ran
 into a similar issue to tickets #24797, #24791, and #24795. So I was
 excited to see the fix in the 1.8.2 release!

 But running 1.8.2 now, I'm still seeing a variant of the problem.

 {{{heroku run ./manage.py migrate}}} and {{{heroku run ./manage.py
 shell}}} work and yield expected results, no errors raised. But a
 "permission denied" message is present in the logs:

 {{{
 $ heroku logs
 2015-05-21T19:03:46.210746+00:00 heroku[api]: Starting process with
 command `./manage.py migrate` by [email protected]
 2015-05-21T19:03:57.695048+00:00 heroku[run.9837]: Awaiting client
 2015-05-21T19:03:57.736396+00:00 heroku[run.9837]: Starting process with
 command `./manage.py migrate`
 2015-05-21T19:03:58.067165+00:00 heroku[run.9837]: State changed from
 starting to up
 2015-05-21T19:04:02Z app[postgres.2450]: [DATABASE] permission denied for
 database "postgres"
 Detail: User does not have CONNECT privilege.
 2015-05-21T19:04:02Z app[postgres.2454]: [DATABASE] extension "postgis"
 already exists, skipping
 2015-05-21T19:04:02Z app[postgres.2454]: [DATABASE] statement: CREATE
 EXTENSION IF NOT EXISTS postgis
 2015-05-21T19:04:05Z app[postgres.2452]: [DATABASE] could not receive data
 from client: Connection reset by peer
 2015-05-21T19:04:06.110871+00:00 heroku[run.9837]: State changed from up
 to complete
 2015-05-21T19:04:06.094695+00:00 heroku[run.9837]: Process exited with
 status 0
 }}}

 At this point, is it a Django or Heroku issue? Heroku was unhelpful when I
 raised the issue with them previously, but I'd happily try again if the
 Django community deems this resolved on their side.

--
Ticket URL: <https://code.djangoproject.com/ticket/24838>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/048.a5a145cf53e96356095e7f551b0009b3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to