HP-UX Directory Server Administrator Guide HP-UX Directory Server Version 8.1 (5900-3098, May 2013)

Table 42 Replication errors (continued)
RemedyImpactReasonError/symptom
the M1's Console or M1 or
M2's errors log). Also, M2
should not initialize M1 back.
Check the disk space and the
possible core file (under the
The server will not be able
to send the changes to a
This message may appear
only when a supplier is
Warning: data for replica's
was reloaded, and it no
server's logs directory). If thisconsumer if the consumer'srestarted. It indicates that thelonger matches the data in
is a single-master replication,maxcsn no longer exists in
the server's changelog.
supplier was unable to write
the changelog or did not
flush out its RUV at its last
the changelog. Recreating
the changelog file. This
could affect replication with
reinitialize the consumers.
Otherwise, if the server later
shutdown. The former isreplica's consumers, in complains that it cannot
usually because of awhich case the consumers
should be reinitialized.
locate some CSN for a
consumer, see if the consumerdisk-space problem, and the
can get the CSN from otherlatter because a server
suppliers. If not, reinitialize
the consumer.
crashed or was ungracefully
shut down.
If this is a single-master
replication, reinitialize the
The local server will not be
able to send any more
Most likely the changelog
was recreated because of
agmt=%s(%s:%d): Cannot
locate CSN %s in the
consumers. Otherwise, see ifchange to that consumerthe disk is full or the server
ungracefully shutdown.
changelog (DB rc=%d). The
consumer may need to be
reinitialized.
the consumer can get the
CSN from other suppliers. If
not, reinitialize the consumer.
until the consumer is
reinitialized or gets the
CSN from other suppliers.
Synchronize the system clocks
on the Directory Server host
The system clock is used to
generate a part of the
The system clocks on the host
machines are extremely out
of sync.
Too much time skew
machines. If applicable, runCSN. In order to reflect the
the network time protocol
(ntp) daemon on those hosts.
change sequence among
multiple suppliers, suppliers
would forward-adjust their
local clocks based on the
remote clocks of the other
suppliers. Because the
adjustment is limited to a
certain amount, any
difference that exceeds the
permitted limit will cause
the replication session to be
aborted.
Watch if the consumer can
receive any new change from
If the consumer recovers
without being restarted,
The consumer is not
responding.
agmt=%s(%s:%d):
Warning: Unable to send
any of its suppliers, or startthere is a chance that the
endReplication extended
operation (%s)
the replication monitor, and
see if all the suppliers of this
replica on the consumer
will be locked forever if it
consumer warn that thedid not receive the release
replica is busy. If the replicalock message from the
supplier. appears to be locked forever
and no supplier can get in,
restart the consumer.
By default changelog purge
is turned off. To turn it on from
Either changelog purge is
turned off, which is the
Changelog is getting too
big.
the command line, run
ldapmodify as follows:
dn:
cn=changelog5,cn=config
default setting, or changelog
purge is turned on, but some
consumers are way behind
the supplier.
changetype: modify
add:
nsslapd-changelogmaxage
nsslapd-changelogmaxage:
1d
8.19 Troubleshooting replication-related problems 389