Hi!
I have a support case from SUSE's version of slapd open, and I wonder about one
specific statement from support:
A core dump is triggered by
syncprov.c:2360:
assert( !BER_BVISEMPTY( &oldestcsn ) && !BER_BVISEMPTY( &newestcsn ) &&
ber_bvcmp( &oldestcsn, &newestcsn ) < 0 );
Support explained: "Any of these indicates the changelog (accesslog) is in a
completely inconsistent or corrupted state."
The support recommends to reset the CSNs by disabling any replication (which
doesn't remove those IMHO) and "either using syncrepl or delta-syncrepl, but
not mixing both.":
I don't see a problem if one dependent server gets the changed through "classic
methods" (e.g. Refresh), and another server gets updates through
delte-syncrepl. Am I wrong?
Finally support concludes: "Please note that these types of replication
integrity issues do not affect 389 Directory Server, which uses a more robust
mechanism for change tracking and includes a proper Lamport clock
implementation."
Well, I actually tried 389DS, but the conversion tool was highly incomplete,
the schemata and ACL mechanism were completely different, and there was not a
single current book for it available, so I resigned.
Feel free to comment.
Kind regards,
Ulrich Windl
