Appendix B. Replication Agreement Status In the read-only nsds5replicaLastUpdateStatus attribute of each replication agreement, Directory Server displays the latest status of the agreement. The following is a list of possible statuses: Disabled agreements If a replication agreement is disabled, the nsds5replicaLastUpdateStatus parameter is no longer updated and can display the following status: The replication agreement was already disabled when the server started: The agreement was disabled during run time. General agreement status The replication agreement was stopped: An incremental update was started: An incremental update succeeded: Replication succeeded, but the consumer ended the session to be able to get acquired by another supplier: Error messages in the ACQUIRING_REPLICA state During the first part of a replication session, the supplier acquires the consumer, establishes the connection, binds to the consumer, verifies that the consumer is not already updated by another supplier, and performs additional checks. The following error codes can be displayed in this state: Failures during establishing a connection with the consumer: The result code and error message indicates the reason why the connection could not be established. An internal error occurred on the consumer: This error is caused by a failure related to the change sequence number (CSN) generator on the consumer. See the consumer log files for further details. The identity used to authenticate to the consumer was neither a valid replication bind distinguished name (DN) nor a member of a bind DN group: No valid replica was defined for the suffix on the consumer: Decoding error of the replication control sent to the consumer: The replica is currently updated by a different supplier: The supplier and consumer use the same replica ID: The supplier or the consumer is incorrectly configured. Set a unique replica ID in the replication configuration to fix the problem. The supplier was set into backoff mode: This state is only displayed when a custom replication hook is implemented. Decoding errors of the replication control received from the consumer: Error messages in the SENDING_UPDATES state After a replica was successfully acquired, the session starts sending updates. In this state, the following messages can be displayed in the respective steps: Examining the replica update vector (RUV): The replica has no update vector configured or replication was not enabled on the consumer: The consumer was not initialized using the same database generation as the supplier: To fix the problem, initialize either the supplier or the consumer. Updating the change state number (CSN) generator: The time difference between the local and the remove server is too big: Directory Server failed to update the CSN generator: Initial changelog positioning: General error in case that the changelog cannot be processed: This error is logged, for example, if the path to the changelog file does not exist. Parsing an entry in the changelog failed: Errors related to the database layer of the changelog: For further details, see the /var/log/dirsrv/slapd- instance_name /errors log file. Directory Server failed to allocate memory: This error is logged, for example, if the changelog buffer or changelog iterator failed to allocate memory. The supplier is ahead of the consumer and wants to send updates, but cannot find the starting point in the changelog: Directory Server treats these errors as fatal, but they can be resolved if the consumer receives the updates from a different supplier. In this case, it is treated as transient. Sending the update: Creating a result thread failed: The result code indicates the reason why the thread was not created. General error in case that the changelog cannot be processed: This error is logged, for example, if the path to the changelog file does not exist. A database error occurred while reading the change log: This event is logged, for example, if Directory Server access a locked database page. Directory Server ran out The creation : Sub-entry update: The creation of the replica keep alive entry failed: General status in the SEND_UPDATES state: A non-fatal error occurred on the local server while processing the changelog: See the /var/log/dirsrv/slapd- instance_name /errors file for further details. A replication connection was disconnected after the connection was established: A timeout appeared on an existing replication connection: The replication automatically tries to resume later.

Commands:
Error (0) No replication sessions started since server startup
Error (0) Replica acquired successfully: agreement disabled
{blank}
Error (0) Replica acquired successfully: Protocol stopped
Error (0) Replica acquired successfully: Incremental update started
Error (0) Replica acquired successfully: Incremental update succeeded
Error (0) Replica acquired successfully: Incremental update succeeded and yielded
Error ( result_code ) Problem connecting to replica - LDAP error: ldap_error_message
Error ( result_code ) Problem connecting to replica (SSL not enabled) - LDAP error: ldap_error_message
Error (8) :Failed to acquire replica: Internal error occurred on the remote replica
Error (3) :Unable to acquire replica: permission denied. The bind dn does not have permission to supply replication updates to the replica. Will retry later.
Error (6) :Unable to acquire replica: there is no replicated area on the consumer server. Replication is aborting.
Error (4) :Unable to acquire replica: the consumer was unable to decode the startReplicationRequest extended operation sent by the supplier. Replication is aborting.
Error (1) :Unable to acquire replica: the replica is currently being updated by another supplier.
Error (11) :Unable to aquire replica: the replica has the same Replica ID as this one. Replication is aborting.
Error (14) :Unable to acquire replica: the replica instructed us to go into backoff mode. Will retry later.
Error (extop_result) :Unable to acquire replica
Error (4) Unable to parse the response to the startReplication extended operation. Replication is aborting.
Error (16) Unable to receive the response for a startReplication extended operation to consumer. Will retry later.
Error (0) Unable to obtain current CSN. " "Replication is aborting.
Error (19) : Replica is not initialized
Error (19) : Replica has different database generation ID, remote replica may need to be initialized
Error (2) : fatal error - too much time skew between replicas
Error (2) : fatal internal error updating the CSN generator
Error (15) : Unexpected format encountered in changelog database
Error (15) : Unexpected format encountered in changelog database
Error (15) : Changelog database was in an incorrect state
Error (15) : Incorrect dbversion found in changelog database
Error (15) : Changelog database error was encountered
Error (15) : changelog memory allocation error occurred
Error (15) : Data required to update replica has been purged from the changelog. " "The replica must be reinitialized.
Error (15) : Changelog data is missing
Error ( result_code ) : Failed to create result thread
Error (15) : Invalid parameter passed to cl5GetNextOperationToReplay
Error (15) : Database error occurred while getting the next operation to replay
Error (15) : Memory allocation error occurred (cl5GetNextOperationToReplay)
Error (-1) : Agreement is corrupted: missing suffix
Error (18) : Incremental update transient error. Backing off, will retry update later.
Error (16) : Incremental update connection error. Backing off, will retry update later.
Error (17) : Incremental update timeout error. Backing off, will retry update later.