Hello everybody, i am experiencing 2 issues while using syncrepl. i am running slapd 2.4.20 shipping with SLES 11.2.

1. replication of an accesslog database. ============================= the accesslog overlay does not assign an entryUUID to its logdb database. therefore replication of this database is not possible.

dn: cn=accesslog objectClass: auditContainer cn: accesslog entryCSN: 20120317121350.967741Z#000000#000#000000 structuralObjectClass: auditContainer contextCSN: 20120320154322.642649Z#000000#000#000000

To be able to replicate cn=accesslog anyways, i initialize the accesslog database via slapadd from an ldif file that contains a made up entryUUID for dn:cn=accesslog, afterwards i fire up the slapd. Replication now seems to work fine. My question is, does this method have any unwanted side effects?

2. replication of cn=config =================== when replicating cn=config all objects below cn=schema,cn=config get replicated when the consumer is initially started. for dn:olcDatabase={-1}frontend,cn=config and dn:cn=config (olcGlobal) initially no synchronization happens. Both objects get replicated only after they have been modified on the on the provider ie. when starting a new consumer i have to carry out meaningless modifications to both objects on the provider to initiate the replication. is this behavior to be expected?

my syncrepl config is:

syncrepl rid=15 provider=ldap://192.168.2.100 type=refreshAndPersist retry="1 1 1 1" searchbase="cn=config" filter="(|(objectClass=olcGlobal)(objectClass=olcSchemaConfig)(objectClass=olcFrontendConfig))" attrs="*,+" bindmethod=simple binddn="cn=admin,cn=config" credentials="secret"

Best regards,

Marvin