Re: bdr_init_copy fails when starting 2nd BDR node

I'm still experiencing similar problems. I'm not certain what parameter you
are referring to when you say 'ehost'. Otherwise, I did want to clarify a
couple of things. I have tried several combinations, each one fails in
various ways. So ...

(1) What is the exact syntax when calling bdr_init_copy from new nodes when
your database name is not 'postgres' and your user name is not 'postgres'.
Please note if you supply local or remote host/port in the command.
(2) Should you do a pg_ctl start on new node before trying to execute
bdr_init_copy. If I don't I get the error I posted earlier.

I've attached the new nodes (dr) postgresql.conf file.

-----Original Message-----
From: 'Andres Freund' [mailto:andres(at)2ndquadrant(dot)com]
Sent: Wednesday, December 31, 2014 5:04 AM
To: John Casey
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] bdr_init_copy fails when starting 2nd BDR node

Hi,

On 2014-12-30 21:12:17 -0500, John Casey wrote:
>
> > What was your bdr config at this point? The error message indicates
> > that
> it tries to
> > connect to port 5432 on localhost - but the copy was taken from
> 'main_node_ip'.
> > Perhaps you forgot to specify the ehost in the config?
>
> # Here is my conf on the DR server (where I am running bdr_init_copy)
> bdr.connections = 'primary'
> bdr.primary_dsn = 'dbname=my_db host=primary_ip user=my_username
port=5432'
> bdr.primary_init_replica = on
> bdr.primary_replica_local_dsn = 'dbname=my_db user=my_username port=5432'

My guess is that this is the source of the problem - you probably have one
system and one self compiled libpq around or something similar and they
disagree about the location of the unix socket directory. It complains
about:

> > connections on Unix domain socket "/tmp/.s.PGSQL.5432"?

which means given the above configuration it has to be
primary_replica_local_dsn. Could you a) try to explicitly set
unix_socket_directory=/tmp in postgresql.conf and host=/tmp in the above
config?

Also, please attach postgresql.conf.

Greetings,

Andres Freund

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services