All,
I upgraded my database to postgres 9.3 and postGIS 2.1, but now my geoserver 2,1 can't seem to connect to the database. Did I upgrade too far?
Thanks,
Steve
--
Stephen Crawford
Center for Environmental Informatics
The Pennsylvania State University
Here is the error message:
java.lang.RuntimeException: Error getting FeatureType, this should never happen!
Error getting FeatureType, this should never happen!
null
Unable to obtain connection: Cannot create PoolableConnectionFactory (FATAL: no pg_hba.conf entry for host "127.0.0.1", user "geoweb", database "wheatgrid", SSL off)
Cannot create PoolableConnectionFactory (FATAL: no pg_hba.conf entry for host "127.0.0.1", user "geoweb", database "wheatgrid", SSL off)
FATAL: no pg_hba.conf entry for host "127.0.0.1", user "geoweb", database "wheatgrid", SSL off
The curious thing is that there IS a correct entry in pg_hba.conf, and I am able to connect to the database via pqsl. That's why I am wonering if it is a geoserver problem.
On 9/23/2013 11:38 AM, Stephen Crawford wrote:
All,
I upgraded my database to postgres 9.3 and postGIS 2.1, but now my
geoserver 2,1 can't seem to connect to the database. Did I upgrade too far?
Thanks,
Steve
--
Stephen Crawford
Center for Environmental Informatics
The Pennsylvania State University
src176@anonymised.com
814.865.9905
On Mon, Sep 23, 2013 at 4:38 PM, Stephen Crawford <src176@anonymised.com> wrote:
All,
I upgraded my database to postgres 9.3 and postGIS 2.1, but now my
geoserver 2,1 can't seem to connect to the database. Did I upgrade too far?
Yes, I'm afraid you did. I believe you need at least GeoServer 2.2 to work
against those versions,
maybe 2.3 (going by vague memories, high chance of being wrong).
However, just say your other message, and it seems you are having problems
setting up
the database connection, which is something entirely different (the issues
I'm thinking about
will show up after you successfully got the connection working, because
some of the functions
we're calling are not there anymore in postgis 2.x, there is a legacy.sql
that you can run
again the db to add them back).
Cheers
Andrea
--
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
Hi Andrea,
I don’t mind upgrading to 2.4…my hope is the connection problem will be solved if I do so?
Thanks,
Steve
···
On 9/23/2013 12:12 PM, Andrea Aime wrote:
On Mon, Sep 23, 2013 at 4:38 PM, Stephen Crawford <src176@anonymised.com> wrote:
All,
I upgraded my database to postgres 9.3 and postGIS 2.1, but now my
geoserver 2,1 can’t seem to connect to the database. Did I upgrade too far?
Yes, I’m afraid you did. I believe you need at least GeoServer 2.2 to work against those versions,
maybe 2.3 (going by vague memories, high chance of being wrong).
However, just say your other message, and it seems you are having problems setting up
the database connection, which is something entirely different (the issues I’m thinking about
will show up after you successfully got the connection working, because some of the functions
we’re calling are not there anymore in postgis 2.x, there is a legacy.sql that you can run
again the db to add them back).
Cheers
Andrea
–
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
[http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk](http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk)
_______________________________________________
Geoserver-users mailing list
[Geoserver-users@lists.sourceforge.net](mailto:Geoserver-users@lists.sourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geoserver-users](https://lists.sourceforge.net/lists/listinfo/geoserver-users)
--
Stephen Crawford
Center for Environmental Informatics
The Pennsylvania State University
[src176@anonymised.com](mailto:src176@anonymised.com)
814.865.9905
On Mon, Sep 23, 2013 at 5:16 PM, Stephen Crawford <src176@anonymised.com> wrote:
Hi Andrea,
I don't mind upgrading to 2.4....my hope is the connection problem will be
solved if I do so?
Given the error messages you've reported, it seems something that needs a
postgresql fix to be solved,
instead of a geoserver upgrade, but I might be wrong
Cheers
Andrea
--
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------