Re: Issue with Configuring BDR 1.0.2 in Postgresql 9.4

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Morning Brad,

Could you pass along your pg_hba.conf for 10.108.55.92? Your issue may be there.


Regards,

Andrew Foster | Educational Measures, LLC
Sr. Database Administrator
7100 E. Belleview Ave, Suite 350
Greenwood Village, CO 80111
303-548-6516
afoster@xxxxxxxxxxxxxxxxxxxxxxx

On Jun 2, 2017, at 8:00 AM, Keefer, Brad (ITS) <Brad.Keefer@xxxxxxxxxx> wrote:

So, I’m trying to set up a simple two-node Postgres Replication cluster, and things are going ok until I try and set up the DSN. The command I am using is
 
bdrdemo=# SELECT bdr.bdr_group_create(local_node_name := 'node1', node_external_dsn := 'host=10.108.55.92 port=5432 dbname=bdrdemo');
 
but when I run that, I receive the following error:

FATAL:  could not connect to the server in non-replication mode: fe_sendauth: no password supplied
 
DETAIL:  dsn was: connect_timeout=30 keepalives=1 keepalives_idle=20 keepalives_interval=20 keepalives_count=5   host=10.108.55.92 port=5432 dbname=bdrdemo fallback_application_name='bdr (6427018047201618294,1,16384,):bdrnodeinfo'
CONTEXT:  SQL statement "SELECT *                           FROM bdr_get_remote_nodeinfo(node_local_dsn)"
PL/pgSQL function internal_begin_join(text,text,text,text) line 42 at SQL statement
SQL statement "SELECT bdr.internal_begin_join(
        'bdr_group_join',
        local_node_name,
        CASE WHEN node_local_dsn IS NULL THEN node_external_dsn ELSE node_local_dsn END,
        join_using_dsn)"
PL/pgSQL function bdr_group_join(text,text,text,text,integer,text[]) line 21 at PERFORM
SQL statement "SELECT bdr.bdr_group_join(
        local_node_name := local_node_name,
        node_external_dsn := node_external_dsn,
        join_using_dsn := null,
        node_local_dsn := node_local_dsn,
        apply_delay := apply_delay,
        replication_sets := replication_sets)"
PL/pgSQL function bdr_group_create(text,text,text,integer,text[]) line 84 at PERFORM
server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.
The connection to the server was lost. Attempting reset: Succeeded.
 
I’m running this on a RHEL 7.3 OS with SELinux set to Permissive.
 
I also enabled the bdr extension via the shared_preload_libraries lin in the postgresql.conf file, and created the extension btree_gist in the bdrdemo database prior to running the SELECT statement above.
 
Not sure what I am missing, but any pointers/advice you could give would be greatly appreciated.
 
Thanks.
 
 
Brad Keefer
Red Hat Consultant – RHCSA
 
Office of Information Technology Services
Tax & Finance Building 8, Floor 7, Harriman Campus
C: 919-210-7045 | brad.keefer@xxxxxxxxxx


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux