Re: BDR Error restarted

From: theftp <theftp(dot)ru(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: BDR Error restarted
Date: 2015-02-02 14:52:25
Message-ID: 1422888745947-5836407.post@n5.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi all,

I have a similar problem.

OS Red Hat Enterprise Linux Server release 6.6.

Postgresql packets were installed from repository as described in
https://wiki.postgresql.org/wiki/BDR_Packages

postgresql-bdr94-bdr-0.8.0beta1-1_2ndQuadrant.el6.x86_64
postgresql-bdr94-contrib-9.4.0_bdr1-1_2ndQuadrant.el6.x86_64
postgresql-bdr94-9.4.0_bdr1-1_2ndQuadrant.el6.x86_64
postgresql-bdr94-libs-9.4.0_bdr1-1_2ndQuadrant.el6.x86_64
postgresql-bdr94-server-9.4.0_bdr1-1_2ndQuadrant.el6.x86_64

There are two servers: 192.168.214.169 (main), 192.168.214.163

On each server run commands:
su - postgres -c "/usr/pgsql-9.4/bin/initdb
--pgdata=/var/lib/pgsql/9.4-bdr/data --auth='trust' --username=test_root"
su - postgres -c "/usr/pgsql-9.4/bin/pg_ctl -l
/var/lib/pgsql/9.4-bdr/data/postgresql-02.log -D
/var/lib/pgsql/9.4-bdr/data -o '-p 5432' -w start"
createdb -p 5432 -U test_root testdb

On the first server I've created a schema and a table in it.

Then configs were updated and postgresql servers were restarted.
iptables is switched off.

//postgrsql.conf [192.168.214.169]

listen_addresses = '192.168.214.169'
port=5432

max_replication_slots = 3
max_wal_senders = 4
wal_level = 'logical'
track_commit_timestamp = on
shared_preload_libraries = 'bdr'
max_worker_processes = 10

bdr.connections = 'second'
bdr.second_dsn = 'host=192.168.214.163 port=5432 dbname=testdb
user=test_root'

// pg_hba.conf [192.168.214.169]

host all test_root 192.168.214.163/32 trust
host replication test_root 192.168.214.163/32 trust
+ uncomment existing replication lines

//postgrsql.conf [192.168.214.163]

listen_addresses = '192.168.214.163'
port=5432

max_replication_slots = 3
max_wal_senders = 4
wal_level = 'logical'
track_commit_timestamp = on
shared_preload_libraries = 'bdr'
max_worker_processes = 10

bdr.connections = 'first'
bdr.first_dsn = 'host=192.168.214.169 port=5432 dbname=testdb
user=test_root'
bdr.first_init_replica = on
bdr.first_replica_local_dsn = 'port=5432 dbname=testdb user=test_root'

// pg_hba.conf [192.168.214.163]

host all test_root 192.168.214.169/32 trust
host replication test_root 192.168.214.169/32 trust
+ uncomment existing replication lines

Replication works only on that created table and only from the first to the
second server.
When I try to create one more table, the sql command 'CREATE TABLE ...'
hangs.

The followng errors are added each second in postgresql logs:

// 192.168.214.169

LOG: starting background worker process "bdr
(6109689945671396351,1,16384,): second: apply"
NOTICE: version "1.0" of extension "btree_gist" is already installed
CONTEXT: slot "bdr_16384_6109689945671396351_1_16384__", output plugin
"bdr", in the startup callback
NOTICE: version "0.8.0.6" of extension "bdr" is already installed
CONTEXT: slot "bdr_16384_6109689945671396351_1_16384__", output plugin
"bdr", in the startup callback
ERROR: data stream ended
LOG: worker process: bdr (6109689945671396351,1,16384,): second: apply (PID
13549) exited with exit code 1

// 192.168.214.163

ERROR: bdr output plugin: slot creation rejected, bdr.bdr_nodes entry for
local node (sysid=6109702913719211129, timelineid=1, dboid=16384):
status='i', bdr still starting up: applying initial dump of remote node
HINT: Monitor pg_stat_activity and the logs, wait until the node has caught
up
CONTEXT: slot "bdr_16384_6109689945671396351_1_16384__", output plugin
"bdr", in the startup callback
LOG: could not receive data from client: Connection reset by peer

In attachment - debug logs of postgresql.

How to fix it?

first_postgres.log
<http://postgresql.nabble.com/file/n5836407/first_postgres.log>
second_postgres.log
<http://postgresql.nabble.com/file/n5836407/second_postgres.log>

--
View this message in context: http://postgresql.nabble.com/BDR-Error-restarted-tp5833139p5836407.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2015-02-02 15:11:01 Re: Problem with REFERENCES on INHERITS
Previous Message David Evans 2015-02-02 11:06:37 Stability of JSON textual representation