[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: cn=config replication to consumer / slave servers

Christopher Strider Cook wrote:

On 4/15/11 11:46 AM, Howard Chu wrote:
Quanah Gibson-Mount wrote:
--On Thursday, April 14, 2011 5:28 PM -0700 Christopher Strider Cook
<ccook@pandora.com>   wrote:

Alternately, I tried to setup a separate database cn=config_slave and
have that snycrepl to the slave into cn=config... but that creates a
naming missmatch.

Is there an approved practice to achieve this, or some other
pointers on
avenues to explore?

Use slapo-rwm to rewrite the cn=config_slave database to be cn=config on
the replicas.

No, that never worked well. Use suffixmassage in the syncrepl config
statement. (Added in 2.4.24)

Yes that looks like the right path.. I've just recompiled to gain this
superpower... But:

So I've got a 'stub' cn=config setup with enough (I think) to get it
booted and connecting to the master to syncrepl over the rest of the config.
olcDatabase\=\{0\}config.ldif  has I think a proper syncrepl line:
olcSyncrepl: {0}rid=001 provider=ldaps://hostxxx.com bindmethod=simp
   le binddn="cn=admin,cn=config_slave" credentials=pass searchbase="
   cn=config_slave" suffixmassage="cn=config" schemachecking=on
type=refreshAndPersist retry="60 +"

Please read the test059 script in the test suite, it already does all the necessary steps in the correct order.

Something is still not quite right. In the logs I see a few troubling
messages and the local cn=config doesn't update.

  -- Howard Chu
  CTO, Symas Corp.           http://www.symas.com
  Director, Highland Sun     http://highlandsun.com/hyc/
  Chief Architect, OpenLDAP  http://www.openldap.org/project/