Red Hat Directory Server 8.0 Administrator's Guide

Error/Symptom Reason Impact Remedy
maximum time lag
from the replication
monitor among all the
consumers.
Irrespective of what
the purge threshold
is, no change will be
purged before it is
replayed by all the
consumers.
The Replication
Monitor is not
responding. (For
information on
Replication Monitor,
see Section 17,
“Monitoring
Replication Status”.)
The SSL port is
specified in some
replication
agreement, but the
certificate database is
not specified or not
accessible by the
Replication Monitor. If
there is no SSL port
problem, one of the
servers in the
replication topology
might hang.
Map the SSL port to a
non-SSL port in the
configuration file of
the Replication
Monitor. For example,
if 636 is the SSL port
and 389 is the
non-SSL port, add the
following line in the
[connection]
section:
*:636=389:*:password
In the Replication
Monitor, some
consumers show just
the header of the
table. (For information
on Replication
Monitor, see
Section 17,
“Monitoring
Replication Status”.)
No change has
originated from the
corresponding
suppliers. In this
case, the MaxCSN: in
the header part
should be "None".
There is nothing
wrong if there is no
change originated
from a supplier.
Table 8.7. Replication Errors
Troubleshooting Replication-Related
351