318212415Z
nsds5replicaChangesSentSinceStartup:
nsds5replicaLastUpdateStatus: 0 Replica acquired successfully: Incremental upd
ate started
nsds5replicaUpdateInProgress: FALSE
nsds5replicaLastInitStart: 0
nsds5replicaLastInitEnd: 0
Any ideas?
Thanks,
Jon
- Original Message -
> From: "Jon Deter
- Original Message -
> From: "Jon Detert"
> To: "General discussion list for the 389 Directory server project."
> <389-us...@lists.fedoraproject.org>
> Sent: Thursday, March 7, 2013 10:37:54 AM
> Subject: [389-users] Single Master replicatio
- Original Message -
> From: "Rich Megginson"
> To: "General discussion list for the 389 Directory server project."
> <389-us...@lists.fedoraproject.org>
> Cc: "Jon Detert"
> Sent: Thursday, March 7, 2013 11:44:48 AM
> Subject: Re:
aId: 65535
nsState:: //8AAADDxzdRAA==
nsDS5ReplicaName: edb50b02-86af11e2-9dc2a557-8005a77d
nsds5ReplicaChangeCount: 0
nsds5replicareapactive: 0
Thanks for any insight you offer.
--
Jon Detert
Sr. Systems Administrator
Infinity Healthcare
Milwaukee, Wisconsin
414
>
> On 03/06/2013 06:49 PM, Jon Detert wrote:
> > I want to check the status of replication agreements, but I don't
> > want to use the directory manager's credentials to do so. I want
> > to use bind credentials for a dn that only has read access.
> >
&
. I've tried these:
(targetfilter = "(objectClass=nsds5ReplicationAgreement)")
and
(target="ldap:///cn=*,cn=replica,cn=*,cn=mapping tree,cn=config")
Any ideas what I'm doing wrong? Thanks
--
Jon Detert
Sr. Systems Administrator
Infinity Healthcare
Milwaukee, Wisconsin
414-290
I'm trying to setup/configure single-master replication between 2
brand-new centos-ds (aka 'dirsrv') v8.1 servers. Centos directory
server is derived from '389 directory server'. I can't find any
community support for it beyond this list. Please pardon the centos
intrusion on your list.
I'm fol
I'm trying to setup a supplier for single-master replication.
I'm actually using Centos Directory Server v8.1 (which is probably
equivalent to something like 389 dir serv v 1.2.4).
I created the changelog entry successfully.
The next step, according to this doc:
http://docs.redhat.com/docs/en-U