HRZ Konten hrzkon...@uni-bonn.de writes:
Is there an easy way to force a new replication on the second node?
I will really appreciate your help...
Just delete the database on the second node and setup a new node.
Well, that is rather a worst case scenario, but if this is the only
--On Monday, January 18, 2010 5:38 PM +0100 Gerard Ranke
gerard.ra...@kmt.hku.nl wrote:
for 2.4.21.
Notice the ' uri= ' in the last version.
Please file an ITS at http://www.openldap.org/its/ for this issue.
Thanks!
--Quanah
--
Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
Am 28.01.2010 13:00, schrieb openldap-software-requ...@openldap.org:
Is there any other way to check that? Then if I don't know that they are
out of synchow could I start the rebuild of the second node...
To check the database content just slapcat both directories and do a
diff.
Rein Tollevik wrote:
Ryan Steele wrote:
I'm replicating both the config and backend databases between two
boxes. Everything seems fine, but for some reason
when I query them both for the contextCSN, the config database returns
only one while the backend database returns two,
as seen below:
HRZ Konten wrote:
Hallo all,
we have 2 OpenLDAP 2.4.17 with N-Way Replication on Debian Lenny.
Config
dn: olcDatabase={0}config
objectClass: olcDatabaseConfig
olcDatabase: {0}config
olcRootPW:: x
structuralObjectClass: olcDatabaseConfig
entryUUID:
Brett @Google wrote:
On Thu, Jan 28, 2010 at 5:31 AM, Dieter Kluenter die...@dkluenter.de
mailto:die...@dkluenter.de wrote:
The 2.4.x series seems to require a perl backend to require knowledge of
syncrepl, even if it's pushing
to a perl backend on another server via a
