| | |
| | | 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_INITIALIZE_DB_10=Changelog failed to start because the \ |
| | | MILD_ERR_COULD_NOT_INITIALIZE_DB_10=The replication server failed to start because the \ |
| | | database %s could not be opened |
| | | MILD_ERR_COULD_NOT_READ_DB_11=Changelog failed to start because the database \ |
| | | %s could not be read |
| | | 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 |
| | | MILD_ERR_NEED_CHANGELOG_PORT_13=The replication server port must be defined |
| | |
| | | NOTICE_NO_CHANGELOG_SERVER_LISTENING_17=There is no replication server \ |
| | | listening on %s |
| | | NOTICE_CHANGELOG_MISSING_CHANGES_18=The replication server %s is missing some \ |
| | | changes that this server has already processed |
| | | changes that this server has already processed on suffix %s |
| | | NOTICE_NEED_MORE_THAN_ONE_CHANGELOG_SERVER_19=More than one replication \ |
| | | server should be configured |
| | | SEVERE_ERR_EXCEPTION_STARTING_SESSION_20=Caught exception during initial \ |
| | | communication with replication server: %s |
| | | NOTICE_EXCEPTION_STARTING_SESSION_20=Caught Exception during initial \ |
| | | communication on domain %s with replication server %s : %s |
| | | MILD_ERR_CANNOT_RECOVER_CHANGES_21=Error when searching old changes from the \ |
| | | database for base DN %s |
| | | NOTICE_COULD_NOT_FIND_CHANGELOG_WITH_MY_CHANGES_22=Could not find a \ |
| | | replication server that has seen all the local changes. Going to replay \ |
| | | replication server that has seen all the local changes on suffix %s. Going to replay \ |
| | | changes |
| | | NOTICE_COULD_NOT_FIND_CHANGELOG_23=Could not connect to any replication \ |
| | | server on suffix %s, retrying... |
| | |
| | | NOTICE_DISCONNECTED_FROM_CHANGELOG_63=The connection to Replication Server %s \ |
| | | has been dropped by the Replication Server |
| | | SEVERE_ERR_CHANGELOG_ERROR_SENDING_INFO_64=An unexpected error occurred \ |
| | | while sending a Server Info message to %s. This connection is going to be \ |
| | | while sending a Server Info message to %s. This connection is going to be \ |
| | | closed and reopened |
| | | 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 \ |
| | |
| | | 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 |
| | | 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 |
| | | DEBUG_REPLICATION_PORT_IOEXCEPTION_72=An IOException was caught while \ |
| | | listening on the replication port |
| | | listening on the replication port |
| | | SEVERE_ERR_SEARCHING_GENERATION_ID_73=An unexpected error %s occured when \ |
| | | searching for generation id for domain : %s |
| | | SEVERE_ERR_SEARCHING_DOMAIN_BACKEND_74=An unexpected error occured when \ |
| | | searching for the backend of the domain : %s |
| | | SEVERE_ERR_LOADING_GENERATION_ID_75=An unexpected error occured when \ |
| | | searching in %s for the generation ID : %s |
| | | SEVERE_ERR_UPDATING_GENERATION_ID_76=An unexpected error %s occured \ |
| | | when updating generation ID for the domain : %s |
| | | NOTICE_BAD_GENERATION_ID_77=On suffix %s. server %s presented generation ID=%s \ |
| | | when expected generation ID=%s. Consequently, replication is degraded for that server |
| | | NOTICE_RESET_GENERATION_ID_78=The generation ID has been reset for domain %s.\ |
| | | Replication is now degraded for this domain |
| | | MILD_ERR_ERROR_MSG_RECEIVED_79=The following error has been received : <%s> |
| | | MILD_ERR_IGNORING_UPDATE_FROM_80=Update <%s> received from server <%s> is \ |
| | | ignored due to a bad generation ID of this server |
| | | MILD_ERR_IGNORING_UPDATE_TO_81=Update <%s> will not be sent to server %s that has \ |
| | | not the right generation ID |
| | | 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 occured 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 |