Re: [GENERAL] changing port numbers so pgbouncer can read geoserver and postgres
On Fri, Nov 1, 2013 at 9:29 AM, Birta Levente wrote: > I don't know what is this geoserver, but this port 8080 I think it's not > relevant in this. > I might be able to help: http://geoserver.org/display/GEOS/Welcome. GeoServer is a Java web application that retrieves GIS data (as in PostGIS in the realm of PostgreSQL) and servers it up in standard formats. This allows for greater interoperability than would be possible with only the PostgreSQL/PostGIS database since many clients cannot communicate with PostgreSQL directly. So the desired request chain is most likely something like this: Client (E.g., ArcMap, a web page with OpenLayers or Leaflet, another web application that processes the data somehow) --> GeoServer (running on port 8080) --> pgBouncer --> PostgreSQL (with PostGIS extension) It looks like GeoServer is having a problem connecting to PostgreSQL, so I think you're right. It's either between GeoServer and pgBouncer or pgBouncer and PostgreSQL. Hopefully, that clears up some points of confusion.
Re: [GENERAL] changing port numbers so pgbouncer can read geoserver and postgres
On 11/2/2013 9:56 AM, Adrian Klaver wrote: Well, what I showed is supposition on my part and is not necessarily the truth. Part of the issue is discerning the truth of how information flows through the system, in particular what exactly is/are the application(s) talking to Postgres/pgBouncer. It is still unknown, at least to me, where geoserver fits into the above and whether it is connecting directly to Postgres or going through the Tomcat server. Once some sort of schematic for connection(current, desired) is provided then it would be possible to do as you suggest. The confusion from what I am following is that the "(application using PostgreSQL) --> port 5432 (Postgres)" part is not known. tomcat itself has no database layer. its purely a web appserver. the java apps running on tomcat use JDBC to connect to a database server like postgresql. -- john r pierce 37N 122W somewhere on the middle of the left coast -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] changing port numbers so pgbouncer can read geoserver and postgres
On 11/02/2013 08:11 AM, Rowan Collins wrote: On 01/11/2013 13:58, Adrian Klaver wrote: On 11/01/2013 06:29 AM, Birta Levente wrote: If I am following correctly the OP chain of connections as originally set up and I believe still is: End User --> port 8080 (Tomcat) --> port 5432 (Postgres) and they are trying to get to End User --> port 808 (Tomcat) --> port 6432 (pgBouncer) --> port 5432 (Postgres) That sounds right, but port 8080 is definitely irrelevant in this case, as it is just a detail of the application - it could just as well be a desktop application with no associated network port. For the sake of what needs to be configured, the chain is just: Before: (application using PostgreSQL) --> port 5432 (Postgres) After: (application using PostgreSQL) --> port 6432 (pgBouncer) --> port 5432 (Postgres) Well, what I showed is supposition on my part and is not necessarily the truth. Part of the issue is discerning the truth of how information flows through the system, in particular what exactly is/are the application(s) talking to Postgres/pgBouncer. It is still unknown, at least to me, where geoserver fits into the above and whether it is connecting directly to Postgres or going through the Tomcat server. Once some sort of schematic for connection(current, desired) is provided then it would be possible to do as you suggest. The confusion from what I am following is that the "(application using PostgreSQL) --> port 5432 (Postgres)" part is not known. So there are two things to configure: a) in the application, tell it to connect to port 6432 for its database connections, instead of port 5432 b) in pgBouncer, make sure it can connect properly to the postgres server on port 5432 It sounds like (b) is currently the issue. -- Adrian Klaver adrian.kla...@gmail.com -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] changing port numbers so pgbouncer can read geoserver and postgres
On 01/11/2013 13:58, Adrian Klaver wrote: On 11/01/2013 06:29 AM, Birta Levente wrote: geoserver is using port 8080, some how they don't seem to be speaking to each other. I don't know what is this geoserver, but this port 8080 I think it's not relevant in this. If I am following correctly the OP chain of connections as originally set up and I believe still is: End User --> port 8080 (Tomcat) --> port 5432 (Postgres) and they are trying to get to End User --> port 808 (Tomcat) --> port 6432 (pgBouncer) --> port 5432 (Postgres) That sounds right, but port 8080 is definitely irrelevant in this case, as it is just a detail of the application - it could just as well be a desktop application with no associated network port. For the sake of what needs to be configured, the chain is just: Before: (application using PostgreSQL) --> port 5432 (Postgres) After: (application using PostgreSQL) --> port 6432 (pgBouncer) --> port 5432 (Postgres) So there are two things to configure: a) in the application, tell it to connect to port 6432 for its database connections, instead of port 5432 b) in pgBouncer, make sure it can connect properly to the postgres server on port 5432 It sounds like (b) is currently the issue. -- Rowan Collins [IMSoP] -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] changing port numbers so pgbouncer can read geoserver and postgres
On 11/01/2013 06:29 AM, Birta Levente wrote: geoserver is using port 8080, some how they don't seem to be speaking to each other. I don't know what is this geoserver, but this port 8080 I think it's not relevant in this. If I am following correctly the OP chain of connections as originally set up and I believe still is: End User --> port 8080 (Tomcat) --> port 5432 (Postgres) and they are trying to get to End User --> port 808 (Tomcat) --> port 6432 (pgBouncer) --> port 5432 (Postgres) -- Adrian Klaver adrian.kla...@gmail.com -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] changing port numbers so pgbouncer can read geoserver and postgres
On 01/11/2013 14:44, si24 wrote: I get this error in geoserver :Original exception error: Unable to obtain connection: Cannot create PoolableConnectionFactory (ERROR: client_login_timeout (server down)) when I change the store port number from 5432 to 6432 so that geoserver can use the pgbouncer instead of calling on the postgres db directly. Not sure if thats the way i'm suppose to do it. it should be ok. have you specified in your pgbouncer.ini auth_type and auth_file ? And I think you really need to check pgbouncer log !!! 5432 is the port that my postgresql is working from and 6432 is where my pgbouncer is calling from. pgbouncer is not calling from 6432!!! postgresql server listening on port 5432 pgbouncer listening on port 6432 geoserver is using port 8080, some how they don't seem to be speaking to each other. I don't know what is this geoserver, but this port 8080 I think it's not relevant in this. -- View this message in context: http://postgresql.1045698.n5.nabble.com/changing-port-numbers-so-pgbouncer-can-read-geoserver-and-postgres-tp5776631.html Sent from the PostgreSQL - general mailing list archive at Nabble.com. smime.p7s Description: S/MIME Cryptographic Signature
[GENERAL] changing port numbers so pgbouncer can read geoserver and postgres
I get this error in geoserver :Original exception error: Unable to obtain connection: Cannot create PoolableConnectionFactory (ERROR: client_login_timeout (server down)) when I change the store port number from 5432 to 6432 so that geoserver can use the pgbouncer instead of calling on the postgres db directly. Not sure if thats the way i'm suppose to do it. 5432 is the port that my postgresql is working from and 6432 is where my pgbouncer is calling from. geoserver is using port 8080, some how they don't seem to be speaking to each other. -- View this message in context: http://postgresql.1045698.n5.nabble.com/changing-port-numbers-so-pgbouncer-can-read-geoserver-and-postgres-tp5776631.html Sent from the PostgreSQL - general mailing list archive at Nabble.com. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
