Univention Bugzilla – Bug 32852
Connector can skip changes in init mode
Last modified: 2013-11-19 06:43:13 CET
Observed while working on Bug #32768. The connector does not probably sync every object if the connector is restarted in the init phase. The problem is the interaction between usnchanged and usncreated. In the init phase the connector searches for usncreated but the connector saves the usnchanged number which is probably higher. For example: dn: object1 usnChanged: 10 usnCreated: 1 dn: object2 usnChanged: 8 usnCreated: 2 First the connector syncs object1 and then saves the usnChanged number. If the connector is now restarted, object2 will not be synced.
That is not complete right. The problem occurs only if objects are rejected in the initialization phase. Fix: r45010 Changelog: r45011
Code Ok, doing the same as the AD-Connector first change from Bug #22622 Comment 3. Changelog Ok.
UCS 3.2 has been released: http://docs.univention.de/release-notes-3.2-en.html http://docs.univention.de/release-notes-3.2-de.html If this error occurs again, please use "Clone This Bug".