#21504 closed Cleanup/optimization (fixed)
GeoDjango swallows connection errors as version failures
| Reported by: | Owned by: | Baptiste Mispelon | |
|---|---|---|---|
| Component: | GIS | Version: | 1.6 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | yes | UI/UX: | no |
Description
I'm getting a:
django.core.exceptions.ImproperlyConfigured: Cannot determine PostGIS version for database "glare". GeoDjango requires at least PostGIS version 1.3. Was the database created from a spatial database template?
but, when I look at the actual exception thrown by the version check:
./manage.py syncdbcould not connect to server: Connection refused
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5432?
It'd be great to be slightly more smart about this :)
Change History (3)
comment:1 by , 11 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
| Triage Stage: | Unreviewed → Accepted |
| Type: | Uncategorized → Cleanup/optimization |
comment:2 by , 11 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
The problem happens because we catch a wide range of errors when trying to determine the postgis version [1].
We could probably be smarter about what we catch.
[1] https://github.com/django/django/blob/master/django/contrib/gis/db/backends/postgis/operations.py#L261