Re: OL 2.3.19, delta-syncrepl issue

[Quanah Gibson-Mount <quanah@stanford.edu>]

--On Friday, February 03, 2006 2:34 PM -0500 Samuel Tran <stran@amnh.org> 
wrote:

> Hi All,
>
> I am testing delta-syncrepl with two Debian Sarge Linux boxes running OL
> 2.3.19 + 2 patches (ITS #4369 and #4376).
>
> Here the configuration on the provider:
>
> # Accesslog DB definition (slapo-accesslog)
> database        bdb
> suffix          "cn=accesslog"
> rootdn          "cn=root,cn=accesslog"
> directory       /var/lib/ldap/accesslog
> index           default eq
> index           entryCSN,objectClass,reqEnd,reqResult,reqStart
>
> # Let the replica DN have limitless searches
> limits dn.exact="cn=syncrepl,ou=Accounts,ou=Apps,dc=example,dc=com"
> time.soft=unlimited
> time.hard=unlimited size.soft=unlimited size.hard=unlimited

The above should be one line.

> # Primary AMNH database definition
> database        bdb
> suffix          "dc=example,dc=com"
> rootdn          "cn=Manager,dc=example,dc=com"
>
> # syncprov specific indexing
> index   entryUUID,entryCSN eq
>
> # Let the replica DN have limitless searches
> limits dn.exact="cn=syncrepl,ou=Accounts,ou=Apps,dc=example,dc=com"
> time.soft=unlimited
> time.hard=unlimited size.soft=unlimited size.hard=unlimited


The above should be one line.

> #############################################################
> # Syncrepl - Provider configuration
> #############################################################
>
> overlay syncprov
> syncprov-checkpoint 100 30
> syncprov-sessionlog 100
> syncprov-nopresent TRUE
> syncprov-reloadhint TRUE
>
> #############################################################
> # Accesslog - Access Logging overlay (required for delta syncrepl)
> #############################################################
>
> overlay accesslog
> logdb cn=accesslog
> logops writes
> # scan the accesslog DB every day, and purge entries older than 28 days
> logpurge 28+00:00 01+00:00
>
>
> Here the configuration on the consumer:
>
> #############################################################
> # Syncrepl - Consumer configuration
> #############################################################
> syncrepl        rid=121
>                 provider=ldaps://info-ldap-001.example.com:636
>                 type=refreshAndPersist
>                 retry="5 +"
>                 searchbase="dc=example,dc=com"
>                 bindmethod=simple
>
> binddn="cn=syncrepl,ou=Accounts,ou=Apps,dc=example,dc=com"
>                 credentials=xxxxxxxxxxxx
>                 logbase="cn=accesslog"
>                 schemachecking=on
>                 syncdata=accesslog



Is there really an extra space between bindmethod and binddn?


> The consumer is in a DMZ with a public IP address while the provider is
> in the internal network with a private IP address. Traffic from the
> consumer to the provider is allowed on port 636.
>
> I modified some entries on the provider. I can see the changes in the
> accesslog db. But no synchronization on the consumer.

Based on the other error logs you sent, it sounds like the syncRepl control 
isn't being published, or the syncrepl client (replica) doesn't have access 
to read the rootDSE on the master.

--Quanah

--
Quanah Gibson-Mount
Principal Software Developer
ITSS/Shared Services
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html