Re: [Postgres-xc-general] createdb: database creation failed: ERROR: Failed to get pooled connections

[Abbas B. <abb...@en...>]

I just spotted another mistake in data node creation. You are creating both
the data nodes on both the coordinators with the default IP i.e. 127.0.0.1
which is not true for datanode1 when created on coordinator2. Similarly it
is not true for datanode2 on coordinator1. It would be good idea to create
both data nodes by explicitly specifying the IP addresses.

So the queries should look something like this.

psql -c "CREATE NODE datanode1 WITH (HOST = 'IP_OF_datanode1', TYPE =
'datanode', PORT = 15432)" postgres
psql -c "CREATE NODE datanode2 WITH (HOST = 'IP_OF_datanode2', TYPE =
'datanode', PORT = 15433)" postgres
psql -c "CREATE NODE coordinator1 WITH (HOST = '10.152.14.24', type =
'coordinator', PORT = 5432);" postgres
psql -c "CREATE NODE coordinator2 WITH (HOST = '10.152.14.25', type =
'coordinator', PORT = 5432);" postgres

If this does not work and gives the same error please provide the output of

psql -c "select oid,* from pgxc_node;" postgres

by running on the coordinator2.

On Fri, Jun 22, 2012 at 7:06 PM, Neil Mooney <nm...@xu...> wrote:

> Thanks to Magorn and Abbass for their input.
>
> I followed your advice RE: creating new coordinator nodes in the db with
> the following query on both nodes:
>
> psql -c "DROP NODE coordinator1" postgres
> psql -c "DROP NODE coordinator2" postgres
> psql -c "CREATE NODE coordinator1 WITH (HOST = '10.152.14.24', type =
> 'coordinator', PORT = 5432);" postgres
> psql -c "CREATE NODE coordinator2 WITH (HOST = '10.152.14.25', type =
> 'coordinator', PORT = 5432);" postgres
> psql -c "SELECT pgxc_pool_reload()" postgres
>
> I am still seeing a problem, logfile indicates connectivity between the
> two data nodes, telnet-ing the port seems to work ok.
>
> [postgres@las1-app015 ~]$ cat logfile
>
> LOG:  database system was interrupted; last known up at 2012-06-22
> 13:31:58 UTC
> LOG:  database system was not properly shut down; automatic recovery in
> progress
> LOG:  record with zero length at 0/1776A90
> LOG:  redo is not required
> LOG:  autovacuum launcher started
> LOG:  database system is ready to accept connections
> LOG:  database system was interrupted; last known up at 2012-06-22
> 13:32:20 UTC
> LOG:  database system was not properly shut down; automatic recovery in
> progress
> LOG:  redo starts at 0/177F970
> LOG:  record with zero length at 0/177FB60
> LOG:  redo done at 0/177FB20
> LOG:  last completed transaction was at log time 2012-06-22
> 13:34:59.977913+00
> LOG:  autovacuum launcher started
> LOG:  database system is ready to accept connections
> LOG:  incomplete startup packet
> LOG:  incomplete startup packet
> LOG:  failed to connect to Datanode
> WARNING:  can not connect to node 16384
> LOG:  failed to acquire connections
> STATEMENT:  CREATE DATABASE test;
>
> ERROR:  Failed to get pooled connections
> STATEMENT:  CREATE DATABASE test;
>
> [postgres@las1-app015 ~]$ psql -c "select oid,node_name from pgxc_node;"
> postgres
>  oid  |  node_name
> -------+--------------
>  11129 | coordinator2
>  16384 | datanode1
>  16385 | datanode2
>  24583 | coordinator1
> (4 rows)
>
> [postgres@las1-app015 ~]$ telnet las1-app014 15432
> Trying 10.152.14.24...
> Connected to las1-app014.
> Escape character is '^]'.
> ^]
>
> telnet> quit
> Connection closed.
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>



-- 
--
Abbas
Architect
EnterpriseDB Corporation
The Enterprise PostgreSQL Company

Phone: 92-334-5100153

Website: www.enterprisedb.com
EnterpriseDB Blog: http://blogs.enterprisedb.com/
Follow us on Twitter: http://www.twitter.com/enterprisedb

This e-mail message (and any attachment) is intended for the use of
the individual or entity to whom it is addressed. This message
contains information from EnterpriseDB Corporation that may be
privileged, confidential, or exempt from disclosure under applicable
law. If you are not the intended recipient or authorized to receive
this for the intended recipient, any use, dissemination, distribution,
retention, archiving, or copying of this communication is strictly
prohibited. If you have received this e-mail in error, please notify
the sender immediately by reply e-mail and delete this message.