I'm having another replication problem where changes made on a particular server are
not being replicated outward at all. Right now, I'm trying to determine what's
going on during the replication process.
(Caveat: I'm still running an old version of 389ds: v1.3.10. In particular, the dsconf
utility does not exist.)
My understanding is that when a server receives a change from a client, it wraps it up as
a CSN and starts a replication session with its peers, during which it sends a message
that states the greatest CSN that it originated. First off, is that a correct
understanding?
If so, how can I determine what CSN a particular server is telling its replication peers
during those sessions? I have a feeling that this server is, for some reason, sending an
inaccurate number.
In the cn=replica,cn=...,cn=mapping tree,cn=config tree, there are entries for each of the
servers topology peers, and they contain nsds50ruv attributes that seem to be the RUVs
that that server has received from those peers, right? But the nsds50ruv attribute also
exists directly in the cn=replica if you explicitly ask for it. Is it possible that this
is the server's own RUV?
Can I rely on the nsds50ruv attributes on this server's peers' cn=replica
nsds50ruv attribute values to be an accurate reflection of what this server is sending as
its CSN in replication sessions?
Any other way to see what's going on in a replication session? (I'm even trying to
decrypt a network capture, but I'm not having any luck with that yet.)
In particular, I see the max CSN for this server in all of these RUVs less than CSNs
recorded in the server's own log files.
--
William Faulk