Hi,
I'm using a configuration with two slapd servers, master and replica. The problem is that replica is constantly desyncing. I'm monitoring it's number of users and groups and the cound of members of one particular group. Users and group entities are always in sync, but entities like groupOfUniqueNames are desyncing - they are not receiveing deltas from master, keeping their members count constant.
My config (done according to the documentation):
===Cut=== overlay syncprov syncprov-checkpoint 100 10 syncprov-sessionlog 100
syncrepl rid=123 provider=ldap://xx.xx.xx.xx:389 type=refreshAndPersist interval=00:00:10:00 retry="60 10 300 +" filter="(objectClass=*)" searchbase="dc=my,dc=domain" attrs="*,+" schemachecking=off bindmethod=simple binddn="uid=proxy,ou=accounts,ou=internal,dc=my,dc=domain" credentials=XXXXXXXXXXXXXX ===Cut===
I've also tried the refreshOnly method, which gave me same result. In order to resync replica I have to flush the directory contents each time and restart the slapd. I'm also suspecting that this desyncing happens because for some reason replica slapd isn't refreshing attribute values, only entities themselves: today I found a user, which userPassword attributes were out of sync on the replica. As far as I understand the documentation, syncrepl should sync the attributes.
And the last question - is there any simple way to enable logging of syncrepl warnings and errors ? My experience with openldap logging tells me there's to mode of logging - "none" and "generate 10Gb of logs per day", but may me it's just me.
Thanks. Eugene.
--On Saturday, June 25, 2016 10:52 AM +0500 "Eugene M. Zheganin" eugene@zhegan.in wrote:
Hi,
I'm using a configuration with two slapd servers, master and replica. The problem is that replica is constantly desyncing
#1 piece of information to provide: OpenLDAP version
--Quanah
--
Quanah Gibson-Mount Platform Architect Manager, Systems Team Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration A division of Synacor, Inc
Hi.
On 25.06.16 21:25, Quanah Gibson-Mount wrote:
--On Saturday, June 25, 2016 10:52 AM +0500 "Eugene M. Zheganin" eugene@zhegan.in wrote:
Hi,
I'm using a configuration with two slapd servers, master and replica. The problem is that replica is constantly desyncing
#1 piece of information to provide: OpenLDAP version
Master is 2.4.40 and replica is 2.4.38 (is this the root of the problem ?).
P.S. I guess it's not, I've upgraded the replica installation to the same exaclty version, but the problem is still here.
Thanks. Eugene.
--On Friday, July 01, 2016 5:53 PM +0500 "Eugene M. Zheganin" emz@norma.perm.ru wrote:
Hi.
On 25.06.16 21:25, Quanah Gibson-Mount wrote:
--On Saturday, June 25, 2016 10:52 AM +0500 "Eugene M. Zheganin" eugene@zhegan.in wrote:
Hi,
I'm using a configuration with two slapd servers, master and replica. The problem is that replica is constantly desyncing
# 1 piece of information to provide: OpenLDAP version
Master is 2.4.40 and replica is 2.4.38 (is this the root of the problem ?).
P.S. I guess it's not, I've upgraded the replica installation to the same exaclty version, but the problem is still here.
2.4.40 is known to have serious replication bugs. I suggest using a current release.
--Quanah
--
Quanah Gibson-Mount Platform Architect Manager, Systems Team Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration A division of Synacor, Inc
Hi.
On 01.07.16 20:45, Quanah Gibson-Mount wrote:
--On Friday, July 01, 2016 5:53 PM +0500 "Eugene M. Zheganin" emz@norma.perm.ru wrote:
Hi.
On 25.06.16 21:25, Quanah Gibson-Mount wrote:
--On Saturday, June 25, 2016 10:52 AM +0500 "Eugene M. Zheganin" eugene@zhegan.in wrote:
Hi,
I'm using a configuration with two slapd servers, master and replica. The problem is that replica is constantly desyncing
# 1 piece of information to provide: OpenLDAP version
Master is 2.4.40 and replica is 2.4.38 (is this the root of the problem ?).
P.S. I guess it's not, I've upgraded the replica installation to the same exaclty version, but the problem is still here.
2.4.40 is known to have serious replication bugs. I suggest using a current release.
Well, I've upgraded both master and replica to 2.4.44, but unfortunately, the problem is still there. However, I cannot say that all the changes aren't replicating: for example yeasterday I've added two user to a group - this change was reflected on a replica, but today my colleague added same two persons into another group, and this change wasn't replicated. Once again, I had to delete all the replica DBs and restart slapd - then changes made it to the replica.
Eugene.
openldap-technical@openldap.org