Red Hat DIRECTORY SERVER 7.1 - ADMINISTRATOR Administrator's Manual page 372

Troubleshooting Replication-Related Problems
With changelog purge turned on, a purge thread that wakes up every five
minutes will remove a change if its age is greater than the value of
nsslapd-changelogmaxage
consumers of this supplier (supplier or hub).
If it appears that the changelog is not purged when the purge threshold is
reached, check the 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.
Symptom:
The Replication Monitor is not responding. (For information on Replication
Monitor, see "Monitoring Replication Status," on page 360.)
Reason: 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.
Remedy: 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
Symptom:
In the Replication Monitor, some consumers show just the header of the table.
(For information on Replication Monitor, see "Monitoring Replication Status," on
page 360.)
Reason: No change has originated from the corresponding suppliers. In this
case, the
Remedy: There is nothing wrong if there is no change originated from a
supplier.
372 Red Hat Directory Server Administrator's Guide • May 2005
*:636=389:*:password
in the header part should be
MaxCSN:
and if it has been replayed to all the direct
[connection]
"None"
section:
.