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

Re: Q: Managing entryCSN with slapadd

Ulrich Windl wrote:

I have a question: Is there a way to fix entryCSNs for slapadd? Reasoning: With dynamic configuration, sometimes (if you messed up) you'll have to edit your  slapcat dump to reinitialize the config database. Unfortunately with replication the entry CSNs seem to casue trouble:
If you don't change the CSN, the canges are not replicated, it seems; if you change the CSN, OpenLDAP doesn't seem to like it.

I see repeating message slike these:
slapd[3017]: Entry olcDatabase={0}config,cn=config CSN 20130709140112.108165Z#000000#000#000000 older or equal to ctx 20130709140112.108165Z#000000#000#000000
slapd[3017]: do_syncrep2: rid=001 CSN too old, ignoring 20130712085712.643156Z#000000#000#000000 (olcDatabase={2}monitor,cn=config)

Ist there a way to fix this?

When editing the slapcat dump, delete the entryCSN. slapadd will generate a new one.

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