| | |
| | | base dn : %s |
| | | MILD_ERR_ERROR_SEARCHING_RUV_15=Error %s when searching for server state %s : \ |
| | | %s base dn : %s |
| | | NOTICE_NO_CHANGELOG_SERVER_LISTENING_17=There is no replication server \ |
| | | listening on %s |
| | | NOTICE_FOUND_CHANGELOGS_WITH_MY_CHANGES_18=Found %d replication server(s) with \ |
| | | up to date changes for suffix %s, in server id %s |
| | | NOTICE_NEED_MORE_THAN_ONE_CHANGELOG_SERVER_19=More than one replication \ |
| | |
| | | NOTICE_COULD_NOT_FIND_CHANGELOG_WITH_MY_CHANGES_22=Could not find a \ |
| | | replication server that has seen all the local changes on suffix %s. Found %d \ |
| | | replications server(s) not up to date. Going to replay changes |
| | | NOTICE_COULD_NOT_FIND_CHANGELOG_23=Could not connect to any replication \ |
| | | server on suffix %s among the following RS candidates %s, retrying... |
| | | NOTICE_EXCEPTION_CLOSING_DATABASE_24=Error closing Replication Server database \ |
| | | %s : |
| | | SEVERE_ERR_EXCEPTION_DECODING_OPERATION_25=Error trying to replay %s, \ |
| | |
| | | This replication server will now shutdown |
| | | SEVERE_ERR_REPLICATION_COULD_NOT_CONNECT_61=The Replication is configured for \ |
| | | suffix %s but was not able to connect to any Replication Server |
| | | NOTICE_NOW_FOUND_SAME_GENERATION_CHANGELOG_62=Replication is up and running \ |
| | | for domain %s with replication server id %s %s - local server id is %s - data \ |
| | | generation is %s |
| | | NOTICE_REPLICATION_SERVER_PROPERLY_DISCONNECTED_63=Replication server %s \ |
| | | %s has properly disconnected for %s in local server id %s. Trying to reconnect \ |
| | | to a suitable replication server |
| | | SEVERE_ERR_CHANGELOG_ERROR_SENDING_ERROR_65=An unexpected error occurred \ |
| | | while sending an Error Message to %s. This connection is going to be closed \ |
| | | and reopened |
| | |
| | | searching in %s for the generation ID : %s |
| | | SEVERE_ERR_UPDATING_GENERATION_ID_76=An unexpected error %s occurred \ |
| | | when updating generation ID for the domain : %s |
| | | NOTICE_BAD_GENERATION_ID_FROM_RS_77=On suffix %s, replication server %s presented \ |
| | | generation ID=%s when expected generation ID=%s |
| | | NOTICE_RESET_GENERATION_ID_78=The generation ID has been reset for domain %s. \ |
| | | New reference generation id is %s |
| | | MILD_ERR_ERROR_MSG_RECEIVED_79=The following error has been received : %s |
| | | MILD_ERR_IGNORING_UPDATE_FROM_RS_80=In RS %s for dn %s, update %s received from \ |
| | | RS %s is ignored due to a bad generation id of remote RS (local genid: \ |
| | | %s, remote genid: %s) |
| | | MILD_ERR_IGNORING_UPDATE_TO_RS_81=In RS %s for dn %s, update %s will not be sent \ |
| | | to RS %s with generation id %s different from local generation id %s |
| | | SEVERE_ERR_INIT_IMPORT_NOT_SUPPORTED_82= Initialization cannot be done because \ |
| | | import is not supported by the backend %s |
| | | SEVERE_ERR_INIT_EXPORT_NOT_SUPPORTED_83= Initialization cannot be done because \ |
| | |
| | | the replication server backend |
| | | SEVERE_ERR_UNKNOWN_DN_95=The base DN %s is not stored by any of the \ |
| | | Directory Server backend |
| | | NOTICE_NOW_FOUND_BAD_GENERATION_CHANGELOG_96=Replication is connected to \ |
| | | replication server, but has a different generation id for domain %s than \ |
| | | replication server %s - local data generation is %s - replication server data \ |
| | | generation is %s - This may be only temporary or requires a full \ |
| | | resynchronization |
| | | NOTICE_HEARTBEAT_FAILURE_97=%s is closing the session \ |
| | | because it could not detect a heartbeat |
| | | SEVERE_ERR_REPLICATONBACKEND_IMPORT_LDIF_NOT_SUPPORTED_98=The replication \ |
| | | server backend does not support the import ldif function |
| | | SEVERE_ERR_REPLICATONBACKEND_EXPORT_LDIF_FAILED_99=The replication \ |
| | | server backend cannot export its entries in LDIF format because the \ |
| | | export-ldif command must be run as a task |
| | | NOTICE_SSL_SERVER_CON_ATTEMPT_ERROR_105=SSL connection attempt from %s (%s) \ |
| | | failed: %s |
| | | SEVERE_ERR_MISSING_REMOTE_MONITOR_DATA_106=Timed out waiting for monitor data \ |
| | | for the domain "%s" from replication server RS(%d) |
| | | SEVERE_ERR_PROCESSING_REMOTE_MONITOR_DATA_107=Monitor data of remote servers \ |
| | | are missing due to a processing error : %s |
| | | SEVERE_ERR_SENDING_REMOTE_MONITOR_DATA_REQUEST_108=Unable to send monitor data \ |
| | |
| | | any replication server. You should \ |
| | | check in the configuration that the domain is enabled and that there is one \ |
| | | replication server up and running |
| | | SEVERE_ERR_EXCEPTION_STARTING_SESSION_PHASE_119=Caught Exception during initial \ |
| | | communication (phase %s) on domain %s with replication server %s : %s |
| | | NOTICE_NEW_SERVER_WITH_SAME_GROUP_ID_120=Disconnecting from replication server \ |
| | | as a new one with our group id (%s) just arrived in topology. This is for \ |
| | | domain %s and we have server id %s |
| | |
| | | generation id: %s |
| | | SEVERE_ERR_RECEIVED_CHANGE_STATUS_NOT_FROM_DS_130=Received change status \ |
| | | message does not come from a directory server (dn: %s, server id: %s, msg: %s) |
| | | NOTICE_DIRECTORY_SERVER_CHANGED_STATUS_131=Directory server %s for dn %s \ |
| | | changed his status to %s |
| | | SEVERE_ERR_RS_INVALID_NEW_STATUS_132=Received invalid new status %s \ |
| | | in RS for replication domain %s and directory server id %s |
| | | SEVERE_WARN_CONNECTED_TO_SERVER_WITH_WRONG_GROUP_ID_133=Connected to a \ |
| | |
| | | server id %s %s has group id %s. This is for domain %s in directory server %s |
| | | SEVERE_ERR_EXCEPTION_SENDING_CS_134=Replication broker with dn %s and server \ |
| | | id %s failed to signal status change because of: %s |
| | | MILD_ERR_IGNORING_UPDATE_FROM_DS_BADGENID_135=In RS %s for dn %s, update %s \ |
| | | received from DS %s is ignored due to a bad generation id of DS (local genid: \ |
| | | %s, remote genid: %s) |
| | | MILD_ERR_IGNORING_UPDATE_TO_DS_BADGENID_136=In RS %s for dn %s, update %s will \ |
| | | not be sent to DS %s with generation id %s different from local generation id %s |
| | | MILD_ERR_IGNORING_UPDATE_FROM_DS_FULLUP_137=In RS %s for dn %s, update %s \ |
| | | received from DS %s is ignored due to DS in full update |
| | | MILD_ERR_IGNORING_UPDATE_TO_DS_FULLUP_138=In RS %s for dn %s, update %s will \ |
| | | not be sent to DS %s in full update |
| | | SEVERE_ERR_EXCEPTION_CHANGING_STATUS_FROM_STATUS_ANALYZER_139=Caught \ |
| | | IOException while changing status for domain %s and serverId: %s from status \ |
| | | analyzer: %s |
| | | NOTICE_BAD_GEN_ID_IN_FULL_UPDATE_140=Replication server %s for dn %s: directory \ |
| | | server %s must stay in full update although a generation id reset has been \ |
| | | ordered (from %s to %s) |
| | | NOTICE_FULL_UPDATE_ENGAGED_FROM_REMOTE_START_141=Local directory server %s is \ |
| | | starting online full update for importing suffix %s data from remote \ |
| | | directory server %s |
| | | NOTICE_FULL_UPDATE_ENGAGED_FROM_REMOTE_END_142=Local directory server %s has \ |
| | | finished online full update for importing suffix %s data from remote \ |
| | | directory server %s. %s |
| | | NOTICE_FULL_UPDATE_ENGAGED_FOR_REMOTE_START_143=Local directory server %s is \ |
| | | starting online full update for exporting %s entries from suffix %s \ |
| | | to remote directory server %s |
| | | NOTICE_FULL_UPDATE_ENGAGED_FOR_REMOTE_END_144=Local directory server %s has \ |
| | | finished online full update for exporting suffix data %s to remote directory \ |
| | | server %s. %s |
| | | NOTICE_TIMEOUT_WHEN_CROSS_CONNECTION_145=Timed out trying to acquire the domain \ |
| | | lock for %s. Connection attempt from replication server %s to local replication \ |
| | | server %s will be aborted. Simultanate cross connection attempt ? |
| | | NOTICE_BAD_GENERATION_ID_FROM_DS_146=On suffix %s, directory server %s presented \ |
| | | generation ID=%s when expected generation ID=%s |
| | | NOTICE_DS_RECEIVED_ACK_ERROR_147=In replication service %s and server id %s, the \ |
| | | assured update message %s was acknowledged with the following errors: %s |
| | | NOTICE_DS_ACK_TIMEOUT_148=In replication service %s, timeout after %s ms \ |
| | |
| | | SEVERE_ERR_RS_DISCONNECTED_DURING_HANDSHAKE_179=Replication server %s was \ |
| | | attempting to connect to replication server %s but has disconnected in \ |
| | | handshake phase |
| | | SEVERE_ERR_REPLICATION_SERVER_BADLY_DISCONNECTED_180=The connection to \ |
| | | replication server %s %s has been unexpectedly dropped by the replication \ |
| | | server for %s in local server id %s |
| | | SEVERE_ERR_SERVER_BADLY_DISCONNECTED_181= %s has badly disconnected from this \ |
| | | replication server %s |
| | | NOTICE_ERR_UNABLE_TO_ENABLE_ECL_VIRTUAL_ATTR_182=Error when loading a virtual \ |
| | | attribute for external change log: Attribute: %s , Error: %s |
| | | NOTICE_ERR_UNABLE_TO_ENABLE_ECL_183=Error in %s when enabling the external \ |
| | |
| | | required. Reason: The provided cookie is older than the start of historical \ |
| | | in the server for the replicated domain : %s |
| | | SEVERE_ERR_INVALID_COOKIE_SYNTAX_187=Invalid syntax of the provided cookie |
| | | NOTICE_NEW_BEST_REPLICATION_SERVER_188=Domain %s (server id: %s) : \ |
| | | disconnecting from this replication server (server id: %s, url: %s) : as a \ |
| | | new one %s is more suitable |
| | | MILD_ERR_INIT_EXPORTER_DISCONNECTION_189=Domain %s (server id: %s) : \ |
| | | remote exporter server disconnection (server id: %s ) detected during \ |
| | | initialization |
| | |
| | | with DN : %s ERROR : %s |
| | | NOTICE_MONITOR_DATA_RECEIVED_203=Monitor data for the domain "%s" has been \ |
| | | received from replication server RS(%d) |
| | | NOTICE_REPLICATION_SERVER_LISTENING_204=Replication server RS(%d) started \ |
| | | listening for new connections on address %s port %d |
| | | INFO_REPLICATION_SERVER_CONNECTION_TO_RS_205=Replication server RS(%d) has \ |
| | | connected to replication server RS(%d) for domain "%s" at %s |
| | | INFO_REPLICATION_SERVER_CONNECTION_FROM_RS_206=Replication server RS(%d) has \ |
| | | accepted a connection from replication server RS(%d) for domain "%s" at %s |
| | | INFO_REPLICATION_SERVER_CONNECTION_FROM_DS_207=Replication server RS(%d) has \ |
| | | accepted a connection from directory server DS(%d) for domain "%s" at %s |
| | | NOTICE_NOW_FOUND_SAME_GENERATION_CHANGELOG_62=Directory server DS(%d) has \ |
| | | connected to replication server RS(%d) for domain "%s" at %s with \ |
| | | generation ID %d |
| | | SEVERE_WARN_NOW_FOUND_BAD_GENERATION_CHANGELOG_96=Directory server DS(%d) has \ |
| | | connected to replication server RS(%d) for domain "%s" at %s, but the \ |
| | | generation IDs do not match, indicating that a full re-initialization is \ |
| | | required. The local (DS) generation ID is %d and the remote (RS) generation \ |
| | | ID is %d |
| | | SEVERE_WARN_COULD_NOT_FIND_CHANGELOG_23=Directory server DS(%d) was unable to \ |
| | | connect to any of the following replication servers for domain "%s": %s |
| | | SEVERE_WARN_NO_AVAILABLE_CHANGELOGS_208=Directory server DS(%d) was unable to \ |
| | | connect to any replication servers for domain "%s" |
| | | MILD_WARN_REPLICATION_SERVER_PROPERLY_DISCONNECTED_63=Replication server RS(%d) \ |
| | | at %s has closed the connection to this directory server DS(%d). This \ |
| | | directory server will now try to connect to another replication \ |
| | | server in order to receive changes for the domain "%s" |
| | | SEVERE_WARN_REPLICATION_SERVER_BADLY_DISCONNECTED_180=Directory server DS(%d) \ |
| | | encountered an error while receiving changes for domain "%s" from replication \ |
| | | server RS(%d) at %s. The connection will be closed, and this directory \ |
| | | server will now try to connect to another replication server |
| | | NOTICE_NEW_BEST_REPLICATION_SERVER_188=Directory Server DS(%d) is switching \ |
| | | from replication server RS(%d) at %s to RS(%d) for domain "%s" because it is \ |
| | | more suitable |
| | | NOTICE_FULL_UPDATE_ENGAGED_FROM_REMOTE_START_141=Starting total update: \ |
| | | importing domain "%s" from remote directory server DS(%d) to this directory \ |
| | | server DS(%d) |
| | | NOTICE_FULL_UPDATE_ENGAGED_FROM_REMOTE_END_142=Finished total update: \ |
| | | imported domain "%s" from remote directory server DS(%d) to this directory \ |
| | | server DS(%d). %s |
| | | NOTICE_FULL_UPDATE_ENGAGED_FOR_REMOTE_START_143=Starting total update: \ |
| | | exporting %d entries in domain "%s" from this directory server DS(%d) to \ |
| | | remote directory server DS(%d) |
| | | NOTICE_FULL_UPDATE_ENGAGED_FOR_REMOTE_START_ALL_209=Starting total update: \ |
| | | exporting %d entries in domain "%s" from this directory server DS(%d) to \ |
| | | all remote directory servers |
| | | NOTICE_FULL_UPDATE_ENGAGED_FOR_REMOTE_END_144=Finished total update: \ |
| | | exported domain "%s" from this directory server DS(%d) to \ |
| | | remote directory server DS(%d). %s |
| | | NOTICE_FULL_UPDATE_ENGAGED_FOR_REMOTE_END_ALL_210=Finished total update: \ |
| | | exported domain "%s" from this directory server DS(%d) to all \ |
| | | remote directory servers. %s |
| | | NOTICE_DIRECTORY_SERVER_CHANGED_STATUS_131=Directory server DS(%d) for domain \ |
| | | "%s" has changed its status to %s |
| | | SEVERE_WARN_HEARTBEAT_FAILURE_97=Directory server DS(%d) is closing \ |
| | | its connection to replication server RS(%d) at %s for domain "%s" \ |
| | | because it could not detect a heart beat |
| | | SEVERE_WARN_BAD_GENERATION_ID_FROM_RS_77=Replication server RS(%d) at %s \ |
| | | presented generation ID %d for domain "%s", but the generation ID of this \ |
| | | replication server RS(%d) is %d. This usually indicates that one or more \ |
| | | directory servers in the replication topology have not been initialized with \ |
| | | the same data, and re-initialization is required |
| | | NOTICE_RESET_GENERATION_ID_78=The generation ID for domain "%s" has been reset \ |
| | | to %d |
| | | SEVERE_WARN_TIMEOUT_WHEN_CROSS_CONNECTION_145=Timed out while trying to \ |
| | | acquire the domain lock for domain "%s". The connection attempt from replication \ |
| | | server RS(%d) at %s to this replication server RS(%d) will be aborted. This \ |
| | | is probably benign and a result of a simultaneous cross connection attempt |
| | | MILD_WARN_BAD_GENERATION_ID_FROM_DS_146=Directory server DS(%d) at %s \ |
| | | presented generation ID %d for domain "%s", but the generation ID of this \ |
| | | replication server RS(%d) is %d. This usually indicates that one or more \ |
| | | directory servers in the replication topology have not been initialized with \ |
| | | the same data, and re-initialization is required |
| | | SEVERE_WARN_IGNORING_UPDATE_FROM_RS_80=Replication server RS(%d) ignoring update \ |
| | | %s for domain "%s" from replication server RS(%d) at %s because its \ |
| | | generation ID %d is different to the local generation ID %d |
| | | SEVERE_WARN_IGNORING_UPDATE_TO_RS_81=Replication server RS(%d) not sending update \ |
| | | %s for domain "%s" to replication server RS(%d) at %s because its \ |
| | | generation ID %d is different to the local generation ID %d |
| | | SEVERE_WARN_IGNORING_UPDATE_FROM_DS_BADGENID_135=Replication server RS(%d) ignoring update \ |
| | | %s for domain "%s" from directory server DS(%d) at %s because its \ |
| | | generation ID %d is different to the local generation ID %d |
| | | SEVERE_WARN_IGNORING_UPDATE_TO_DS_BADGENID_136=Replication server RS(%d) not sending update \ |
| | | %s for domain "%s" to directory server DS(%d) at %s because its \ |
| | | generation ID %d is different to the local generation ID %d |
| | | SEVERE_WARN_IGNORING_UPDATE_FROM_DS_FULLUP_137=Replication server RS(%d) ignoring update \ |
| | | %s for domain "%s" from directory server DS(%d) at %s because it is currently \ |
| | | performing a full update |
| | | SEVERE_WARN_IGNORING_UPDATE_TO_DS_FULLUP_138=Replication server RS(%d) not sending update \ |
| | | %s for domain "%s" to directory server DS(%d) at %s because it is currently \ |
| | | performing a full update |
| | | SEVERE_ERR_RS_BADLY_DISCONNECTED_181=The connection from this replication \ |
| | | server RS(%d) to replication server RS(%d) at %s for domain "%s" has failed |
| | | SEVERE_ERR_DS_BADLY_DISCONNECTED_211=The connection from this replication \ |
| | | server RS(%d) to directory server DS(%d) at %s for domain "%s" has failed |
| | | SEVERE_WARN_NO_CHANGELOG_SERVER_LISTENING_17=Directory server DS(%d) was \ |
| | | unable to connect to replication server %s for domain "%s". Please \ |
| | | check that there is a replication server listening at this address |
| | | SEVERE_WARN_TIMEOUT_CONNECTING_TO_RS_212=Directory server DS(%d) timed out \ |
| | | while connecting to replication server %s for domain "%s" |
| | | SEVERE_WARN_EXCEPTION_STARTING_SESSION_PHASE_119=Directory server DS(%d) \ |
| | | encountered an unexpected error while connecting to replication server \ |
| | | %s for domain "%s": %s |
| | | INFO_SSL_SERVER_CON_ATTEMPT_ERROR_105=Replication server accepted a connection \ |
| | | from %s to local address %s but the SSL handshake failed. This is probably \ |
| | | benign, but may indicate a transient network outage or a misconfigured client \ |
| | | application connecting to this replication server. The error was: %s |
| | | SEVERE_WARN_MISSING_REMOTE_MONITOR_DATA_106=Timed out waiting for monitor data \ |
| | | for the domain "%s" from replication server RS(%d) |
| | | |