HP-UX Directory Server 8.1 administrator guide

The cl-dump.pl script, which is explained in detail in the HP-UX Directory Server configuration,
command, and file reference can also help troubleshoot replication-related problems. Depending
on the usage options, the script can selectively dump a particular replica:
• Dump the contents of a replication-change-log file and in-memory variables purge
RUV and maxRUV.
• grep and interpret change sequence numbers (CSNs) in the changelog.
• Get the base-64 encoded changelog from the Directory Server, then decode the changelog.
Many common replication problems are described in Table 8-7 “Replication errors”.
Table 8-7 Replication errors
RemedyImpactReasonError/symptom
Ignore this message if it
occurs before the consumer
is initialized. Otherwise,
reinitialize the consumer if
the message is persistent. In
a multi-master environment,
all the servers should be
initialized only once from a
root supplier, directly or
indirectly. For example, M1
initializes M2 and M4, M2
then initializes M3, and so
on. The important thing to
note is that M2 must not start
initializing M3 until M2's
own initialization is done
(check the total update status
from the M1's Console or M1
or M2's errors log). Also, M2
should not initialize M1 back.
The local supplier will not
replicate any data to the
consumer.
The consumer specified at
the beginning of this
message has not been
(successfully) initialized yet,
or it was initialized from a
different root supplier.
agmt=%s (%s:%d) Replica
has a different generation
ID than the local data.
Check the disk space and the
possible core file (under the
server's logs directory). If this
is a single-master replication,
reinitialize the consumers.
Otherwise, if the server later
complains that it cannot
locate some CSN for a
consumer, see if the
consumer can get the CSN
from other suppliers. If not,
reinitialize the consumer.
The server will not be able
to send the changes to a
consumer if the
consumer's maxcsn no
longer exists in the server's
changelog.
This message may appear
only when a supplier is
restarted. It indicates that
the supplier was unable to
write the changelog or did
not flush out its RUV at its
last shutdown. The former
is usually because of a
disk-space problem, and the
latter because a server
crashed or was ungracefully
shut down.
Warning: data for replica's
was reloaded, and it no
longer matches the data in
the changelog. Recreating
the changelog file. This
could affect replication with
replica's consumers, in
which case the consumers
should be reinitialized.
If this is a single-master
replication, reinitialize the
consumers. Otherwise, see if
the consumer can get the
CSN from other suppliers. If
not, reinitialize the consumer.
The local server will not be
able to send any more
change to that consumer
until the consumer is
reinitialized or gets the
CSN from other suppliers.
Most likely the changelog
was recreated because of the
disk is full or the server
ungracefully shutdown.
agmt=%s(%s:%d): Cannot
locate CSN %s in the
changelog (DB rc=%d). The
consumer may need to be
reinitialized.
390 Managing replication