Recent changes to support-requests

#7 Postgres-XC crashes with failed to find proc 0x7fb0cb34f7c0 in ProcArray and sorry, too many clients already

2015-04-15T06:44:45.169000Z

attachment patch should fix this bug.

#7 Postgres-XC crashes with failed to find proc 0x7fb0cb34f7c0 in ProcArray and sorry, too many clients already

2014-11-05T16:45:15.359000Z

Dear Koichi,

I was hit by this bug too. Do you plan to apply the patch anytime soon?

According to wikipedia, the licensing should not be an issue here as XL uses MPL version 2.0:

http://en.wikipedia.org/wiki/Mozilla_Public_License

"In the absence of patents, MPL-licensed code can be freely used, altered, and redistributed. Versions with patented code can still be used, transferred, and even sold, but cannot be altered without special permission."

happily, it's not patented and I would take word 'use' as permission to apply it as a patch elsewhere as it is constrained to the 'component'.

But as usual with licensing it is confusing. Is there any chance to get a clear statement from XC and XL teams whether patches to already existing code in XC are moot if it comes to re-applying from MPL to BSD or there is chance for a mutual agreement to speed up development of both projects?

Cheers,
Chris.

Postgres-XC crashes with failed to find proc 0x7fb0cb34f7c0 in ProcArray and sorry, too many clients already

2014-10-21T11:05:52.972000Z

Hello,

I am really devastated. For the last week, week and half, I was trying to ran successfully almost all postgres-xc versions 1.1, 1.1.1, 1.2, 1.2.1...etc and the only one which runs without any problems was 1.0.4.
My setup is based on 4 AWS instances with Ubuntu 14.04 LTS on them.
2xData-Nodes 1xCordinator 1xGTM server. While I was strugling with it I tried many approaches like DL the code and compile it, install ubuntu package and so on.

Here is my problem and steps I do.
1. DL the code from sourceforge.net
2. unpak and do ./configure, make and make install
3. Initdb on all related hosts:

Cordinator
/usr/local/pgsql/bin/initdb -D /var/lib/postgres-xc/data --nodename cn1
DataNode1
/usr/local/pgsql/bin/initdb -D /var/lib/postgres-xc/data --nodename dn1
DataNode2
/usr/local/pgsql/bin/initdb -D /var/lib/postgres-xc/data --nodename dn2
GTM server
/usr/local/pgsql/bin/initgtm -Z gtm -D /var/lib/postgres-xc/data

Setting up the IP address of the GTM server on all nodes and start them with:
/usr/local/pgsql/bin/pg_ctl start -D /var/lib/postgres-xc/data -Z datanode -l /var/lib/postgres-xc/data/logfile
/usr/local/pgsql/bin/pg_ctl start -D /var/lib/postgres-xc/data -Z coordinator -l /var/lib/postgres-xc/data/logfile
/usr/local/pgsql/bin/gtm_ctl -Z gtm -D /var/lib/postgres-xc/data start
Adding nodes into cordinator:
postgres=# CREATE NODE dn1 WITH (HOST = '172.30.0.14', type = 'datanode', PORT = 5432);
postgres=# CREATE NODE dn2 WITH (HOST = '172.30.0.15', type = 'datanode', PORT = 5432);
postgres=# SELECT pgxc_pool_reload();

When I issue "createdb -h 172.30.0.11(cordinatorIP) -Upostgres-xc pgbench" from 5th node, it creates the DB on all nodes. Then I populate the DB with "pgbench -h 172.30.0.11 -i -s 10 -Upostgres-xc pgbench" and when i try to run any tests the whole setup crashes with:

starting vacuum...end.
starting vacuum pgbench_accounts...end.
Client 0 aborted in state 13: ERROR: failed to find GlobalTransaction for xid 10135
WARNING: unexpected EOF on datanode connection
Client 1 aborted in state 13: ERROR: sorry, too many clients already
transaction type: TPC-B (sort of)
scaling factor: 10
query mode: simple
number of clients: 2
number of threads: 2
duration: 3600 s
number of transactions actually processed: 126
tps = 42.505160 (including connections establishing)
tps = 42.612909 (excluding connections establishing)

On the coordinator node I am observing the folloging errors into log file:

LOG: failed to find proc 0x7fb0cb3f2480 in ProcArray
STATEMENT: drop table if exists pgbench_history
LOG: failed to find proc 0x7fb0cb3f2480 in ProcArray
STATEMENT: create table pgbench_history(tid int,bid int,aid int,delta int,mtime timestamp,filler char(22))
LOG: failed to find proc 0x7fb0cb3f2480 in ProcArray
STATEMENT: drop table if exists pgbench_tellers
LOG: failed to find proc 0x7fb0cb3f2480 in ProcArray
STATEMENT: create table pgbench_tellers(tid int not null,bid int,tbalance int,filler char(84)) with (fillfactor=100)
LOG: failed to find proc 0x7fb0cb3f2480 in ProcArray
STATEMENT: drop table if exists pgbench_accounts
LOG: failed to find proc 0x7fb0cb3f2480 in ProcArray
STATEMENT: create table pgbench_accounts(aid int not null,bid int,abalance int,filler char(84)) with (fillfactor=100)
LOG: failed to find proc 0x7fb0cb3f2480 in ProcArray
STATEMENT: drop table if exists pgbench_branches
LOG: failed to find proc 0x7fb0cb3f2480 in ProcArray
STATEMENT: create table pgbench_branches(bid int not null,bbalance int,filler char(88)) with (fillfactor=100)
LOG: failed to find proc 0x7fb0cb3f2480 in ProcArray
STATEMENT: commit
LOG: failed to find proc 0x7fb0cb3f2480 in ProcArray
STATEMENT: alter table pgbench_branches add primary key (bid)
LOG: failed to find proc 0x7fb0cb3f2480 in ProcArray
STATEMENT: alter table pgbench_tellers add primary key (tid)
LOG: failed to find proc 0x7fb0cb3f2480 in ProcArray
STATEMENT: alter table pgbench_accounts add primary key (aid)
LOG: failed to find proc 0x7fb0cb3f2480 in ProcArray
STATEMENT: truncate pgbench_history
ERROR: failed to find GlobalTransaction for xid 11378
STATEMENT: END;
WARNING: unexpected EOF on datanode connection
ERROR: sorry, too many clients already
STATEMENT: END;
WARNING: unexpected EOF on datanode connection
LOG: Failed to ABORT at node 16384
Detail: unexpected EOF on datanode connection
LOG: Failed to ABORT an implicitly PREPARED transaction status - 7
LOG: could not send data to client: Broken pipe
FATAL: connection to client lost
LOG: failed to find proc 0x7fb0cb34f7c0 in ProcArray
LOG: failed to find proc 0x7fb0cb34f7c0 in ProcArray
LOG: failed to find proc 0x7fb0cb34f7c0 in ProcArray
LOG: failed to find proc 0x7fb0cb34f7c0 in ProcArray
LOG: failed to find proc 0x7fb0cb34f7c0 in ProcArray**

On the data-nodes:

LOG: failed to find proc 0x7f379dee4a00 in ProcArray
LOG: failed to find proc 0x7f379dee4a00 in ProcArray
LOG: failed to find proc 0x7f379dee4a00 in ProcArray

and some of the transactons are still uncommited on some of the nodes and if I want to connect to other node ot throws the error "psql: FATAL: sorry, too many clients already"

Please any ideas, clue help....etc.

Thanks

#6 Problems using Hibernate Hbm2DDLExporter

2014-09-19T11:50:02.734000Z

Thanks for your support. Everything seems to be working properly now.

#6 Problems using Hibernate Hbm2DDLExporter

2014-09-18T09:08:07.734000Z

Still one problem left now...

Table is created via:

CREATE TABLE qrtz_triggers (
trigger_name character varying(200) NOT NULL,
trigger_group character varying(200) NOT NULL,
job_name character varying(200) NOT NULL,
job_group character varying(200) NOT NULL,
is_volatile boolean NOT NULL,
description character varying(250),
next_fire_time bigint,
prev_fire_time bigint,
trigger_state character varying(16) NOT NULL,
trigger_type character varying(8) NOT NULL,
start_time bigint NOT NULL,
end_time bigint,
calendar_name character varying(200),
misfire_instr integer,
job_data bytea,
priority integer
)
DISTRIBUTE BY REPLICATION;
ALTER TABLE ONLY qrtz_triggers
ADD CONSTRAINT qrtz_triggers_pkey PRIMARY KEY (trigger_name, trigger_group);

Command that fails:
ALTER TABLE ONLY qrtz_triggers
ADD CONSTRAINT eam_fk_qt_qjd FOREIGN KEY (job_name, job_group) REFERENCES qrtz_job_details(job_name, job_group) ON DELETE CASCADE;

Errormessage:
ERROR: Cannot create foreign key whose evaluation cannot be enforced to remote nodes

Can you tell me how I can fix this perhaps?

#6 Problems using Hibernate Hbm2DDLExporter

2014-09-18T06:13:10.346000Z

I am using the binary enterprise version of it. Problem occurs when creating tables:

hq=> create table EAM_AGENT (
hq(> ID int4 not null,
hq(> VERSION_COL int8 default 0 not null,
hq(> ADDRESS varchar(255) not null,
hq(> PORT int4 not null,
hq(> AUTHTOKEN varchar(100) not null,
hq(> AGENTTOKEN varchar(100) not null unique,
hq(> VERSION varchar(50),
hq(> CTIME int8,
hq(> MTIME int8,
hq(> UNIDIRECTIONAL bool not null,
hq(> PLUGIN_INVENTORY_CHECKSUM varchar(128),
hq(> LAST_PLUGIN_INVENTORY_CHECKIN int8 default 0 not null,
hq(> AGENT_TYPE_ID int4,
hq(> primary key (ID)
hq(> );

ERROR: Unique index of partitioned table must contain the hash/modulo distribution column.

which can be fixed by adding DISTRIBUTE BY REPLICATION to the end of the query.

The problem I have is that I am not able to add it, cause I don't know how I could do that (hence this stuff is done by hypernate).

Can you help me there?

Problems using Hibernate Hbm2DDLExporter

2014-09-17T13:32:27.582000Z

Hi all,

When trying to install hyperic server which supports PostgreSQL 9.1.x I get an error message stating that the database might not be supported.
Do you have an idea how to fix this possibly?

Errormsg: hyperic-hqee-installer-5.8.2/installer/data/setup-db-hibernate.xml:102: org.hibernate.tool.hbm2x.ExporterException: Errors while performing Hbm2DDLExporter

Thanks in advance for your help!

v1.2 ERROR: Cannot create index whose evaluation cannot be enforced to remote nodes

2014-06-27T20:50:08.676000Z

Create index for table cddos generates error message (I have no idea what it means or where to look for meaning). The only thing I can think of is that there are more fields in the index than in the key?

Index create:
CREATE UNIQUE INDEX cidos1 ON cddos USING btree (cunges, ndomat, netima);

Table definition:
CREATE TABLE cddos (
ndomat numeric(7,0) NOT NULL,
netima numeric(1,0) NOT NULL,
ndopfe character(15) NOT NULL,
clcndo character(1) NOT NULL,
didaff numeric(9,0) NOT NULL,
dlvcpr numeric(9,0) NOT NULL,
ciuges character(2) NOT NULL,
d1odpl numeric(9,0) NOT NULL,
csesoc character(4) NOT NULL,
capres character(2) NOT NULL,
dmcdos numeric(9,0) NOT NULL,
cstacp character(1) NOT NULL,
cunges character(7) NOT NULL,
cmetra character(1) NOT NULL,
danars numeric(9,0) NOT NULL,
ddecra numeric(9,0) NOT NULL,
dnotpa numeric(9,0) NOT NULL,
ddecal numeric(9,0) NOT NULL,
dmocgm numeric(9,0) NOT NULL,
dapres numeric(9,0) NOT NULL,
dreres numeric(9,0) NOT NULL,
dmajdo numeric(9,0) NOT NULL,
dndpot numeric(9,0) NOT NULL,
confid character(4) NOT NULL,
coeffk character(1) NOT NULL,
corgim character(3) NOT NULL,
confor character(1) NOT NULL,
doheix numeric(9,0) NOT NULL,
ctimco character(2) NOT NULL,
depaje numeric(9,0) NOT NULL,
daplma numeric(9,0) NOT NULL,
dbarsa numeric(9,0) NOT NULL,
ctybas character(1) NOT NULL,
dmjdcp numeric(9,0) NOT NULL,
hmjdcp numeric(7,0) NOT NULL,
CONSTRAINT cidos0 PRIMARY KEY (ndomat, netima)
)
DISTRIBUTE BY HASH (ndomat);

psql:run_alter.txt:1: ERROR: Cannot create index whose evaluation cannot be enforced to remote nodes

How to Define and Load large databases with lots of tables

2014-06-24T12:50:48.558000Z

I have worked to create a large environment and have encountered numerous problems. I used v1.2 as it showed to be released. It drops connections all of the time and complains about missing tuples though it seems to have loaded the correct number of records in the tables. I loaded the tables from csv files an got lots of the following messages:
LOG: failed to find proc 0x7f6a7f638f20 in ProcArray
WARNING: pgstat wait timeout

There are 491 tables defined in this environment and 347 have data loaded for the application under test. There is about 30GB of data all together. On a number of occasions during the define of the tables and the load I received the following messages:
WARNING: unexpected EOF on datanode connection
WARNING: unexpected EOF on datanode connection
ERROR: sorry, too many clients already
ERROR: Failed to get pooled connections

Can anyone provide insight into this?

Best release to test postgres-xc

2014-05-23T08:53:28.210000Z

I'd like to test postgres-xc.
I noticed that all the release are in parallel development.
What are the differences between release 1.0.x, 1.1.x and 1.2.x?
To test the platform, which one is the best?

Thank you.