So apparently, PostGIS 2.1.3 came with a security feature that turned all GDAL drivers off. A simple edit to the environment file and a restart fixed the issue.
Add this to your environment file. On Debian it's located in /etc/postgresql/9.3/main/ POSTGIS_GDAL_ENABLED_DRIVERS=ENABLE_ALL Keep in mind that this was disabled for a reason. Seeing that our project is not live, and our users will not be allowed to enter their own queries, I think it's safe for me to turn this back on. Here's the release notes for this update: http://postgis.net/2014/05/19/postgis-2.0.6_and_2.1.3 -Jayson On Thu, Jun 5, 2014 at 11:23 AM, Jayson Gallardo <[email protected]> wrote: > We just ran a package update or our Debian machine last night, and now > this morning our app doesn't work. I've narrowed it down to this: > > ERROR: rt_raster_to_gdal: Could not load the output GDAL driver > production=# select postgis_full_version(); > > postgis_full_version > > > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > POSTGIS="2.1.3 r12547" GEOS="3.4.2-CAPI-1.8.2 r3921" PROJ="Rel. 4.8.0, 6 > March 2012" GDAL="GDAL 1.10.1, released 2013/08/26" LIBXML="2.9.1" > LIBJSON="UNKNOWN" (core procs from "2.1.2 r12389" need upgrade) TOPOLOGY > RASTER (raster procs from "2.1.2 r12389" need upgrade) > (1 row) > > Thanks in advance, > Jayson >
_______________________________________________ postgis-users mailing list [email protected] http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
