Re: Implementing Replication via pgAdmin

Daniel B. Thurman wrote:
> # Set the cluster name that this instance of slon is running against
> # default is to read it off the command line
> cluster_name='MasterCluster'
>
> # Set slon's connection info, default is to read it off the command line
> conn_info='host=copper.cdkkt.com port=5432 dbname=MyTest user=postgres password=***'

That is the minimum you need to get started.

> I did the same thing for slave side, and I get an error message:
> 4) ERROR slon_connectdb: PQconnectdb("host=copper.cdkkt.com dbname=MyTest
> user=postgres") failed - fe_sendauth: no password supplied

Well the connection string in that error message doesn't contain a
password, unlike the one in the conf file you showed above. Are you sure
you registered the right file?

> Seems that master cannot reach the slave and the slave cannot reach
> the master?
>
> I thought that perhaps this was due to the account being LocalSystem
> accounts, for the both master and slave servers and perhaps network
> access is not permitted with these accounts?

Not that I'm aware of - and you wouldn't get that specific message in
that case anywy.

> And yet, I note that the Nodes on both the master and slave are
> running with PID and valid process id numbers. However, changing
> a value in the master database table does not replicate to the slave.
>
> As a test, I tried to use a local user account for the slon service on
> the master as 'postgres', which is a Windows 2000 Professional OS, which
> allows local user accounts to be created and I was able to get slon to
> run, but as for the slave server, which is a Windows 2000 Server, which
> is also a secondary Domain Controller, I am not allowed to create local
> user accounts, but instead must use the domain user account
> as: 'postgres(at)cdkkt(dot)com' which differs from that used by PostgreSQL
> as: 'postgres'?

Shouldn't matter in the slightest.

> This is getting really confusing...
>
> Please advise?

You're asking in the wrong place really - this list is for pgAdmin
issues but this is Slony installation issue.

Regards, Dave.