Re: repmgr problem with registering standby - Mailing list pgsql-general

From Toby Corkindale
Subject Re: repmgr problem with registering standby
Date
Msg-id 1217244880.3404.1311777041030.JavaMail.root@dmz03
Whole thread Raw
In response to Re: repmgr problem with registering standby  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-general
----- Original Message -----
> On Wed, Jul 27, 2011 at 10:36 AM, Toby Corkindale wrote:
> > Hi,
> > I have repmgr working to some degree on a couple of servers, but am
> > having
> > trouble with the "register" part on the slave.
> >
> > On the master, I run:
> > # repmgr -f /etc/repmgr/validator/repmgr.conf \
> >  --verbose --force master register
> >
> > Opening configuration file: /etc/repmgr/validator/repmgr.conf
> > repmgr connecting to master database
> > repmgr connected to master, checking its state
> > finding node list for cluster 'validator'
> > Master node correctly registered for cluster validator with id 0
> > (conninfo:
> > host=10.133.54.2 port=5432 user=repmgr dbname=repmgr)
> >
> >
> > So that looks good, but then I try this on the slave:
> > # repmgr -f /etc/repmgr/validator/repmgr.conf \
> >  --verbose standby register
> >
> > Opening configuration file: /etc/repmgr/validator/repmgr.conf
> > repmgr connecting to standby database
> > repmgr connected to standby, checking its state
> > repmgr connecting to master database
> > finding node list for cluster 'validator'
> > A master must be defined before configuring a slave
> >
> >
> >
> > 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)
> >
> >
> > Does anyone have an idea of what might be going wrong here?
>
> Hi, thanks for using repmgr.
>
> What version of repmgr are you using? What version of PostgreSQL?

Hi Simon,
We're using version 1.1.0 of repmgr, against PostgreSQL 9.0.4-1~bpo60+1 (ie. the version from backports) on Debian
squeeze.

To complicate matters, we have several postgresql instances per machine, using Debian's pg cluster stuff. This seems to
workelsewhere with repmgr though (as long as we make sure the ports are specified in the repmgr configs). 
However, I'm not having any success even with just the default/single instance of pg either at the moment.

Cheers,
Toby

pgsql-general by date:

Previous
From: "Karsten Hilbert"
Date:
Subject: Re: Implementing "thick"/"fat" databases
Next
From: Greg Smith
Date:
Subject: Re: heavy load-high cpu itilization