> > and better yet, can you connect to both of them on the machine where the
> > slons will run like this:
> >
> > psql -h au -p 5433 -U postgres my_db
> > psql -h au -p 5432 -U postgres my_db
> >
> > and if so, what's the output of:
> >
> > select _my_db_cluster.getlocalnodeid('_my_db_cluster');
> >
> > on both those?
> 
> The first one (the master) reports 1, and the second one (the slave)
> reports 2, as expected.
> 
> So I guess the question is, why does slon think it is on the wrong node?
> If it connects and does the getlocalnodeid() as you say, then what makes
> it think that's the wrong node?  What tells it that node 2 is the wrong
> one?

In that case, I bet one of the store paths is wrong.  I.e. it thinks it's
connecting to node 1, but is really connecting to node 2.

Does the conninfo in _my_db_cluster.sl_path match the conninfo you expect to
see?


 

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 2996 (20080403) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com