Re: bdr_init_copy fails when starting 2nd BDR node

From: 'Andres Freund' <andres(at)2ndquadrant(dot)com>
To: John Casey <john(dot)casey(dot)rtp(at)icloud(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: bdr_init_copy fails when starting 2nd BDR node
Date: 2014-12-31 10:04:01
Message-ID: 20141231100401.GA19836@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Mike Broers 2014-12-31 15:00:35 ltree gist index errors and fill factor questions
Previous Message sramay 2014-12-31 07:31:11 Re: vacuum vs pg_repack vs pg_reorg