# CDDL HEADER START
|
#
|
# The contents of this file are subject to the terms of the
|
# Common Development and Distribution License, Version 1.0 only
|
# (the "License"). You may not use this file except in compliance
|
# with the License.
|
#
|
# You can obtain a copy of the license at legal-notices/CDDLv1_0.txt
|
# or http://forgerock.org/license/CDDLv1.0.html.
|
# See the License for the specific language governing permissions
|
# and limitations under the License.
|
#
|
# When distributing Covered Code, include this CDDL HEADER in each
|
# file and include the License file at legal-notices/CDDLv1_0.txt.
|
# If applicable, add the following below this CDDL HEADER, with the
|
# fields enclosed by brackets "[]" replaced with your own identifying
|
# information:
|
# Portions Copyright [yyyy] [name of copyright owner]
|
#
|
# CDDL HEADER END
|
#
|
# Copyright 2006-2010 Sun Microsystems, Inc.
|
# Portions copyright 2011-2013 ForgeRock AS
|
#
|
#
|
# This file contains the primary Directory Server configuration. It must not
|
# be directly edited while the server is online. The server configuration
|
# should only be managed using the administration utilities provided with the
|
# Directory Server.
|
|
|
#
|
# Global directives
|
#
|
global.category=SYNC
|
|
#
|
# Format string definitions
|
#
|
# Keys must be formatted as follows:
|
#
|
# [SEVERITY]_[DESCRIPTION]_[ORDINAL]
|
#
|
# where:
|
#
|
# SEVERITY is one of:
|
# [INFO, MILD_WARN, SEVERE_WARN, MILD_ERR, SEVERE_ERR, FATAL_ERR, DEBUG, NOTICE]
|
#
|
# DESCRIPTION is an upper case string providing a hint as to the context of
|
# the message in upper case with the underscore ('_') character serving as
|
# word separator
|
#
|
# ORDINAL is an integer unique among other ordinals in this file
|
#
|
MILD_ERR_SYNC_INVALID_DN_1=The configured DN is already used by another \
|
domain
|
MILD_ERR_UNKNOWN_HOSTNAME_5=Replication Server failed to start because the \
|
hostname is unknown
|
MILD_ERR_COULD_NOT_BIND_CHANGELOG_6=Replication Server failed to start : \
|
could not bind to the listen port : %d. Error : %s
|
MILD_ERR_UNKNOWN_TYPE_7=Unknown operation type : %s
|
MILD_ERR_OPERATION_NOT_FOUND_IN_PENDING_9=Internal Error : Operation %s \
|
change number %s was not found in pending list
|
MILD_ERR_COULD_NOT_READ_DB_11=The replication server failed to start because the database \
|
%s could not be read : %s
|
MILD_ERR_EXCEPTION_REPLAYING_OPERATION_12=An Exception was caught while \
|
replaying operation %s : %s
|
DEBUG_ERROR_UPDATING_RUV_14=Error %s when updating server state %s : %s \
|
base dn : %s
|
MILD_ERR_ERROR_SEARCHING_RUV_15=Error %s when searching for server state %s : \
|
%s base dn : %s
|
SEVERE_ERR_EXCEPTION_SENDING_TOPO_INFO_20=Caught IOException while sending \
|
topology info (for update) on domain %s for %s server %s : %s
|
MILD_ERR_CANNOT_RECOVER_CHANGES_21=Error when searching old changes from the \
|
database for base DN %s
|
NOTICE_EXCEPTION_CLOSING_DATABASE_24=Error closing Replication Server database \
|
%s : %s
|
SEVERE_ERR_EXCEPTION_DECODING_OPERATION_25=Error trying to replay %s, \
|
operation could not be decoded :
|
FATAL_ERR_CHANGELOG_SHUTDOWN_DATABASE_ERROR_26=Error trying to use the \
|
underlying database. The Replication Server is going to shut down: %s
|
SEVERE_ERR_ERROR_CLOSING_CHANGELOG_ENV_28=Error closing the Replication Server \
|
database : %s
|
SEVERE_ERR_EXCEPTION_CHANGELOG_TRIM_FLUSH_29=Error during the Replication \
|
Server database trimming or flush process. The Changelog service is going to \
|
shutdown: %s
|
SEVERE_ERR_WRITER_UNEXPECTED_EXCEPTION_32=An unexpected error happened \
|
handling connection with %s. This connection is going to be closed
|
SEVERE_ERR_RS_ERROR_SENDING_ACK_33=In replication server %s: an unexpected error \
|
occurred while sending an ack to server id %s for change number %s in domain %s \
|
. This connection is going to be closed and reopened
|
MILD_ERR_LOOP_REPLAYING_OPERATION_35=A loop was detected while replaying \
|
operation: %s error %s
|
MILD_ERR_FILE_CHECK_CREATE_FAILED_36=An Exception was caught while testing \
|
existence or trying to create the directory for the Replication Server \
|
database : %s
|
SEVERE_ERR_SIMULTANEOUS_IMPORT_EXPORT_REJECTED_44=The current request is \
|
rejected due to an import or an export already in progress for the same data
|
SEVERE_ERR_INVALID_IMPORT_SOURCE_45=On domain %s, initialization of server \
|
with serverId:%s has been requested from a server with an invalid \
|
serverId:%s. %s
|
SEVERE_ERR_INVALID_EXPORT_TARGET_46=Invalid target for the export
|
SEVERE_ERR_NO_REACHABLE_PEER_IN_THE_DOMAIN_47=Domain %s: the server with \
|
serverId=%s is unreachable
|
SEVERE_ERR_NO_MATCHING_DOMAIN_48=No domain matches the provided base DN '%s'
|
SEVERE_ERR_MULTIPLE_MATCHING_DOMAIN_49=Multiple domains match the base DN \
|
provided
|
SEVERE_ERR_INVALID_PROVIDER_50=The provider class does not allow the \
|
operation requested
|
SEVERE_ERR_COULD_NOT_SOLVE_HOSTNAME_51=The hostname %s could not be resolved \
|
as an IP address
|
NOTICE_READER_NULL_MSG_52=Received a Null Msg from %s
|
NOTICE_READER_EXCEPTION_53=Exception when reading messages from %s
|
SEVERE_ERR_DUPLICATE_SERVER_ID_54=In Replication server %s: servers %s and %s \
|
have the same ServerId : %d
|
SEVERE_ERR_DUPLICATE_REPLICATION_SERVER_ID_55=In Replication server %s: \
|
replication servers %s and %s have the same ServerId : %d
|
SEVERE_ERR_BAD_HISTORICAL_56=Entry %s was containing some unknown historical \
|
information, This may cause some inconsistency for this entry
|
MILD_ERR_CANNOT_ADD_CONFLICT_ATTRIBUTE_57=A conflict was detected but the \
|
conflict information could not be added. Operation :
|
MILD_ERR_CANNOT_RENAME_CONFLICT_ENTRY_58=An error happened trying to \
|
rename a conflicting entry :
|
MILD_ERR_EXCEPTION_RENAME_CONFLICT_ENTRY_59=An Exception happened when \
|
trying to rename a conflicting entry :
|
SEVERE_ERR_REPLICATION_COULD_NOT_CONNECT_61=The Replication is configured for \
|
suffix %s but was not able to connect to any 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
|
SEVERE_ERR_CHANGELOG_ERROR_SENDING_MSG_66=An unexpected error occurred while \
|
sending a Message to %s. This connection is going to be closed and reopened
|
MILD_ERR_ERROR_REPLAYING_OPERATION_67=Could not replay operation %s with \
|
ChangeNumber %s error %s %s
|
MILD_ERR_UNKNOWN_ATTRIBUTE_IN_HISTORICAL_68=The entry %s has historical \
|
information for attribute %s which is not defined in the schema. This \
|
information will be ignored
|
NOTICE_UNRESOLVED_CONFLICT_69=An unresolved conflict was detected for DN %s
|
SEVERE_ERR_COULD_NOT_CLOSE_THE_SOCKET_70=The Replication Server socket could not \
|
be closed : %s
|
SEVERE_ERR_COULD_NOT_STOP_LISTEN_THREAD_71=The thread listening on the \
|
replication server port could not be stopped : %s
|
SEVERE_ERR_SEARCHING_GENERATION_ID_73=An unexpected error %s occurred when \
|
searching for generation id for domain : %s
|
SEVERE_ERR_SEARCHING_DOMAIN_BACKEND_74=An unexpected error occurred when \
|
looking for the replicated backend : %s. It may be not configured or disabled
|
SEVERE_ERR_LOADING_GENERATION_ID_75=An unexpected error occurred when \
|
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
|
MILD_ERR_ERROR_MSG_RECEIVED_79=The following error has been received : %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 \
|
export is not supported by the backend %s
|
SEVERE_ERR_INIT_CANNOT_LOCK_BACKEND_84= Initialization cannot be done because \
|
the following error occurred while locking the backend %s : %s
|
NOTICE_EXCEPTION_RESTARTING_SESSION_85=Caught Exception during reinitialization of \
|
communication on domain %s : %s
|
SEVERE_ERR_EXCEPTION_LISTENING_86=Replication server caught exception while \
|
listening for client connections %s
|
SEVERE_ERR_ERROR_CLEARING_DB_87=While clearing the database %s , the following \
|
error happened: %s
|
NOTICE_ERR_ROUTING_TO_SERVER_88=Protocol error : a replication server is not expected \
|
to be the destination of a message of type %s
|
SEVERE_ERR_CHECK_CREATE_REPL_BACKEND_FAILED_89=An unexpected error occurred when \
|
testing existence or creating the replication backend : %s
|
SEVERE_ERR_DELETE_REPL_BACKEND_FAILED_90=An unexpected error occurred when \
|
deleting the replication backend : %s
|
SEVERE_ERR_BACKEND_EXPORT_ENTRY_91=An error occurred when \
|
exporting the entry %s : %s
|
SEVERE_ERR_BACKEND_CANNOT_CREATE_LDIF_WRITER_92 =An error occurred when \
|
creating the LDIF writer to export backend : %s
|
SEVERE_ERR_BACKEND_SEARCH_ENTRY_93 =An error occurred when \
|
searching for %s : %s
|
SEVERE_ERR_REPLICATIONBACKEND_ENTRY_DOESNT_EXIST_94=Entry %s does not exist in \
|
the replication server backend
|
SEVERE_ERR_UNKNOWN_DN_95=The base DN %s is not stored by any of the \
|
Directory Server backend
|
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
|
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 \
|
request for domain "%s" to replication server RS(%d) due to the following \
|
error: %s
|
SEVERE_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_CHANGES_SENT_113=All missing changes sent to replication server
|
SEVERE_ERR_PUBLISHING_FAKE_OPS_114=Caught exception publishing fake operations \
|
for domain %s : %s
|
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 \
|
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)
|
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 \
|
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_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 \
|
reset for domain %s
|
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 \
|
on base-dn %s : %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 \
|
Byte Count=%s (Fixed)
|
NOTICE_ERR_FRACTIONAL_CONFIG_UNKNOWN_OBJECT_CLASS_160=Wrong fractional \
|
replication configuration: could not find object class definition for %s in \
|
schema
|
NOTICE_ERR_FRACTIONAL_CONFIG_UNKNOWN_ATTRIBUTE_TYPE_161=Wrong fractional \
|
replication configuration : could not find attribute type definition for %s \
|
in schema
|
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 : \
|
%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_CHANGENUMBER_DATABASE_173=An error occurred when accessing the \
|
change number database : %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 \
|
as local server
|
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 \
|
local server
|
SEVERE_ERR_DS_DISCONNECTED_DURING_HANDSHAKE_178=Directory server %s was \
|
attempting to connect to replication server %s but has disconnected in \
|
handshake phase
|
SEVERE_ERR_RS_DISCONNECTED_DURING_HANDSHAKE_179=Replication server %s was \
|
attempting to connect to replication server %s but has disconnected in \
|
handshake phase
|
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 \
|
change log: %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 for the provided cookie '%s'
|
MILD_ERR_INIT_EXPORTER_DISCONNECTION_189=Domain %s (server id: %s) : \
|
remote exporter server disconnection (server id: %s ) detected during \
|
initialization
|
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. \
|
Servers list: %s
|
SEVERE_ERR_INIT_RS_DISCONNECTION_DURING_EXPORT_195=\
|
When initializing remote server(s), connection to Replication Server with \
|
serverId=%s is lost
|
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
|
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 \
|
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. 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 \
|
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)
|
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
|
MILD_ERR_READING_OLDEST_THEN_NEWEST_IN_CHANGENUMBER_DATABASE_217=An error occurred \
|
when accessing the change number database: impossible to read the newest record \
|
after having successfully read the oldest. Database might have been cleaned or \
|
closed between successive reads
|
SEVERE_WARN_CANNOT_OPEN_DATABASE_BECAUSE_SHUTDOWN_WAS_REQUESTED_218=Cannot \
|
open database %s because shutdown was requested from replication server RS(%d)
|
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)
|
SEVERE_ERR_CANNOT_CREATE_REPLICA_DB_BECAUSE_CHANGELOG_DB_SHUTDOWN_235=Could not \
|
create replica database because the changelog database is shutting down
|
FATAL_ERR_CHANGE_NUMBER_INDEXER_UNEXPECTED_EXCEPTION_236=An unexpected error \
|
forced the %s thread to shutdown: %s. \
|
The changeNumber attribute will not move forward anymore. \
|
You can reenable this thread by first setting the "compute-change-number" \
|
property to false and then back to true
|
FATAL_ERR_CHANGE_NUMBER_INDEXER_INCONSISTENT_CSN_READ_237=Aborting initialization: \
|
expected the newest change number index record CSN '%s' to be equal to \
|
the CSN read from the replica DBs '%s'
|
