6766N/A# The contents of this file are subject to the terms of the
6766N/A# Common Development and Distribution License, Version 1.0 only
6766N/A# (the "License"). You may not use this file except in compliance
6766N/A# You can obtain a copy of the license at
6766N/A# See the License for the specific language governing permissions
6766N/A# and limitations under the License.
6766N/A# When distributing Covered Code, include this CDDL HEADER in each
6766N/A# file and include the License file at
6766N/A# add the following below this CDDL HEADER, with the fields enclosed
6766N/A# by brackets "[]" replaced with your own identifying information:
6766N/A# Portions Copyright [yyyy] [name of copyright owner]
6766N/A# Copyright 2006-2010 Sun Microsystems, Inc.
6766N/A# Portions copyright 2011-2014 ForgeRock AS
6766N/A# This file contains the primary Directory Server configuration. It must not
6766N/A# be directly edited while the server is online. The server configuration
6766N/A# should only be managed using the administration utilities provided with the
6766N/A# Keys must be formatted as follows:
6766N/A# [SEVERITY]_[DESCRIPTION]_[ORDINAL]
6766N/A# [INFO, MILD_WARN, SEVERE_WARN, MILD_ERR, SEVERE_ERR, FATAL_ERR, DEBUG, NOTICE]
6766N/A# DESCRIPTION is an upper case string providing a hint as to the context of
6766N/A# the message in upper case with the underscore ('_') character serving as
6766N/A# ORDINAL is an integer unique among other ordinals in this file
6766N/AMILD_ERR_SYNC_INVALID_DN_1=The configured DN is already used by another \
6766N/AMILD_ERR_INVALID_CHANGELOG_SERVER_4=Invalid replication server configuration
6766N/AMILD_ERR_UNKNOWN_HOSTNAME_5=Replication Server failed to start because the \
6766N/AMILD_ERR_COULD_NOT_BIND_CHANGELOG_6=Replication Server failed to start : \
6766N/A could not bind to the listen port : %d. Error : %s
6766N/AMILD_ERR_UNKNOWN_TYPE_7=Unknown operation type : %s
6766N/AMILD_ERR_OPERATION_NOT_FOUND_IN_PENDING_9=Internal Error : Operation %s \
6766N/A change number %s was not found in pending list
6766N/AMILD_ERR_COULD_NOT_INITIALIZE_DB_10=The replication server failed to start because the \
6766N/A database %s could not be opened
6766N/AMILD_ERR_COULD_NOT_READ_DB_11=The replication server failed to start because the database \
6766N/AMILD_ERR_EXCEPTION_REPLAYING_OPERATION_12=An Exception was caught while \
6766N/A replaying operation %s : %s
6766N/AMILD_ERR_NEED_CHANGELOG_PORT_13=The replication server port must be defined
6766N/ADEBUG_ERROR_UPDATING_RUV_14=Error %s when updating server state %s : %s \
6766N/AMILD_ERR_ERROR_SEARCHING_RUV_15=Error %s when searching for server state %s : \
6766N/ANOTICE_FOUND_CHANGELOGS_WITH_MY_CHANGES_18=Found %d replication server(s) with \
6766N/Aup to date changes for suffix %s, in server id %s
6766N/ANOTICE_NEED_MORE_THAN_ONE_CHANGELOG_SERVER_19=More than one replication \
6766N/A server should be configured
6766N/ASEVERE_ERR_EXCEPTION_SENDING_TOPO_INFO_20=Caught IOException while sending \
6766N/A topology info (for update) on domain %s for %s server %s : %s
6766N/AMILD_ERR_CANNOT_RECOVER_CHANGES_21=Error when searching old changes from the \
6766N/ANOTICE_COULD_NOT_FIND_CHANGELOG_WITH_MY_CHANGES_22=Could not find a \
6766N/A replication server that has seen all the local changes on suffix %s. Found %d \
6766N/Areplications server(s) not up to date. Going to replay changes
6766N/ANOTICE_EXCEPTION_CLOSING_DATABASE_24=Error closing Replication Server database \
6766N/ASEVERE_ERR_EXCEPTION_DECODING_OPERATION_25=Error trying to replay %s, \
6766N/A operation could not be decoded :
6766N/AFATAL_ERR_CHANGELOG_SHUTDOWN_DATABASE_ERROR_26=Error Trying to use the \
6766N/A underlying database. The Replication Server is going to shut down
6766N/ASEVERE_ERR_IGNORE_BAD_DN_IN_DATABASE_IDENTIFIER_27=A badly formatted DN was \
6766N/A found in the list of database known by this Replication Server :%s. This \
6766N/ASEVERE_ERR_ERROR_CLOSING_CHANGELOG_ENV_28=Error closing the Replication Server \
6766N/ASEVERE_ERR_EXCEPTION_CHANGELOG_TRIM_FLUSH_29=Error during the Replication \
6766N/A Server database trimming or flush process. The Changelog service is going to \
6766N/ASEVERE_ERR_REPLICATION_SERVER_CONNECTION_ERROR_30=Error in Replication Server \
6766N/ASEVERE_ERR_UNKNOWN_MESSAGE_31=%s has sent an unknown message. Closing the \
6766N/ASEVERE_ERR_WRITER_UNEXPECTED_EXCEPTION_32=An unexpected error happened \
6766N/A handling connection with %s. This connection is going to be closed
6766N/ASEVERE_ERR_RS_ERROR_SENDING_ACK_33=In replication server %s: an unexpected error \
6766N/A occurred while sending an ack to server id %s for change number %s in domain %s \
6766N/A . This connection is going to be closed and reopened
6766N/ASEVERE_ERR_EXCEPTION_RECEIVING_REPLICATION_MESSAGE_34=An Exception was caught \
6766N/A while receiving replication message : %s
6766N/AMILD_ERR_LOOP_REPLAYING_OPERATION_35=A loop was detected while replaying \
6766N/AMILD_ERR_FILE_CHECK_CREATE_FAILED_36=An Exception was caught while testing \
6766N/A existence or trying to create the directory for the Replication Server \
6766N/AINFO_CHANGELOG_SERVER_ATTR_37=List of replication servers to \
6766N/A which this Replication Server should connect. Each value of this attribute \
6766N/A should contain a values build with the hostname and the port number of the \
6766N/A remote server separated with a ":"
6766N/AINFO_SERVER_ID_ATTR_38=Server ID. Each Replication Server in \
6766N/A the topology must be assigned a unique server ID in the topology
6766N/AINFO_CHANGELOG_PORT_ATTR_39=Port number that the replication \
6766N/A server will use to listen for connections from LDAP servers
6766N/AINFO_WINDOW_SIZE_ATTR_40=Receive window size of the replication server
6766N/AINFO_QUEUE_SIZE_ATTR_41=Receive queue size of the replication \
6766N/A server. The replication servers will queue up to this number of messages in \
6766N/A its memory queue and save the older messages to persistent storage. Using a \
6766N/A larger size may improve performances when The replication delay is larger \
6766N/A than this size but at the cost of using more memory
6766N/AINFO_CHANGELOG_DIR_PATH_ATTR_42=Replication Server directory. \
6766N/A The replication server will create all persistent storage below this path
6766N/AINFO_PURGE_DELAY_ATTR_43=Replication Server Purge Delay, The replication \
6766N/A Servers will keep all changes up to this amount of time before deleting them. \
6766N/A This value defines the maximum age of a backup that can be restored because \
6766N/A replication servers would not be able to refresh LDAP servers with older \
6766N/A versions of the data. A zero value can be used to specify an infinite delay \
6766N/ASEVERE_ERR_SIMULTANEOUS_IMPORT_EXPORT_REJECTED_44=The current request is \
6766N/A rejected due to an import or an export already in progress for the same data
6766N/ASEVERE_ERR_INVALID_IMPORT_SOURCE_45=On domain %s, initialization of server \
6766N/A with serverId:%s has been requested from a server with an invalid \
6766N/ASEVERE_ERR_INVALID_EXPORT_TARGET_46=Invalid target for the export
6766N/ASEVERE_ERR_NO_REACHABLE_PEER_IN_THE_DOMAIN_47=Domain %s: the server with \
6766N/ASEVERE_ERR_NO_MATCHING_DOMAIN_48=No domain matches the provided base DN '%s'
6766N/ASEVERE_ERR_MULTIPLE_MATCHING_DOMAIN_49=Multiple domains match the base DN \
6766N/ASEVERE_ERR_INVALID_PROVIDER_50=The provider class does not allow the \
6766N/ASEVERE_ERR_COULD_NOT_SOLVE_HOSTNAME_51=The hostname %s could not be resolved \
6766N/ANOTICE_READER_NULL_MSG_52=Received a Null Msg from %s
6766N/ANOTICE_READER_EXCEPTION_53=Exception when reading messages from %s
6766N/ASEVERE_ERR_DUPLICATE_SERVER_ID_54=In Replication server %s: servers %s and %s \
6766N/ASEVERE_ERR_DUPLICATE_REPLICATION_SERVER_ID_55=In Replication server %s: \
6766N/Areplication servers %s and %s have the same ServerId : %d
6766N/ASEVERE_ERR_BAD_HISTORICAL_56=Entry %s was containing some unknown historical \
6766N/A information, This may cause some inconsistency for this entry
6766N/AMILD_ERR_CANNOT_ADD_CONFLICT_ATTRIBUTE_57=A conflict was detected but the \
6766N/A conflict information could not be added. Operation :
6766N/AMILD_ERR_CANNOT_RENAME_CONFLICT_ENTRY_58=An error happened trying to \
6766N/A rename a conflicting entry :
6766N/AMILD_ERR_EXCEPTION_RENAME_CONFLICT_ENTRY_59=An Exception happened when \
6766N/A trying to rename a conflicting entry :
6766N/ASEVERE_ERR_CHANGELOG_UNSUPPORTED_UTF8_ENCODING_60=The JVM does not support \
6766N/A UTF-8. This is required to be able to encode the changes in the database. \
6766N/A This replication server will now shutdown
6766N/ASEVERE_ERR_REPLICATION_COULD_NOT_CONNECT_61=The Replication is configured for \
6766N/A suffix %s but was not able to connect to any Replication Server
6766N/ASEVERE_ERR_CHANGELOG_ERROR_SENDING_ERROR_65=An unexpected error occurred \
6766N/A while sending an Error Message to %s. This connection is going to be closed \
6766N/ASEVERE_ERR_CHANGELOG_ERROR_SENDING_MSG_66=An unexpected error occurred while \
6766N/A sending a Message to %s. This connection is going to be closed and reopened
6766N/AMILD_ERR_ERROR_REPLAYING_OPERATION_67=Could not replay operation %s with \
6766N/A ChangeNumber %s error %s %s
6766N/AMILD_ERR_UNKNOWN_ATTRIBUTE_IN_HISTORICAL_68=The entry %s has historical \
6766N/A information for attribute %s which is not defined in the schema. This \
6766N/A information will be ignored
6766N/ANOTICE_UNRESOLVED_CONFLICT_69=An unresolved conflict was detected for DN %s
6766N/ASEVERE_ERR_COULD_NOT_CLOSE_THE_SOCKET_70=The Replication Server socket could not \
6766N/ASEVERE_ERR_COULD_NOT_STOP_LISTEN_THREAD_71=The thread listening on the \
6766N/A replication server port could not be stopped : %s
6766N/ADEBUG_REPLICATION_PORT_IOEXCEPTION_72=An IOException was caught while \
6766N/A listening on the replication port
6766N/ASEVERE_ERR_SEARCHING_GENERATION_ID_73=An unexpected error %s occurred when \
6766N/Asearching for generation id for domain : %s
6766N/ASEVERE_ERR_SEARCHING_DOMAIN_BACKEND_74=An unexpected error occurred when \
6766N/Alooking for the replicated backend : %s. It may be not configured or disabled
6766N/ASEVERE_ERR_LOADING_GENERATION_ID_75=An unexpected error occurred when \
6766N/Asearching in %s for the generation ID : %s
6766N/ASEVERE_ERR_UPDATING_GENERATION_ID_76=An unexpected error %s occurred \
6766N/Awhen updating generation ID for the domain : %s
6766N/AMILD_ERR_ERROR_MSG_RECEIVED_79=The following error has been received : %s
6766N/ASEVERE_ERR_INIT_IMPORT_NOT_SUPPORTED_82= Initialization cannot be done because \
6766N/Aimport is not supported by the backend %s
6766N/ASEVERE_ERR_INIT_EXPORT_NOT_SUPPORTED_83= Initialization cannot be done because \
6766N/Aexport is not supported by the backend %s
6766N/ASEVERE_ERR_INIT_CANNOT_LOCK_BACKEND_84= Initialization cannot be done because \
6766N/Athe following error occurred while locking the backend %s : %s
6766N/ANOTICE_EXCEPTION_RESTARTING_SESSION_85=Caught Exception during reinitialization of \
6766N/A communication on domain %s : %s
6766N/ASEVERE_ERR_EXCEPTION_LISTENING_86=Replication server caught exception while \
6766N/A listening for client connections %s
6766N/ASEVERE_ERR_ERROR_CLEARING_DB_87=While clearing the database %s , the following \
6766N/ANOTICE_ERR_ROUTING_TO_SERVER_88=Protocol error : a replication server is not expected \
6766N/A to be the destination of a message of type %s
6766N/ASEVERE_ERR_CHECK_CREATE_REPL_BACKEND_FAILED_89=An unexpected error occurred when \
6766N/A testing existence or creating the replication backend : %s
6766N/ASEVERE_ERR_DELETE_REPL_BACKEND_FAILED_90=An unexpected error occurred when \
6766N/A deleting the replication backend : %s
6766N/A SEVERE_ERR_BACKEND_EXPORT_ENTRY_91=An error occurred when \
6766N/A exporting the entry %s : %s
6766N/ASEVERE_ERR_BACKEND_CANNOT_CREATE_LDIF_WRITER_92 =An error occurred when \
6766N/A creating the LDIF writer to export backend : %s
6766N/ASEVERE_ERR_BACKEND_SEARCH_ENTRY_93 =An error occurred when \
6766N/ASEVERE_ERR_REPLICATIONBACKEND_ENTRY_DOESNT_EXIST_94=Entry %s does not exist in \
6766N/A the replication server backend
6766N/ASEVERE_ERR_UNKNOWN_DN_95=The base DN %s is not stored by any of the \
6766N/ASEVERE_ERR_REPLICATONBACKEND_IMPORT_LDIF_NOT_SUPPORTED_98=The replication \
6766N/A server backend does not support the import ldif function
6766N/ASEVERE_ERR_REPLICATONBACKEND_EXPORT_LDIF_FAILED_99=The replication \
6766N/A server backend cannot export its entries in LDIF format because the \
6766N/A export-ldif command must be run as a task
6766N/ASEVERE_ERR_PROCESSING_REMOTE_MONITOR_DATA_107=Monitor data of remote servers \
6766N/A are missing due to a processing error : %s
6766N/ASEVERE_ERR_SENDING_REMOTE_MONITOR_DATA_REQUEST_108=Unable to send monitor data \
6766N/A request for domain "%s" to replication server RS(%d) due to the following \
6766N/ASEVERE_ERR_EXCEPTION_REPLAYING_REPLICATION_MESSAGE_109=An Exception was caught \
while replaying replication message : %s
SEVERE_ERR_REPLICATION_SERVER_CONFIG_NOT_FOUND_110=The replication server \
configuration could not be found
DEBUG_GOING_TO_SEARCH_FOR_CHANGES_111=The replication server is late \
regarding our changes: going to send missing ones
DEBUG_SENDING_CHANGE_112=Sending change number: %s
DEBUG_CHANGES_SENT_113=All missing changes sent to replication server
SEVERE_ERR_PUBLISHING_FAKE_OPS_114=Caught exception publishing fake operations \
SEVERE_ERR_COMPUTING_FAKE_OPS_115=Caught exception computing fake operations \
for domain %s for replication server %s : %s
INFO_IGNORING_REMOTE_MONITOR_DATA_116=Late monitor data received for domain "%s" \
from replication server RS(%d), and will be ignored
NOTICE_SERVER_STATE_RECOVERY_117=ServerState recovery for domain %s, \
updated with changeNumber %s
SEVERE_ERR_RESET_GENERATION_CONN_ERR_ID_118=For replicated domain %s, in \
server with serverId=%s, the generation ID could not be set to value %s \
in the rest of the topology because this server is NOT connected to \
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_RS_DN_DOES_NOT_MATCH_121=DN sent by remote replication server: %s does \
not match local replication server one: %s
SEVERE_ERR_DS_DN_DOES_NOT_MATCH_122=DN sent by replication server: %s does \
not match local directory server one: %s
SEVERE_ERR_EXCEPTION_FORWARDING_RESET_GEN_ID_123=Caught IOException while \
forwarding ResetGenerationIdMsg to peer replication servers for domain %s : %s
SEVERE_ERR_DS_INVALID_INIT_STATUS_124=Computed invalid initial status: %s in \
DS replication domain %s with server id %s
SEVERE_ERR_RS_INVALID_INIT_STATUS_125=Replication server received invalid \
initial status: %s for replication domain %s from server id %s
SEVERE_ERR_DS_INVALID_REQUESTED_STATUS_126=Received invalid requested status %s \
in DS replication domain %s with server id %s
SEVERE_ERR_RS_CANNOT_CHANGE_STATUS_127=Could not compute new status in RS \
replication domain %s for server id %s. Was in %s status and received %s event
SEVERE_ERR_DS_CANNOT_CHANGE_STATUS_128=Could not compute new status in DS \
replication domain %s with server id %s. Was in %s status and received %s event
SEVERE_ERR_EXCEPTION_CHANGING_STATUS_AFTER_RESET_GEN_ID_129=Caught IOException \
while changing status for domain %s and serverId: %s after reset for \
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)
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 \
replication server with wrong group id. We have group id %s and replication \
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
SEVERE_ERR_EXCEPTION_CHANGING_STATUS_FROM_STATUS_ANALYZER_139=Caught \
IOException while changing status for domain %s and serverId: %s from status \
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 \
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 \
waiting for the acknowledgement of the assured update message: %s
SEVERE_ERR_DS_UNKNOWN_ASSURED_MODE_149=In directory server %s, received unknown \
assured update mode: %s, for domain %s. Message: %s
SEVERE_ERR_RS_UNKNOWN_ASSURED_MODE_150=In replication server %s, received unknown \
assured update mode: %s, for domain %s. Message: %s
SEVERE_ERR_UNKNOWN_ASSURED_SAFE_DATA_LEVEL_151=In replication server %s, \
received a safe data assured update message with incoherent level: %s, this is \
for domain %s. Message: %s
SEVERE_ERR_RESET_GENERATION_ID_FAILED_152=The generation ID could not be \
NOTICE_ERR_CANNOT_CHANGE_CONFIG_DURING_TOTAL_UPDATE_153=Cannot change the \
configuration while a total update is in progress
SEVERE_ERR_COULD_NOT_START_REPLICATION_154=The Replication was not started \
MILD_ERR_ERROR_RETRIEVING_MONITOR_DATA_155=Error retrieving monitoring data: %s
SEVERE_ERR_EXCEPTION_LOCKING_RS_DOMAIN_156=Caught exception when locking \
the replication server domain: %s
SEVERE_ERR_REPLICATION_PROTOCOL_MESSAGE_TYPE_157=Replication \
protocol error. Bad message type. %s received, %s required
SEVERE_ERR_RESYNC_REQUIRED_MISSING_DOMAIN_IN_PROVIDED_COOKIE_158=Full resync \
required because the provided cookie is missing the replicated domain(s) %s. \
The following cookie value can be used to retrieve the missing changes, \
including the COMPLETE record of changes for the missing domain(s) : %s
SEVERE_ERR_BYTE_COUNT_159=The Server Handler byte count is not correct \
NOTICE_ERR_FRACTIONAL_CONFIG_UNKNOWN_OBJECT_CLASS_160=Wrong fractional \
replication configuration: could not find object class definition for %s in \
NOTICE_ERR_FRACTIONAL_CONFIG_UNKNOWN_ATTRIBUTE_TYPE_161=Wrong fractional \
replication configuration : could not find attribute type definition for %s \
NOTICE_ERR_FRACTIONAL_CONFIG_NOT_OPTIONAL_ATTRIBUTE_162=Wrong fractional \
replication configuration : attribute %s is not optional in class %s
NOTICE_ERR_FRACTIONAL_CONFIG_WRONG_FORMAT_163=Wrong fractional replication \
configuration : wrong format : %s (need at least [<className>|*],attributeName)
NOTICE_ERR_FRACTIONAL_CONFIG_BOTH_MODES_164=Wrong fractional replication \
configuration : cannot use both exclusive and inclusive modes
NOTICE_ERR_FRACTIONAL_CONFIG_PROHIBITED_ATTRIBUTE_165=Wrong fractional \
replication configuration : prohibited attribute %s usage
NOTICE_ERR_FRACTIONAL_166=Fractional replication : exception for domain : %s : \
NOTICE_FRACTIONAL_BAD_DATA_SET_NEED_RESYNC_167=Warning : domain %s fractional \
replication configuration is inconsistent with backend data set : need \
resynchronization or fractional configuration to be changed
MILD_ERR_PLUGIN_FRACTIONAL_LDIF_IMPORT_INVALID_PLUGIN_TYPE_168=The fractional \
replication ldif import plugin is configured with invalid plugin type %s. \
Only the ldifImport plugin type is allowed
NOTICE_ERR_FULL_UPDATE_IMPORT_FRACTIONAL_BAD_REMOTE_169=The online full \
update for importing suffix %s data from remote directory server %s has been \
stopped due to fractional configuration inconsistency between destination \
and source server : imported data set has not the same fractional configuration
NOTICE_ERR_FULL_UPDATE_IMPORT_FRACTIONAL_REMOTE_IS_FRACTIONAL_170=The online \
full update for importing suffix %s data from remote directory server %s has \
been stopped due to fractional configuration inconsistency between \
destination and source server : imported data set has some fractional \
configuration but not destination server
NOTICE_ERR_FRACTIONAL_FORBIDDEN_OPERATION_171=The following operation has \
been forbidden in suffix %s due to inconsistency with the fractional \
replication configuration : %s
NOTICE_ERR_FRACTIONAL_FORBIDDEN_FULL_UPDATE_FRACTIONAL_172=The export of \
domain %s from server %s to all other servers of the topology is forbidden as \
the source server has some fractional configuration : only fractional servers \
in a replicated topology does not make sense
MILD_ERR_DRAFT_CHANGENUMBER_DATABASE_173=An error occurred when accessing the \
database of the draft change number : %s
SEVERE_ERR_INITIALIZATION_FAILED_NOCONN_174=The initialization failed because \
the domain %s is not connected to a replication server
SEVERE_ERR_FRACTIONAL_COULD_NOT_RETRIEVE_CONFIG_175=Could not retrieve the \
configuration for a replication domain matching the entry %s
NOTICE_ERR_LDIF_IMPORT_FRACTIONAL_BAD_DATA_SET_176=The LDIF import for \
importing suffix %s data has been stopped due to fractional configuration \
inconsistency : imported data set has not the same fractional configuration \
NOTICE_ERR_LDIF_IMPORT_FRACTIONAL_DATA_SET_IS_FRACTIONAL_177=The LDIF import \
for importing suffix %s data has been stopped due to fractional configuration \
inconsistency : imported data set has some fractional configuration but not \
SEVERE_ERR_DS_DISCONNECTED_DURING_HANDSHAKE_178=Directory server %s was \
attempting to connect to replication server %s but has disconnected in \
SEVERE_ERR_RS_DISCONNECTED_DURING_HANDSHAKE_179=Replication server %s was \
attempting to connect to replication server %s but has disconnected in \
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 \
NOTICE_ERR_ENTRY_UID_DSEE_MAPPING_184=Error for entry %s when mapping entry UID\
attribute to DSEE NsUniqueID attribute. Value to be mapped: %s \
SEVERE_ERR_RESYNC_REQUIRED_UNKNOWN_DOMAIN_IN_PROVIDED_COOKIE_185=Full resync \
required. Reason: The provided cookie contains unknown replicated domain %s. \
Current starting cookie <%s>
SEVERE_ERR_RESYNC_REQUIRED_TOO_OLD_DOMAIN_IN_PROVIDED_COOKIE_186=Full resync \
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
MILD_ERR_INIT_EXPORTER_DISCONNECTION_189=Domain %s (server id: %s) : \
remote exporter server disconnection (server id: %s ) detected during \
SEVERE_ERR_INIT_IMPORT_FAILURE_190=\
During initialization from a remote server, the following error occurred : %s
SEVERE_ERR_INIT_RS_DISCONNECTION_DURING_IMPORT_191=\
Connection failure with Replication Server %s during import
SEVERE_ERR_INIT_BAD_MSG_ID_SEQ_DURING_IMPORT_192=\
Bad msg id sequence during import. Expected:%s Actual:%s
SEVERE_ERR_INIT_NO_SUCCESS_START_FROM_SERVERS_193=\
The following servers did not acknowledge initialization in the expected \
time. They are potentially down or too slow. Servers list: %s
SEVERE_ERR_INIT_NO_SUCCESS_END_FROM_SERVERS_194=\
The following servers did not end initialization being connected with the \
right generation (%s). They are potentially stopped or too slow. \
SEVERE_ERR_INIT_RS_DISCONNECTION_DURING_EXPORT_195=\
When initializing remote server(s), connection to Replication Server with \
SEVERE_ERR_INIT_HEARTBEAT_LOST_DURING_EXPORT_196=\
When initializing remote server(s), the initialized server with serverId=%s \
is potentially stopped or too slow
SEVERE_ERR_SENDING_NEW_ATTEMPT_INIT_REQUEST_197=\
When sending a new initialization request for an initialization from a remote \
server, the following error occurred %s. The initial error was : %s
NOTICE_RESENDING_INIT_FROM_REMOTE_REQUEST_198=\
Resending a new initialization request for an initialization from a remote \
server due to the root error : %s
NOTICE_RESENDING_INIT_TARGET_199=\
Resending a new initialization start for an initialization of a remote server \
due to the root error : %s
NOTICE_ERR_WHILE_TRYING_TO_DECODE_RUV_IN_STATE_200=Error while trying to \
translate RUV into state for suffix %s
SEVERE_ERR_RSQUEUE_DIFFERENT_MSGS_WITH_SAME_CN_201=Processing two different \
changes with same changeNumber=%s. Previous msg=<%s>, New msg=<%s>
SEVERE_ERR_COULD_NOT_SOLVE_CONFLICT_202=Error while trying to solve conflict \
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 \
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 \
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. The previous replication server evaluation was: "%s", and the \
new replication server evaluation was: "%s"
NOTICE_FULL_UPDATE_ENGAGED_FROM_REMOTE_START_141=Starting total update: \
importing domain "%s" from remote directory server DS(%d) to this directory \
NOTICE_FULL_UPDATE_ENGAGED_FROM_REMOTE_END_142=Finished total update: \
imported domain "%s" from remote directory server DS(%d) to this directory \
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 \
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 \
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 \
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 \
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)
NOTICE_LOAD_BALANCE_REPLICATION_SERVER_213=Directory Server DS(%d) is disconnecting \
from replication server RS(%d) at %s for domain "%s" in order to find another \
replication server in the topology and distribute load more equally
SEVERE_WARN_INVALID_SYNC_HIST_VALUE_214=The attribute value '%s' is not a valid \
synchronization history value
SEVERE_ERR_REPLICATIONDB_CANNOT_PROCESS_CHANGE_RECORD_215=Replication server RS(%d) \
failed to parse change record with changenumber %s from the database. Error: %s
SEVERE_ERR_SESSION_STARTUP_INTERRUPTED_216=%s was interrupted in the startup phase
NOTICE_RS_URL_HAS_NO_PORT_NUMBER_217=Could not find a port number in RS(%d) URL "%s"
NOTICE_RS_NOT_LOCALLY_CONFIGURED_219=RS(%d) was not configured locally on DS(%d), \
but at least one other RS was
NOTICE_RS_HAS_NO_GENERATION_ID_220=RS(%d) has no generation Id, but at least one \
other RS has the same generation Id %d as DS(%d)
NOTICE_RS_HAS_DIFFERENT_GENERATION_ID_THAN_DS_221=RS(%d) generation Id %d does not \
match DS(%d) generation Id %d, but at least another RS does
NOTICE_RS_HAS_DIFFERENT_GROUP_ID_THAN_DS_222=RS(%d) groupId %d does not match \
DS(%d) groupId %d, but at least another RS does
NOTICE_RS_LATER_THAN_LOCAL_DS_223=RS(%d) newest change %s is behind DS(%d) \
newest change %s, but at least another RS is at the same point or ahead of the DS
NOTICE_RS_LATER_THAN_ANOTHER_RS_MORE_UP_TO_DATE_THAN_LOCAL_DS_224=RS(%d) newest \
change %s is behind another RS which is ahead of DS(%d) newest change %s
NOTICE_RS_ON_DIFFERENT_VM_THAN_DS_225=RS(%d) is on the same host, but a different \
virtual machine than DS(%d), but at least another RS is
NOTICE_RS_ON_DIFFERENT_HOST_THAN_DS_226=RS(%d) is on a different host than DS(%d), \
but at least another RS is on the same host
NOTICE_DISCONNECT_DS_FROM_OVERLOADED_RS_227=DS(%d) disconnected from overloaded RS(%d)
NOTICE_DO_NOT_DISCONNECT_DS_FROM_OVERLOADED_RS_228=DS(%d) not disconnected from \
overloaded RS(%d), other DSs will disconnect
NOTICE_NO_NEED_TO_REBALANCE_DSS_BETWEEN_RSS_229=DS(%d) not disconnected from \
current RS(%d), since there is no need to rebalance all directory servers to \
other replication servers in the topology
NOTICE_DO_NOT_DISCONNECT_DS_FROM_ACCEPTABLE_LOAD_RS_230=DS(%d) not disconnected \
from current RS(%d), because RS is underloaded or its load goal is reached
NOTICE_BIGGEST_WEIGHT_RS_231=DS(%d) will connect to RS(%d) because it has the \
biggest weight among all the replication servers
NOTICE_AVOID_YOYO_EFFECT_232=DS(%d) stayed connected to RS(%d) to avoid the yoyo effect
NOTICE_BEST_RS_233=RS(%d) has been evaluated to be the best replication server \
for DS(%d) to connect to because it was the only one standing after all tests
NOTICE_UNKNOWN_RS_234=RS(%d) could not be contacted by DS(%d)
NOTICE_ECL_LOOKTHROUGH_LIMIT_EXCEEDED_238=This search operation has checked the \
maximum of %d entries for matches