[Date Prev][Date Next]
Re: CSN too old, ignoring - and therefore not syncing
Can you post your config somewhere?
On 22/12/2008, Pat Riehecky <firstname.lastname@example.org> wrote:
> Here is the quick and dirty what I am trying to do:
> ldap1 and ldap2 are supposed to be in MultiMaster. They are time synced
> to pool.ntp.org and each other (if they drift I would rather they sorta
> drift together, but pool should be keeping that in check).
> Right now I am just beating them up to see how 2.4.13 performs. (So far
> VERY well, minus this little problem)
> I have a rather small ldif (41 entries) that just wont sync (I'm
> starting small). Debug gives me
> ber_scanf fmt (m}) ber:
> ber_dump: buf=0xb806f120 ptr=0xb806f137 end=0xb806f175 len=62
> 0000: 00 3c 72 69 64 3d 30 30 31 2c 73 69 64 3d 30
> 30 .<rid=001,sid=00
> 0010: 32 2c 63 73 6e 3d 32 30 30 38 31 32 32 32 31 37
> 0020: 34 37 32 31 2e 38 35 35 39 30 34 5a 23 30 30 30
> 0030: 30 30 30 23 30 30 31 23 30 30 30 30 30 30
> do_syncrep2: rid=001 CSN too old, ignoring
> I am not exactly sure how it gotten to be "too old." The ldif I am
> importing is not the result of a slapcat or anything that would preserve
> the CSN or UUID attributes (not that syncrepl uses UUID). I am loading
> one single file with ldapadd which, in my understanding, sets up the CSN
> and wouldn't let me import one anyway.
> Each server has no entries until I load the one, so there shouldn't be
> any weird stale CSNs causing this. They are "sync'ed" almost instantly
> after the one system is loaded - I just don't have everything.
> After a sync:
> ldap1 - slapcat |grep dn: |wc -l = 41
> ldap2 - slapcat |grep dn: |wc -l = 18
> Right now I can get them in sync with a slapcat/slapadd, but when the go
> into production I wont be able to say for certain which one is
> authoritative. That is the purpose of multi-master....
> OpenLDAP 2.4.13, built by me (passed all tests) on Ubuntu Linux 32 bit
> Any ideas as to what I can do to stop this from happening?
Sent from my mobile device