Hi,

on a consumer with two replicated databases I get this on startup: # grep sync

Feb 7 17:16:52 rfas099 slapd[4263]: Config: ** successfully added syncrepl rid=401 "ldap://master.foo.de" Feb 7 17:16:52 rfas099 slapd[4263]: line 124 (syncrepl ***) Feb 7 17:16:52 rfas099 slapd[4263]: Config: ** successfully added syncrepl rid=402 "ldap://master.foo.de" Feb 7 17:16:52 rfas099 slapd[4264]: do_syncrep2: rid=401 LDAP_RES_INTERMEDIATE - REFRESH_DELETE Feb 7 17:16:52 rfas099 slapd[4264]: do_syncrep2: rid=402 LDAP_RES_INTERMEDIATE - SYNC_ID_SET Feb 7 17:16:52 rfas099 slapd[4264]: do_syncrep2: rid=402 LDAP_RES_INTERMEDIATE - REFRESH_DELETE

There is do_syncrep2: rid=402 LDAP_RES_INTERMEDIATE - SYNC_ID_SET for one database, but not for the other.

From the list archive I got this: "The SYNC_ID_SET messages in this case are the provider telling the consumer what entries it has, so the consumer can delete entries not present on the provider. This is normal operation in some situations. It shouldn't happen too often if you specify a sufficient sessionlog size on the provider." http://www.openldap.org/lists/openldap-technical/201104/msg00079.html

So, if there is no SYNC_ID_SET for a database, is this a bad sign?

Marc