https://bugs.openldap.org/show_bug.cgi?id=10424

          Issue ID: 10424
           Summary: When using more than one syncrepl directive on a
                    single DB, the contextCSN should be stored accordingly
                    to the replication base
           Product: OpenLDAP
           Version: 2.6.10
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Keywords: needs_review
          Severity: normal
          Priority: ---
         Component: overlays
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

Trying to replicate cn=config but parially, I tried to set many syncrepl
directives so that each oe of them just replicate the single element it is
configured for. Here is an exemple thet replicate the frontend database and
only it:

{0}rid=004
 provider=ldaps://openldap1:10636
 bindmethod=simple
 binddn="cn=syncrepl,ou=accounts,dc=worteks,dc=com"
 credentials=blah
 tls_cacert=/opt/application/openldap/ssl/ca.crt
 tls_cert=/opt/application/openldap/ssl/openldap-common.crt
 tls_key=/opt/application/openldap/ssl/openldap-common.key
 tls_reqcert=demand
 tls_protocol_min=3.3
 searchbase="olcDatabase={-1}frontend,cn=config"
 scope="base"
 type=refreshAndPersist
 retry="30 +"
 timeout=1
 schemachecking=off 

If I have this single syncrepl directive, all is ok, it replicates the frontend
data and only this entry.

Would I like to replicate, says, 'cn=config' with another syncrepl directive
like:

olcSyncrepl: {0}rid=001
 provider=ldaps://openldap1:10636
 bindmethod=simple
 binddn="cn=syncrepl,ou=accounts,dc=worteks,dc=com"
 credentials=blah
 tls_cacert=/opt/application/openldap/ssl/ca.crt
 tls_cert=/opt/application/openldap/ssl/openldap-common.crt
 tls_key=/opt/application/openldap/ssl/openldap-common.key
 tls_reqcert=demand
 tls_protocol_min=3.3
 searchbase="cn=config"
 scope="base"
 type=refreshAndPersist
 retry="30 +"
 timeout=1
 schemachecking=off

where the search base is different, then suddenly I get some 'CSN too old'
errors, which make totally sense as we only have one single contextCSN stored
in the root entry (cn=config in my use case).

I know I'm really border line here (and the rational is that I want a partial
replication of cn=config because the two servers are a bit different), but I
would suggest that the contextCSN to be stored in the entry associated to the
searchBase, not at the root of the database.

-- 
You are receiving this mail because:
You are on the CC list for the issue.

Reply via email to