HP-UX Directory Server 8.1 administrator guide

Table 8-7 Replication errors (continued)
RemedyImpactReasonError/symptom
By default changelog purge
is turned off. To turn it on
from the command line, run
ldapmodify as follows:
dn:
cn=changelog5,cn=config
changetype: modify
add:
nsslapd-changelogmaxage
nsslapd-changelogmaxage:
1d
Where 1d means 1 day.
Other valid time units are s
for seconds, m for minutes, h
for hours, and w for weeks.
A value of 0 turns off the
purge.
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
and if it has been replayed to
all the direct 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.
Either changelog purge is
turned off, which is the
default setting, or changelog
purge is turned on, but
some consumers are way
behind the supplier.
Changelog is getting too
big.
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
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.
The Replication Monitor is
not responding. For
information on Replication
Monitor, see “Monitoring
replication status”.
There is nothing wrong if
there is no change originated
from a supplier.
No change has originated
from the corresponding
suppliers. In this case, the
MaxCSN: in the header part
should be "None".
In the Replication Monitor,
some consumers show just
the header of the table. For
information on Replication
Monitor, see “Monitoring
replication status”.
392 Managing replication