Re: bdr_init_copy fails when starting 2nd BDR node

Hi,

On 2014-12-29 23:51:05 -0500, John Casey wrote:
> I've been having issues while attempting to begin BDR replication. If I set
> up the main node, then use bdr_init_copy, it always fails on second node, as
> shown below.
>
>
>
> postgres$ rm -Rf $PGDATA
>
> postgres$ echo db_password | pg_basebackup -X stream -h main_node_ip -p 5432
> -U username -D $PGDATA
>
> postgres$ cp $HOME/backup/postgresql.conf $PGDATA
>
> postgres$ bdr_init_copy -U username -D $PGDATA
>
> bdr_init_copy: starting...
>
> Assigning new system identifier: 6098464173726284030...
>
> Creating primary replication slots...
>
> Creating restore point...
>
> Could not connect to the remote server: could not connect to server: No such
> file or directory
>
> Is the server running locally and accepting
>
> connections on Unix domain socket "/tmp/.s.PGSQL.5432"?

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 th ehost in the
config?

What does 'git describe --tags' return?

Greetings,

Andres Freund