# 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
# trunk/opends/resource/legal-notices/OpenDS.LICENSE
# or https://OpenDS.dev.java.net/OpenDS.LICENSE.
# 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
# trunk/opends/resource/legal-notices/OpenDS.LICENSE.  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-2008 Sun Microsystems, Inc.
#
#
# 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=\u914d\u7f6e\u7684 DN \u5df2\u6709\u5176\u4ed6\u7db2\u57df\u4f7f\u7528
MILD_ERR_INVALID_CHANGELOG_SERVER_4=\u8907\u88fd\u4f3a\u670d\u5668\u914d\u7f6e\u7121\u6548
MILD_ERR_UNKNOWN_HOSTNAME_5=\u8907\u88fd\u4f3a\u670d\u5668\u7121\u6cd5\u555f\u52d5\uff0c\u56e0\u70ba\u4e3b\u6a5f\u540d\u7a31\u4e0d\u660e
MILD_ERR_COULD_NOT_BIND_CHANGELOG_6=\u8907\u88fd\u4f3a\u670d\u5668\u7121\u6cd5\u555f\u52d5: \u7121\u6cd5\u9023\u7d50\u81f3\u5075\u807d\u9023\u63a5\u57e0: %d\u3002\u932f\u8aa4: %s
MILD_ERR_UNKNOWN_TYPE_7=\u4f5c\u696d\u985e\u578b\u4e0d\u660e: %s
MILD_ERR_OPERATION_NOT_FOUND_IN_PENDING_9=\u5167\u90e8\u932f\u8aa4: \u5728\u64f1\u7f6e\u6e05\u55ae\u4e2d\u627e\u4e0d\u5230\u4f5c\u696d %s \u8b8a\u66f4\u865f\u78bc %s
MILD_ERR_COULD_NOT_INITIALIZE_DB_10=\u8907\u88fd\u4f3a\u670d\u5668\u7121\u6cd5\u555f\u52d5\uff0c\u56e0\u70ba\u8cc7\u6599\u5eab %s \u7121\u6cd5\u958b\u555f
MILD_ERR_COULD_NOT_READ_DB_11=\u8907\u88fd\u4f3a\u670d\u5668\u7121\u6cd5\u555f\u52d5\uff0c\u56e0\u70ba\u7121\u6cd5\u8b80\u53d6\u8cc7\u6599\u5eab %s: %s
MILD_ERR_EXCEPTION_REPLAYING_OPERATION_12=\u91cd\u65b0\u57f7\u884c\u4f5c\u696d %s \u6642\u767c\u751f\u7570\u5e38: %s
MILD_ERR_NEED_CHANGELOG_PORT_13=\u5fc5\u9808\u5b9a\u7fa9\u8907\u88fd\u4f3a\u670d\u5668\u9023\u63a5\u57e0
###DEBUG_ERROR_UPDATING_RUV_14=Error %s when updating server state %s : %s \
### base dn : %s
MILD_ERR_ERROR_SEARCHING_RUV_15=\u641c\u5c0b\u4f3a\u670d\u5668\u72c0\u614b %2$s \u6642\u767c\u751f\u932f\u8aa4 %1$s: %3$s\uff0c\u57fa\u5e95 dn: %4$s
NOTICE_SERVER_DISCONNECT_16=%s has disconnected from this replication server %s
NOTICE_NO_CHANGELOG_SERVER_LISTENING_17=\u6c92\u6709\u8907\u88fd\u4f3a\u670d\u5668\u5075\u807d\u65bc %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=\u61c9\u914d\u7f6e\u591a\u90e8\u8907\u88fd\u4f3a\u670d\u5668
###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=\u5f9e\u8cc7\u6599\u5eab\u4e2d\u641c\u5c0b\u57fa\u5e95 DN %s \u7684\u820a\u6709\u8b8a\u66f4\u6642\u767c\u751f\u932f\u8aa4
NOTICE_COULD_NOT_FIND_CHANGELOG_WITH_MY_CHANGES_22=\u627e\u4e0d\u5230\u5c3e\u78bc %s \u5df2\u5177\u6709\u6240\u6709\u672c\u6a5f\u8b8a\u66f4\u7684\u8907\u88fd\u4f3a\u670d\u5668\u3002\u627e\u5230 %d \u90e8\u4e0d\u662f\u6700\u65b0\u7684\u8907\u88fd\u4f3a\u670d\u5668\u3002\u5373\u5c07\u91cd\u65b0\u57f7\u884c\u8b8a\u66f4
NOTICE_COULD_NOT_FIND_CHANGELOG_23=\u7121\u6cd5\u9023\u7dda\u81f3\u5c3e\u78bc %s \u7684\u4efb\u4f55\u8907\u88fd\u4f3a\u670d\u5668\uff0c\u6b63\u5728\u91cd\u8a66...
NOTICE_EXCEPTION_CLOSING_DATABASE_24=\u95dc\u9589\u8907\u88fd\u4f3a\u670d\u5668\u8cc7\u6599\u5eab %s \u6642\u767c\u751f\u932f\u8aa4:
###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
###SEVERE_ERR_IGNORE_BAD_DN_IN_DATABASE_IDENTIFIER_27=A badly formatted DN was \
### found in the list of database known by this Replication Server :%s. This \
### Identifier will be ignored
###SEVERE_ERR_ERROR_CLOSING_CHANGELOG_ENV_28=Error closing the Replication Server \
### database :
###SEVERE_ERR_EXCEPTION_CHANGELOG_TRIM_FLUSH_29=Error during the Replication \
### Server database trimming or flush process. The Changelog service is going to \
### shutdown
###SEVERE_ERR_REPLICATION_SERVER_CONNECTION_ERROR_30=Error in Replication Server \
### handshake processing. Connection from/to %s is aborted
###SEVERE_ERR_UNKNOWN_MESSAGE_31=%s has sent an unknown message. Closing the \
### connection
###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
###SEVERE_ERR_EXCEPTION_RECEIVING_REPLICATION_MESSAGE_34=An Exception was caught \
### while receiving replication message : %s
MILD_ERR_LOOP_REPLAYING_OPERATION_35=\u91cd\u65b0\u57f7\u884c\u4f5c\u696d\u6642\u5075\u6e2c\u5230\u8ff4\u5708: %s \u932f\u8aa4 %s
MILD_ERR_FILE_CHECK_CREATE_FAILED_36=\u6e2c\u8a66\u8907\u88fd\u4f3a\u670d\u5668\u8cc7\u6599\u5eab\u7684\u5b58\u5728\u6027\u6216\u5617\u8a66\u5efa\u7acb\u5176\u76ee\u9304\u6642\u767c\u751f\u7570\u5e38: %s
INFO_CHANGELOG_SERVER_ATTR_37=\u6b64\u8907\u88fd\u4f3a\u670d\u5668\u61c9\u9023\u7dda\u4e4b\u8907\u88fd\u4f3a\u670d\u5668\u7684\u6e05\u55ae\u3002\u6b64\u5c6c\u6027\u7684\u6bcf\u500b\u503c\uff0c\u5747\u61c9\u5305\u542b\u4e00\u500b\u7531\u4e3b\u6a5f\u540d\u7a31\u8207\u9023\u63a5\u57e0\u865f\u78bc\u7d44\u6210\u7684\u503c\u5efa\u7f6e\uff0c\u4e3b\u6a5f\u540d\u7a31\u8207\u9023\u63a5\u57e0\u865f\u78bc\u4e4b\u9593\u4ee5\u300c:\u300d\u9694\u958b
INFO_SERVER_ID_ATTR_38=\u4f3a\u670d\u5668 ID\u3002\u5c0d\u65bc\u62d3\u6a38\u4e2d\u7684\u6bcf\u90e8\u8907\u88fd\u4f3a\u670d\u5668\uff0c\u5747\u61c9\u70ba\u5176\u6307\u5b9a\u4e00\u500b\u552f\u4e00\u7684\u4f3a\u670d\u5668 ID
INFO_CHANGELOG_PORT_ATTR_39=\u8907\u88fd\u4f3a\u670d\u5668\u5c07\u7528\u4ee5\u5075\u807d\u4f86\u81ea LDAP \u4f3a\u670d\u5668\u4e4b\u9023\u7dda\u7684\u9023\u63a5\u57e0\u865f\u78bc
INFO_WINDOW_SIZE_ATTR_40=\u63a5\u6536\u8907\u88fd\u4f3a\u670d\u5668\u7684\u8996\u7a97\u5927\u5c0f
INFO_QUEUE_SIZE_ATTR_41=\u63a5\u6536\u8907\u88fd\u4f3a\u670d\u5668\u7684\u4f47\u5217\u5927\u5c0f\u3002\u8907\u88fd\u4f3a\u670d\u5668\u6703\u5728\u5176\u8a18\u61b6\u9ad4\u4f47\u5217\u4e2d\u6392\u5165\u6b64\u6578\u91cf\u7684\u8a0a\u606f\uff0c\u4e26\u5c07\u8f03\u820a\u7684\u8a0a\u606f\u5132\u5b58\u5230\u6c38\u4e45\u5132\u5b58\u88dd\u7f6e\u4e2d\u3002\u8907\u88fd\u5ef6\u9072\u8d85\u904e\u6b64\u5927\u5c0f\u6642\uff0c\u4f7f\u7528\u8f03\u5927\u7684\u5927\u5c0f\u5c07\u53ef\u6539\u5584\u6548\u80fd\uff0c\u4f46\u4e5f\u6703\u8017\u7528\u8f03\u591a\u7684\u8a18\u61b6\u9ad4
INFO_CHANGELOG_DIR_PATH_ATTR_42=\u8907\u88fd\u4f3a\u670d\u5668\u76ee\u9304\u3002\u8907\u88fd\u4f3a\u670d\u5668\u6703\u5728\u6b64\u8def\u5f91\u4e0b\u5efa\u7acb\u6240\u6709\u6c38\u4e45\u5132\u5b58\u88dd\u7f6e
INFO_PURGE_DELAY_ATTR_43=\u8907\u88fd\u4f3a\u670d\u5668\u6e05\u9664\u5ef6\u9072\uff1b\u8907\u88fd\u4f3a\u670d\u5668\u5728\u4fdd\u7559\u6240\u6709\u7684\u8b8a\u66f4\u9054\u6b64\u6642\u9593\u9577\u5ea6\u5f8c\uff0c\u5373\u6703\u52a0\u4ee5\u522a\u9664\u3002\u6b64\u503c\u5b9a\u7fa9\u5099\u4efd\u53ef\u9032\u884c\u9084\u539f\u7684\u6642\u9650\uff0c\u56e0\u70ba\u8907\u88fd\u4f3a\u670d\u5668\u5c07\u7121\u6cd5\u91cd\u65b0\u6574\u7406\u542b\u6709\u820a\u7248\u8cc7\u6599\u7684 LDAP \u4f3a\u670d\u5668\u3002\u96f6\u503c\u7528\u4ee5\u6307\u5b9a\u7121\u9650\u5ef6\u9072 (\u6216\u6c38\u4e0d\u6e05\u9664)
###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=Invalid source for the import
###SEVERE_ERR_INVALID_EXPORT_TARGET_46=Invalid target for the export
###SEVERE_ERR_NO_REACHABLE_PEER_IN_THE_DOMAIN_47=No reachable peer in the domain
###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=\u5f9e %s \u63a5\u6536\u5230\u7a7a\u8a0a\u606f
NOTICE_READER_EXCEPTION_53=\u8b80\u53d6\u4f86\u81ea %s \u7684\u8a0a\u606f\u6642\u767c\u751f\u7570\u5e38
###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=\u5075\u6e2c\u5230\u885d\u7a81\uff0c\u4f46\u7121\u6cd5\u589e\u52a0\u885d\u7a81\u8cc7\u8a0a\u3002\u4f5c\u696d:
MILD_ERR_CANNOT_RENAME_CONFLICT_ENTRY_58=\u5617\u8a66\u91cd\u65b0\u547d\u540d\u885d\u7a81\u9805\u76ee\u6642\u767c\u751f\u932f\u8aa4:
MILD_ERR_EXCEPTION_RENAME_CONFLICT_ENTRY_59=\u5617\u8a66\u91cd\u65b0\u547d\u540d\u885d\u7a81\u9805\u76ee\u6642\u767c\u751f\u7570\u5e38:
###SEVERE_ERR_CHANGELOG_UNSUPPORTED_UTF8_ENCODING_60=The JVM does not support \
### UTF-8. This is required to be able to encode the changes in the database. \
### 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_DISCONNECTED_FROM_CHANGELOG_63=The connection to Replication Server %s %s has been dropped by the Replication Server for %s in local server id %s
###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=\u7121\u6cd5\u91cd\u65b0\u57f7\u884c\u542b\u6709 ChangeNumber %2$s\u3001\u932f\u8aa4 %3$s %4$s \u7684\u4f5c\u696d %1$s
MILD_ERR_UNKNOWN_ATTRIBUTE_IN_HISTORICAL_68=\u9805\u76ee %s \u542b\u6709\u5c6c\u6027 %s \u7684\u6b77\u7a0b\u8cc7\u8a0a\uff0c\u4f46\u6b64\u5c6c\u6027\u4e26\u672a\u5b9a\u7fa9\u65bc\u6a21\u5f0f\u4e2d\u3002\u5c07\u5ffd\u7565\u6b64\u8cc7\u8a0a
NOTICE_UNRESOLVED_CONFLICT_69=\u5c0d DN %s \u5075\u6e2c\u5230\u7121\u6cd5\u89e3\u6c7a\u7684\u885d\u7a81
###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
###DEBUG_REPLICATION_PORT_IOEXCEPTION_72=An IOException was caught while \
### listening on the replication port
###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
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 \
###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=\u91cd\u65b0\u521d\u59cb\u5316\u7db2\u57df %s \u4e0a\u7684\u901a\u8a0a\u6642\u767c\u751f\u7570\u5e38: %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=\u5354\u5b9a\u932f\u8aa4: \u8907\u88fd\u4f3a\u670d\u5668\u4e0d\u61c9\u70ba\u8a0a\u606f\u985e\u578b %s \u7684\u76ee\u6a19
###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=\u532f\u51fa\u9805\u76ee %s \u6642\u767c\u751f\u932f\u8aa4: %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
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 \u6b63\u5728\u95dc\u9589\u968e\u6bb5\u4f5c\u696d\uff0c\u56e0\u70ba\u5b83\u7121\u6cd5\u5075\u6e2c\u5230\u6d3b\u52d5\u8a0a\u865f
###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=\u5f9e %s (%s) \u57f7\u884c\u7684 SSL \u9023\u7dda\u5617\u8a66\u5931\u6557: %s
###SEVERE_ERR_MISSING_REMOTE_MONITOR_DATA_106=Monitor data of remote servers \
### are missing due to an error in the retrieval process. Potentially a server \
### is too slow to provide its monitoring data over the protocol
###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=Exception raised when \
### sending request to get remote monitor data
###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_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 \
###for domain %s : %s
###SEVERE_ERR_COMPUTING_FAKE_OPS_115=Caught exception computing fake operations \
###for domain %s for replication server %s : %s
NOTICE_IGNORING_REMOTE_MONITOR_DATA_116=\u5f9e\u4f3a\u670d\u5668 ID \u70ba %s \u7684\u4f3a\u670d\u5668\u6536\u5230\u90e8\u5206\u76e3\u8996\u8cc7\u6599\uff0c\u4f46\u56e0\u592a\u665a\u9001\u9054\u800c\u906d\u5230\u5ffd\u7565
NOTICE_SERVER_STATE_RECOVERY_117=\u7db2\u57df %s \u7684 ServerState \u56de\u5fa9\u5df2\u4f7f\u7528 changeNumber %s \u66f4\u65b0
###SEVERE_ERR_RESET_GENERATION_CONN_ERR_ID_118=The generation ID could not be \
###reset for domain %s because it is NOT connected to the replication. You should \
###check in the configuration that the domain is enabled
###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
###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)
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 \
### 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
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
NOTICE_FULL_UPDATE_ENGAGED_FOR_REMOTE_START_143=Local directory server %s is starting online full update for exporting suffix %s data 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
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 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
MILD_ERR_ERROR_RETRIEVING_MONITOR_DATA_155=Error retrieving monitoring data: %s