Re: repmgr problem with registering standby

From: Toby Corkindale <toby(dot)corkindale(at)strategicdata(dot)com(dot)au>
To: Jaime Casanova <jaime(at)2ndquadrant(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: repmgr problem with registering standby
Date: 2011-07-28 00:24:52
Message-ID: 4E30AC54.4050200@strategicdata.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 28/07/11 03:47, Jaime Casanova wrote:
> On Wed, Jul 27, 2011 at 4:36 AM, Toby Corkindale
> <toby(dot)corkindale(at)strategicdata(dot)com(dot)au> wrote:
>>
>> So that looks good, but then I try this on the slave:
>> # repmgr -f /etc/repmgr/validator/repmgr.conf \
>> --verbose standby register
>>
> can you show the content of /etc/repmgr/validator/repmgr.conf?

cluster=validator
node=mel-db06
conninfo='host=10.133.54.1 port=5432 user=repmgr dbname=repmgr'

>> I can query the database like so though, and it seems like it's all good:
>> repmgr=# select * from repmgr_validator.repl_nodes;
>> id | cluster | conninfo
>> ----+-----------+------------------------------------------------------
>> 0 | validator | host=10.133.54.2 port=5432 user=repmgr dbname=repmgr
>> (1 row)
>
> this is on the master or the slave?

I ran that on the slave; however I've just checked now, and the same
results are given on both nodes.
Just so you know, db06=10.133.54.1 and db07=10.133.54.2.
They also have a second address each on the 192.168.10.x network as well
though.

Toby

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message sqldbxdeveloper 2011-07-28 01:51:05 Re: problems viewing information_schema.schemata
Previous Message Jack Christensen 2011-07-27 23:10:08 Re: WITH x AS (...) and visibility in UPDATE