[Date Prev][Date Next]
RE: syncrepl and glue
- To: "Howard Chu" <email@example.com>
- Subject: RE: syncrepl and glue
- From: "Spicer, Kevin" <KevinS@bmrb.co.uk>
- Date: Wed, 11 Jan 2006 01:29:14 -0000
- Cc: <openldap-software@OpenLDAP.org>
- Content-class: urn:content-classes:message
- Thread-index: AcYV9o51l4Xpa/gzSvydIAQlUL5goAAUuvwQ
- Thread-topic: syncrepl and glue
From: Howard Chu [mailto:firstname.lastname@example.org]
>The answer is in the description for "subordinate" in slapd.conf(5).
>have to exchange the order of the syncprov and glue overlays to prevent
>the provider from descending into the glued databases.
Thanks, however that doesn't seem to solve the problem of no replication
happening (although it appears to have solved the random changes to db
problem). I have verified that replication works with the subordinate
directives (and 'overlay glue' directive) commented on the provider.
My database definition on the provider for the superior db contains the
### START ###
syncprov-checkpoint 100 10
### END ###
The consumer has this...
retry="30 10 120 30 300 +"
I have tried it with the ppolicy directives removed on the provider, but
that doesn't have an
impact. I'm seeing the following log lines on the consumer...
slapd: [ID 764482 local4.debug] do_syncrep2: got search entry
(These correspond to binds from the syncuser on the provider)
Turning up logging on the provider I see this line..
slapd: [ID 430416 local4.debug] slap_global_control: unavailable
BMRB wins two BMRA awards - http://www.bmrb.co.uk
This message (and any attachment) is intended only for the
recipient and may contain confidential and/or privileged
material. If you have received this in error, please contact the
sender and delete this message immediately. Disclosure, copying
or other action taken in respect of this email or in
reliance on it is prohibited. BMRB Limited accepts no liability
in relation to any personal emails, or content of any email which
does not directly relate to our business.