Log message reference

Severity: WARNING
Message: The provided string "%s" could not be parsed as a valid Access Control Instruction (ACI) because it failed general ACI syntax evaluation.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) version value "%s" is invalid, only the version 3.0 is supported.

Severity: WARNING
Message: The provided Access Control Instruction access type value "%s" is invalid. A valid access type value is either allow or deny.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) rights values "%s" are invalid. The rights must be a list of 1 to 6 comma-separated keywords enclosed in parentheses.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) rights keyword values "%s" are invalid. The valid rights keyword values are one or more of the following: read, write, add, delete, search, compare or the single value all.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule value "%s" is invalid because it is missing a close parenthesis that corresponded to the initial open parenthesis.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule value "%s" is invalid. A valid bind rule value must be in the following form: keyword operator "expression".

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule keyword value "%s" is invalid. A valid keyword value is one of the following: userdn, groupdn, roledn, userattr,ip, dns, dayofweek, timeofday or authmethod.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule operator value "%s" is invalid. A valid bind rule operator value is either '=' or "!=".

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule expression value corresponding to the keyword value "%s" is missing an expression. A valid bind rule value must be in the following form: keyword operator "expression".

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule boolean operator value "%s" is invalid. A valid bind rule boolean operator value is either "OR" or "AND".

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule keyword string "%s" is invalid for the bind rule operator string "%s".

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule userdn expression failed to URL decode for the following reason: %s.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule groupdn expression value "%s" is invalid. A valid groupdn keyword expression value requires one or more LDAP URLs in the following format: ldap:///groupdn [|| ldap:///groupdn] …​ [|| ldap:///groupdn].

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule groupdn expression value failed to URL decode for the following reason: %s.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule ip expression value "%s" is invalid. A valid ip keyword expression requires one or more comma-separated elements of a valid IP address list expression.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule dns expression value "%s" is invalid. A valid dns keyword expression value requires a valid fully qualified DNS domain name.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule dns expression value "%s" is invalid, because a wild-card pattern was found in the wrong position. A valid dns keyword wild-card expression value requires the '*' character only be in the leftmost position of the domain name.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule dayofweek expression value "%s" is invalid, because of an invalid day of week value. A valid dayofweek value is one of the following English three-letter abbreviations for the days of the week: sun, mon, tue, wed, thu, fri, or sat.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule timeofday expression value "%s" is invalid. A valid timeofday value is expressed as four digits representing hours and minutes in the 24-hour clock (0 to 2359).

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule timeofday expression value "%s" is not in the valid range. A valid timeofday value is expressed as four digits representing hours and minutes in the 24-hour clock (0 to 2359).

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule authmethod expression value "%s" is invalid. A valid authmethod value is one of the following: none, simple,SSL, or "sasl mechanism", where mechanism is one of the supported SASL mechanisms including CRAM-MD5, DIGEST-MD5, and GSSAPI.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule userattr expression value "%s" is invalid.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule userattr expression inheritance pattern value "%s" is invalid. A valid inheritance pattern value must have the following format: parent[inheritance_level].attribute#bindType.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule userattr expression inheritance pattern value "%s" is invalid. The inheritance level value cannot exceed the max level limit of %s.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule userattr expression inheritance pattern value "%s" is invalid because it is non-numeric.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) target rule value "%s" is invalid. A valid target rule value must be in the following form: keyword operator "expression".

Severity: WARNING
Message: The provided Access Control Instruction (ACI) target keyword value "%s" is invalid. A valid target keyword value is one of the following: target, targetscope, targetfilter, targetattr or targattrfilters.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) target operator value "%s" is invalid. The only valid target operator value for the "%s" keyword is '='.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) target keyword value "%s" was seen multiple times in the ACI "%s".

Severity: WARNING
Message: The provided Access Control Instruction (ACI) target keyword operator value "%s" is invalid. A valid target keyword operator value is either '=' or "!=".

Severity: WARNING
Message: The provided Access Control Instruction (ACI) targetscope expression operator value "%s" is invalid. A valid targetscope expression value is one of the following: one, onelevel, subtree or subordinate.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) target expression value "%s" is invalid. A valid target keyword expression value requires a LDAP URL in the following format: ldap:///distinguished_name_pattern.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) target expression DN value "%s" is invalid. The target expression DN value must be a descendant of the ACI entry DN "%s", if no wild-card is specified in the target expression DN.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) targetattr expression value "%s" is invalid. A valid targetattr keyword expression value requires one or more valid attribute type names in the following format: attribute1 [|| attribute2] …​ [|| attributeN]. Attribute options are not supported.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) targetfilter expression value "%s" is invalid because it is not a valid LDAP filter.

Severity: INFO
Message: An attempt to add the entry "%s" containing an aci attribute type failed, because the authorization DN "%s" lacked modify-acl privileges.

Severity: INFO
Message: An attempt to modify an aci attribute type in the entry "%s" failed, because the authorization DN "%s" lacked modify-acl privileges.

Severity: WARNING
Message: An attempt to add the entry "%s" containing an aci attribute type failed because of the following reason: %s.

Severity: WARNING
Message: An attempt to modify an aci attribute type in the entry "%s" failed because of the following reason: %s.

Severity: WARNING
Message: "%s", located in the entry "%s", because of the following reason: %s.

Severity: INFO
Message: Added %s Access Control Instruction (ACI) attribute types found in context "%s" to the access control evaluation engine.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) targattrfilter expression value %s is invalid because it is not in the correct format. A valid targattrsfilters expression value must be in the following format: "add=attr1: F1 && attr2: F2 …​ && attrN: FN,del= attr1: F1 && attr2: F2 …​ && attrN: FN".

Severity: WARNING
Message: The provided Access Control Instruction (ACI) targattrfilter expression value %s is invalid because the both operation tokens match in the two filter lists.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) targattrfilters expression value %s is invalid because there are more than two filter list statements.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) targattrfilters expression value %s is invalid because the provided filter list string is in the wrong format. A valid targattrfilters filter list must be in the following format: add=attr1: F1 && attr2: F2 …​ && attrN: FN.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) targattrfilters expression value %s is invalid because one or more of the specified filters are invalid for the following reason: %s.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) targattrfilters expression value %s is invalid because one or more of the specified filters are invalid because of non-matching attribute type names in the filter.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) attribute name value %s is invalid. A valid attribute type name must begin with an ASCII letter and must contain only ASCII letters,digits or the "-" character.

Severity: NOTICE
Message: The SASL mechanism "%s" provided in the Access Control Instruction (ACI) bind rule authmethod expression is not one of the currently registered mechanisms in the server.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule dns expression value "%s" references hostname %s, but the canonical representation for that hostname is configured to be %s. The server will attempt to automatically interpret the correct localhost value.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule dns expression value "%s" references hostname %s, which resolves to IP address %s, but the canonical hostname for that IP address is %s. This likely means that the provided hostname will never match any clients.

Severity: WARNING
Message: An error occurred while attempting to determine whether hostname %s referenced in dns expression bind rule "%s" used the correct canonical representation: %s. This likely means that the provided hostname will never match any clients.

Severity: INFO
Message: Added %s Global Access Control Instruction (ACI) attribute types to the access control evaluation engine.

Severity: INFO
Message: An unexpected error occurred while processing the ds-cfg-global-aci attribute in configuration entry %s: %s.

Severity: INFO
Message: An unexpected error occurred while processing the aci attributes in the configuration system: %s.

Severity: WARNING
Message: The pattern DN %s is not valid because it contains two consecutive wildcards in an attribute value.

Severity: WARNING
Message: The pattern DN %s is not valid because it uses wildcards for substring matching on an attribute type. A single wildcard is allowed in place of an attribute type.

Severity: WARNING
Message: The pattern DN %s is not valid because it contains a wildcard in an attribute type in a multi-valued RDN.

Severity: WARNING
Message: Selfwrite check skipped because an attribute "%s" with a distinguished name syntax was not a valid DN.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) targetattr expression value "%s" is invalid because the expression contains invalid or duplicate tokens.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) expression value "%s" is invalid because it contains the roledn keyword, which is not supported, replace it with the groupdn keyword.

Severity: WARNING
Message: Failed to decode the Access Control Instruction (ACI)%s.

Severity: WARNING
Message: The server is being put into lockdown mode because invalid ACIs rules were detected either when the server was started or during a backend initialization.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule userattr expression value failed to URL decode for the following reason: %s.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule userattr expression value failed to parse because the ldap URL "%s" contains an empty base DN.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule userattr expression value failed to parse because the attribute field of the ldap URL "%s" either contains more than one description or the field is empty.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule IP address expression failed to parse because the prefix part of the expression "%s" has an invalid format.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule IP address expression failed to parse because the prefix value of the expression "%s" was an invalid value. All values must greater than or equal to 0 and either less than or equal 32 for IPV4 addresses or less than or equal to 128 for IPV6 addresses.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule IP address expression failed to parse because the prefix part of the expression "%s" has an non-numeric value.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule IP address expression failed to parse because the IPv4 address expression "%s" format was invalid.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule IP address expression failed to parse because the IPv4 address expression "%s" contains an invalid value. All values of the address must be between 0 and 255.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule IP address expression failed to parse because the IPv4 address expression "%s" contains a non-numeric value.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule IP address expression failed to parse because the IPv6 address expression "%s" contains an illegal wildcard character. Wildcards are not supported when using IPv6 addresses in a IP bind rule expression.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule IP address expression "%s" failed to parse for the following reason: "%s".

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule IP address expression failed to parse because the netmask part of the expression "%s" has an invalid format.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule IP address expression failed to parse because the netmask part of the expression "%s" has an invalid value.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) targetcontrol expression value "%s" is invalid. A valid targetcontrol keyword expression value requires one or more valid control OID strings in the following format: oid [|| oid1] …​ [|| oidN].

Severity: WARNING
Message: The provided Access Control Instruction (ACI) targetcontrol OID value "%s" could not be parsed because the value contained an illegal character %c at position %d.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) targetcontrol OID value "%s" could not be parsed because the numeric OID contained two consecutive periods at position %d.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) extop expression value "%s" is invalid. A valid extop keyword expression value requires one or more valid extended operation request OID strings in the following format: oid [|| oid1] …​ [|| oidN].

Severity: WARNING
Message: Backend %s does not have a presence index defined for attribute type %s. Access control initialization may take a very long time to complete in this backend.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule SSF expression "%s" failed to parse for the following reason: "%s".

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule ssf expression value "%s" is not in the valid range. A valid ssf value is in the range of 1 to 1024.

Severity: WARNING
Message: The provided Access Control Instruction (ACI) bind rule timeofday expression "%s" failed to parse for the following reason: "%s".

Severity: NOTICE
Message: The global access control policy '%s' has been added.

Severity: NOTICE
Message: The global access control policy '%s' has been removed.

Severity: NOTICE
Message: The global access control policy '%s' has been modified.

Severity: NOTICE
Message: The global access control engine has been initialized with %d policies.

Severity: ERROR
Message: The global access control policy defined in "%s" could not be parsed because it contains an invalid target DN pattern "%s".

Severity: ERROR
Message: The global access control policy defined in "%s" could not be parsed because it contains an invalid user DN pattern "%s".

Severity: ERROR
Message: The global access control policy defined in "%s" could not be parsed because it contains an unrecognized control alias "%s".

Severity: ERROR
Message: The global access control policy defined in "%s" could not be parsed because it contains an unrecognized extended operation alias "%s".

Severity: INFO
Message: This utility can be used to display basic server information.

Severity: INFO
Message: Adds the local server (with version 7.0 or more) to a topology with older server versions (prior to 7.0).

Severity: INFO
Message: Establishing connections.

Severity: INFO
Message: Checking registration information.

Severity: INFO
Message: %s entries processed (%s %% complete).

Severity: INFO
Message: %s entries processed.

Severity: INFO
Message: %s remaining to be processed.

Severity: ERROR
Message: A target server must be specified either by using LDAP connection options or the --%s option.

Severity: ERROR
Message: An error occurred while reading the server configuration: %s.

Severity: ERROR
Message: An error occurred while printing server status script friendly output: %s.

Severity: INFO
Message: Run status.

Severity: INFO
Message: Started.

Severity: INFO
Message: Stopped.

Severity: INFO
Message: Open connections.

Severity: INFO
Message: General details.

Severity: INFO
Message: Host name.

Severity: INFO
Message: Server ID.

Severity: INFO
Message: Administration port (LDAPS).

Severity: INFO
Message: Version.

Severity: INFO
Message: Installation path.

Severity: INFO
Message: Instance path.

Severity: INFO
Message: Installation and instance path.

Severity: INFO
Message: Running server Java details.

Severity: INFO
Message: Java version.

Severity: INFO
Message: Java vendor.

Severity: INFO
Message: JVM available CPUs.

Severity: INFO
Message: JVM max heap size.

Severity: INFO
Message: Connection handlers.

Severity: INFO
Message: Name.

Severity: INFO
Message: Port.

Severity: INFO
Message: Protocol.

Severity: INFO
Message: Load m1 rate.

Severity: INFO
Message: Load m5 rate.

Severity: INFO
Message: Local backends.

Severity: INFO
Message: Proxy backends.

Severity: INFO
Message: Backend.

Severity: INFO
Message: Type.

Severity: INFO
Message: Active cache.

Severity: INFO
Message: Base DN.

Severity: INFO
Message: Entries.

Severity: INFO
Message: Replication.

Severity: INFO
Message: Receive delay.

Severity: INFO
Message: Replay delay.

Severity: INFO
Message: Disk space.

Severity: INFO
Message: State.

Severity: INFO
Message: Free space.

Severity: INFO
Message: There are no connection handlers setup in the server.

Severity: INFO
Message: There are no local backends setup in the server.

Severity: INFO
Message: There are no proxy backends setup in the server.

Severity: INFO
Message: No disks are monitored by the server.

Severity: INFO
Message: Connect to the server to obtain JVM information.

Severity: INFO
Message: Connect to the server to obtain disk space information.

Severity: ERROR
Message: Unable to perform the search on the monitor backend. To display information, the status tool requires the remote server monitor backend to be enabled.

Severity: INFO
Message: The folder into which the files will be placed into.

Severity: INFO
Message: {directory}.

Severity: INFO
Message: The instance is running.

Severity: INFO
Message: The instance is not running.

Severity: INFO
Message: Password to use to bind to the server.

Severity: INFO
Message: {password}.

Severity: INFO
Message: Path to the JDK utility binaries directory such as jstack.

Severity: INFO
Message: {directory}.

Severity: INFO
Message: Specifies whether audit files are excluded.

Severity: INFO
Message: Specifies whether keystore files are excluded.

Severity: INFO
Message: Specifies that the tool should not interact with the server, that is no LDAP operation, and no jstack sampling.

Severity: INFO
Message: Specifies whether a Java Heap Dump (using jmap) should be produced. The binary file is generated at the same location as the ZIP archive before being added to it; please make sure that the target directory’s volume has sufficient capacity.

Severity: INFO
Message: Maximum number of log files to collect. Ignored if --logsAfterDate is provided.

Severity: INFO
Message: {number}.

Severity: INFO
Message: Collect log files after this date. Format "YYYYMMDDhhmmss" like "20161123143612" = 23 November 2016, 14:36 12s. Overrides --maxLogFiles.

Severity: INFO
Message: {date}.

Severity: INFO
Message: When the server is embedded in OpenAM, there is no PID file. Therefore this option indicates the server PID of the OpenAM application server.

Severity: INFO
Message: {pid}.

Severity: INFO
Message: This tool collects support data from the OpenDJ instance it is bound to.

Severity: NOTICE
Message: <xinclude:include href="description-supportextract.xml" />.

Severity: NOTICE
Message: extract support data.

Severity: ERROR
Message: Error: %s.

Severity: ERROR
Message: The output directory "%s" could not be found.

Severity: ERROR
Message: The number argument for "maxLogFiles" is invalid.

Severity: ERROR
Message: The date argument for "logsAfterDate" is invalid.

Severity: ERROR
Message: The serverPID argument is not a valid number.

Severity: ERROR
Message: The --bindDN and/or --bindPassword arguments are missing.

Severity: ERROR
Message: Could not collect monitoring data from the directory server: %s.

Severity: ERROR
Message: Could not collect all the files.

Severity: ERROR
Message: An error occurred while parsing the command-line arguments: The argument --outputDirectory is required to have a value but none was provided in the argument list and no default value is available.

Severity: INFO
Message: Continuing data gathering though there was an error: %s.

Severity: INFO
Message: The following archive has been created : %s.

Severity: NOTICE
Message: Could not find "java.properties".

Severity: NOTICE
Message: Error while loading "java.properties": %s.

Severity: INFO
Message: No monitoring data can be collected when the server is not running or no server interaction is allowed.

Severity: INFO
Message: No JVM stack dump can be produced when the server is not running or no server interaction is allowed.

Severity: ERROR
Message: Could not find the "%s" command in "%s".

Severity: ERROR
Message: Skipping log "%s" (unsupported config).

Severity: INFO
Message: Collecting the configuration files.

Severity: INFO
Message: Collecting process statistics.

Severity: INFO
Message: Making copy of the %s file before collecting process statistics.

Severity: INFO
Message: Removing file copy %s.

Severity: INFO
Message: Skipping backup of %s log (file not found).

Severity: INFO
Message: Collecting JVM heap dump : using %s.

Severity: INFO
Message: Collecting the log files.

Severity: INFO
Message: Collecting backend statistics.

Severity: INFO
Message: Collecting the GC log files.

Severity: INFO
Message: Skipping GC logs collection because GC logging is not enabled.

Severity: INFO
Message: Collecting ChangelogDb information.

Severity: INFO
Message: No changelogDb data found (is a DS or is not replicated).

Severity: INFO
Message: Collecting the monitoring info from cn=monitor.

Severity: INFO
Message: Collecting process thread information, sample number : %d.

Severity: INFO
Message: Generating stack dump, sample number : %d using %s for pid %d.

Severity: INFO
Message: Processor information.

Severity: INFO
Message: OS information.

Severity: INFO
Message: Extract environment variables.

Severity: INFO
Message: DS /proc files.

Severity: INFO
Message: VM environment information.

Severity: INFO
Message: Disk information.

Severity: INFO
Message: Network information.

Severity: INFO
Message: Linux release.

Severity: INFO
Message: Linux /proc info files.

Severity: INFO
Message: Collecting system node information.

Severity: INFO
Message: Listing the security stores.

Severity: INFO
Message: Adding %s.

Severity: INFO
Message: Skipping %s.

Severity: INFO
Message: Skipping java security stores.

Severity: INFO
Message: Skipping audit files.

Severity: ERROR
Message: There was at least one error during the tasks execution: %s.

Severity: INFO
Message: No value was provided for %s, JDK tool directory is set to %s.

Severity: INFO
Message: Cannot extract process statistics (by running "top" command) on OS '%s'. Only %s dump samples will be collected.

Severity: INFO
Message: This tool manages data synchronization between servers. For replication to work you must initialize the contents of one of the servers with the contents of the others using the '%s' subcommand.

Severity: NOTICE
Message: Manages data synchronization between servers.

Severity: ERROR
Message: An unexpected error has been raised during execution of the tool: '%s'.

Severity: INFO
Message: Initialize replication data for the server.

Severity: INFO
Message: Starting initialization from '%s' to '%s' for base DNs: %s.

Severity: INFO
Message: Starting initialization from '%s' to all replicas for base DNs: %s.

Severity: INFO
Message: Starting initialization for base DN: '%s'.

Severity: NOTICE
Message: An error occurred when launching initialization: %s.

Severity: INFO
Message: Base DN(s) to use. Multiple base DNs can be provided by using this option multiple times.

Severity: INFO
Message: Server ID of the server containing the source data.

Severity: INFO
Message: {serverSource}.

Severity: INFO
Message: Server ID of the server to be initialized.

Severity: INFO
Message: {serverToInitialize}.

Severity: INFO
Message: Initialize all the other servers in the topology.

Severity: NOTICE
Message: A mandatory argument is missing. Choose one and only one argument from '--toServer', '--fromServer' and '--toAllServers'.

Severity: NOTICE
Message: Invalid combination of arguments. Choose one and only one argument from '--toServer', '--fromServer' and '--toAllServers'.

Severity: NOTICE
Message: An error occurred during initialization. Last log details: %s. Task state: %s.

Severity: NOTICE
Message: An error occurred during initialization. Task state: %s.

Severity: NOTICE
Message: Error during the processing of the reset generationID task. Last log details: %s. Task state: %s.

Severity: NOTICE
Message: Error during the processing of the reset generationID task. Task state: %s.

Severity: INFO
Message: Cannot extract the master key pair certificate with alias '%s' because the crypto-manager’s key manager provider of the local server does not contain such key or does not support extracting certificates.

Severity: INFO
Message: Cannot find a CA certificate in the replication trust managers of the local server. Please verify the %s trust-manager-provider configuration value.

Severity: INFO
Message: Base DN(s) to replicate.

Severity: ERROR
Message: Inappropriate server ID '%s' for the local server: it does not represent a numeric value as required to communicate with pre 7.0 servers. Use an integer server ID without leading zeros.

Severity: ERROR
Message: Inappropriate group ID '%s' for the local server: it cannot be converted to an integer, but this is required to communicate with pre 7.0 servers. Use a group ID that can be converted into an integer, or use 'default' if you do not want to set a group ID.

Severity: ERROR
Message: Cannot use server ID '%s' for the local server because it is already used by server '%s' (configuration object %s).

Severity: ERROR
Message: Cannot read the configuration of the local server. The error was: %s.

Severity: ERROR
Message: Cannot read 'cn=admin data' in server '%s'. The error was: %s.

Severity: ERROR
Message: Error when reading the server IDs from all the servers in the old topology. The error was: %s.

Severity: ERROR
Message: Cannot discover the configuration of the local server. The error was: %s.

Severity: ERROR
Message: Cannot add an entry describing the new server to 'cn=admin data' in the remote server '%s' in the existing topology. The error was: %s.

Severity: ERROR
Message: Cannot add '%s' to the bootstrap replication server list on server '%s'. The error was: %s.

Severity: ERROR
Message: Cannot add '%s' to the configuration of replication server on server '%s'. The error was: %s.

Severity: ERROR
Message: Cannot add '%s' to the configuration of replication domain '%s' on server '%s'. The error was: %s.

Severity: ERROR
Message: Cannot retrieve the replication port from server '%s'. The error was: %s.

Severity: ERROR
Message: Cannot configure the local server so it can replicate with the servers in the existing topology. The error was: %s.

Severity: ERROR
Message: Cannot read server ID from server '%s' on DNs '%s' and '%s'. The errors were: %s.

Severity: ERROR
Message: Cannot determine server ID for server '%s' on DNs '%s' and '%s'.

Severity: ERROR
Message: Cannot obtain a connection to server '%s' from the existing topology. The error was: %s.

Severity: ERROR
Message: Cannot obtain a connection for one of the servers in the existing topology. The error was: %s.

Severity: ERROR
Message: Cannot configure all the servers in the existing topology to replicate with the new server. The error was: %s.

Severity: ERROR
Message: An error occurred opening (or closing) a connection to change the configuration of the local server. The error was: %s.

Severity: ERROR
Message: An error occurred opening connections to the server in the existing topology or the new server. The error was: %s.

Severity: ERROR
Message: Once done, restart the server for the changes to take effect.

Severity: ERROR
Message: Cannot read the server ID or the group ID for the local server. The error(s) are: %s.

Severity: ERROR
Message: Cannot add the entry '%s' to the server '%s'. The error was: %s.

Severity: ERROR
Message: Cannot read the entry '%s' on server '%s'. The error was: %s.

Severity: ERROR
Message: Cannot modify the entry '%s' on server '%s' to reconcile it with what is expected by the tool. The error was: %s.

Severity: INFO
Message: Adding server instances keys from the existing topology into 'cn=admin data' in the new server.

Severity: ERROR
Message: Cannot add server instance keys to the new server. The error was: %s.

Severity: INFO
Message: Enabling 'cn=admin data' backend.

Severity: INFO
Message: Creating the trust manager '%s' to be used by replication connections in the local server.

Severity: INFO
Message: Updating replication configuration on local server.

Severity: INFO
Message: Updating replication configuration for baseDN '%s' on local server.

Severity: INFO
Message: Configuring the servers in the topology to talk to the local server.

Severity: INFO
Message: Replication has been successfully configured on the local server. Note that for replication to work you must initialize the contents of the base DNs that are being replicated. Run the following command(s) to do so:.

Severity: INFO
Message: Start disaster recovery for all servers. Read the documentation on disaster recovery carefully before using this command.

Severity: INFO
Message: End disaster recovery for all servers. Read the documentation on disaster recovery carefully before using this command.

Severity: NOTICE
Message: An error occurred while attempting to monitor the task progress. The error was: %s.

Severity: NOTICE
Message: An error occurred when starting disaster recovery: %s.

Severity: INFO
Message: Starting disaster recovery for server '%s' for base DNs: %s.

Severity: INFO
Message: Starting disaster recovery for base DN: '%s'.

Severity: NOTICE
Message: An error occurred during start of disaster recovery. Last log details: %s. Task state: %s.

Severity: NOTICE
Message: An error occurred during start of disaster recovery. Task state: %s.

Severity: INFO
Message: Replication is now suspended and the replicated servers will reject any modifications. Now initialize the contents of the base DNs on all of the servers by importing LDIF or by restoring a backup. The same LDIF or backup must be used on each server. When the initialization has completed you must use the 'end-disaster-recovery' subcommand to resume replication for the base DNs.

Severity: NOTICE
Message: An error occurred when ending disaster recovery: %s.

Severity: INFO
Message: Ending disaster recovery for server '%s' for base DNs: %s.

Severity: INFO
Message: Ending disaster recovery for base DN '%s'.

Severity: NOTICE
Message: An error occurred during end of disaster recovery. Last log details: %s. Task state: %s.

Severity: NOTICE
Message: An error occurred during end of disaster recovery. Task state: %s.

Severity: INFO
Message: Replication has now resumed for the base DNs and directory servers will accept modifications.

Severity: INFO
Message: Check the server error logs for additional details.

Severity: INFO
Message: Purges old replication meta-data from application data.

Severity: INFO
Message: Maximum duration of the command in seconds.

Severity: INFO
Message: {maximum duration in seconds}.

Severity: INFO
Message: Purging old replication meta-data for server '%s' for base DNs: %s.

Severity: NOTICE
Message: An error occurred while purging old replication meta-data: %s.

Severity: NOTICE
Message: An error occurred while purging old replication meta-data. Last log details: %s. Task state: %s.

Severity: NOTICE
Message: An error occurred while purging old replication meta-data. Task state: %s.

Severity: INFO
Message: Re-synchronizes the change-log change number of the target server with the change-log change number of the source server.

Severity: INFO
Message: The change number to use as the basis for re-synchronization.

Severity: INFO
Message: {change number}.

Severity: INFO
Message: Start to re-synchronize the change-log change number of server '%s' from the source server '%s'.

Severity: INFO
Message: Re-synchronizing with change number '%s'.

Severity: INFO
Message: Change number corresponds to start CSN '%s' and base DN '%s'.

Severity: NOTICE
Message: Error when searching change number '%s' in the source server: %s.

Severity: NOTICE
Message: Unable to retrieve change number '%s' in the source server.

Severity: NOTICE
Message: No CSN found for the change number '%s' in the source server.

Severity: NOTICE
Message: No base DN found for the change number '%s' in the source server.

Severity: NOTICE
Message: Unable to retrieve the newest change number in the source server.

Severity: NOTICE
Message: An error occurred when re-synchronizing the change number: %s.

Severity: NOTICE
Message: An error occurred during the re-synchronization of the change number. Last log details: %s. Task state: %s.

Severity: NOTICE
Message: An error occurred during the re-synchronization of the change number. Task state: %s.

Severity: NOTICE
Message: The source and target server have distinct replication domains. As a consequence the change number from the target server can’t be reset from a change number of the source server.

Severity: NOTICE
Message: Unable to find a replicated domain in the target server.

Severity: NOTICE
Message: Unable to find a replicated domain matching the DN '%s' corresponding to the change number.

Severity: NOTICE
Message: An error occurred when searching replicated domains in server. Result code was: '%s'.

Severity: NOTICE
Message: An error occurred when searching replicated domains in server: %s.

Severity: INFO
Message: Displays the status of the replication service and various diagnostics about it. The information is derived from reading cn=monitor on all the servers in the replication topology. The status of a server is one of the following. BAD - DATA MISMATCH: either the fractional replication configuration does not match the backend data, or the initial state of the replicated data does not match other servers and this server must be re-initialized; BAD - TOO LATE: the server has fallen further behind than the replication purge delay and must be re-initialized; GOOD: normal operation, nothing to do; SLOW: the server’s replay delay is greater than five seconds; UNHEALTHY: read the server health errors in the server monitoring data for details.

Severity: INFO
Message: Base DN.

Severity: INFO
Message: Base DN / DS.

Severity: INFO
Message: Base DN / RS.

Severity: INFO
Message: Base DN / RS / DS.

Severity: INFO
Message: Status.

Severity: INFO
Message: Group.

Severity: INFO
Message: Receive delay (ms).

Severity: INFO
Message: Replay delay (ms).

Severity: INFO
Message: Entry count.

Severity: INFO
Message: Server / host port.

Severity: INFO
Message: Error or diagnostic.

Severity: INFO
Message: Displays individual replicas in the output.

Severity: INFO
Message: Displays individual changelog servers in the output.

Severity: INFO
Message: Display replication group information in the output.

Severity: ERROR
Message: An error occurred while reading cn=monitor on server %s: %s.

Severity: ERROR
Message: Error while reading cn=monitor: %s.

Severity: ERROR
Message: Cannot contact server: no admin port could be discovered in its entry %s.

Severity: ERROR
Message: Server is not healthy: %s.

Severity: ERROR
Message: General error: %s.

Severity: INFO
Message: Base DN(s) to display. Multiple base DNs can be provided by using this option multiple times. If no base DNs are provided, then all the base DNs will be displayed.

Severity: INFO
Message: Clears all replication server changelog data for the offline local server; the other replication servers in the topology will transfer any needed data when the server restarts.

Severity: ERROR
Message: A problem occurred while clearing the changelog data: %s.

Severity: INFO
Message: Clearing all replication server changelog data for the local server.

Severity: INFO
Message: Nothing to do: this server does not keep any replication server changelog data.

Severity: ERROR
Message: Cannot obtain a connection for one of the servers in the topology. The error was: %s.

Severity: ERROR
Message: Cannot obtain a connection to server '%s' from the topology. The error was: %s.

Severity: ERROR
Message: An error occurred opening (or closing) a connection to read or change the configuration of the local server. The error was: %s.

Severity: INFO
Message: This server has already been cleaned, there is nothing left to do.

Severity: INFO
Message: The remaining cleanup on this server cannot be performed because the administrator user '%s' in the admin backend was used to bind to the server. You should run again this command using a bind DN, such as "uid=admin", which lies outside the "cn=admin data" backend to be able to complete the cleanup on this server.

Severity: ERROR
Message: Cannot disable admin backend on the local server. The error was: %s.

Severity: ERROR
Message: Cannot update configuration for server '%s'. The error was: %s.

Severity: ERROR
Message: Cannot read monitor entries under '%s' on the local server. The error was: %s.

Severity: ERROR
Message: Cannot delete entries under '%s' in admin backend. The error was: %s.

Severity: INFO
Message: All servers have been cleaned.

Severity: INFO
Message: All servers have been cleaned. The admin backend will remain enabled because it contains secret keys that may be used by reversible password storage schemes.

Severity: INFO
Message: The server %s has now been cleaned.

Severity: INFO
Message: Servers have been cleaned, however the administrator user '%s' in the admin backend was not removed because it was used to bind to the server. To remove it, you should run the following commands on all servers using a bind DN, such as "uid=admin", which lies outside the "cn=admin data" backend:.

Severity: INFO
Message: Removing servers from admin backend.

Severity: INFO
Message: Removing instance keys from admin backend.

Severity: INFO
Message: Removing administrators from admin backend.

Severity: INFO
Message: Cleaning and updating configuration of server %s.

Severity: INFO
Message: Set bootstrap servers configuration for server %s.

Severity: INFO
Message: Disable admin backend for server %s.

Severity: WARNING
Message: Some reversible password storage schemes are enabled in the configuration, note that it won’t be possible to use them in password policies since the admin data backend has been disabled.

Severity: INFO
Message: Clean all the servers (with version 7.0 or more) that have been migrated from a topology of older servers (version prior to 7.0).

Severity: ERROR
Message: An attempt was made to configure the root DSE backend without providing a configuration entry. This is not allowed.

Severity: WARNING
Message: Base DN "%s" is configured as one of the subordinate base DNs to use for searches below the root DSE. However, this base DN is not handled by any suffix registered with the Directory Server and will therefore not be used.

Severity: ERROR
Message: Unwilling to update entry "%s" because modify operations are not supported in the root DSE backend. If you wish to alter the contents of the root DSE itself, then it may be possible to do so by modifying the "%s" entry in the configuration.

Severity: ERROR
Message: Unwilling to perform a search (connection ID %d, operation ID %d) with a base DN of "%s" in the root DSE backend. The base DN for searches in this backend must be the DN of the root DSE itself.

Severity: ERROR
Message: Unable to process the search with connection ID %d and operation ID %d because it had an invalid scope of %s.

Severity: ERROR
Message: An unexpected error occurred while trying to open the LDIF writer for the root DSE backend: %s.

Severity: ERROR
Message: An unexpected error occurred while trying to export the root DSE entry to the specified LDIF target: %s.

Severity: INFO
Message: The root DSE configuration has been updated so that it will now use a new set of user-defined attributes.

Severity: ERROR
Message: An attempt was made to configure the monitor backend without providing a configuration entry. This is not allowed, and no monitor information will be available over protocol.

Severity: ERROR
Message: Unwilling to add entry "%s" because add operations are not supported in the "%s" backend.

Severity: ERROR
Message: Unwilling to remove entry "%s" because delete operations are not supported in the "%s" backend.

Severity: ERROR
Message: Unwilling to update entry "%s" because modify operations are not supported in the monitor backend. If you wish to alter the contents of the base monitor entry itself, then it may be possible to do so by modifying the "%s" entry in the configuration.

Severity: ERROR
Message: Unwilling to rename entry "%s" because modify DN operations are not supported in the "%s" backend.

Severity: ERROR
Message: An error occurred while attempting to export the base monitor entry: %s.

Severity: ERROR
Message: An error occurred while attempting to export the monitor entry for monitor provider %s: %s.

Severity: ERROR
Message: The "%s" backend does not support LDIF import operations.

Severity: INFO
Message: The monitor configuration has been updated so that it will now use a new set of user-defined attributes.

Severity: ERROR
Message: Unable to retrieve the requested entry from the "%s" backend because the provided DN was null.

Severity: ERROR
Message: Unable to retrieve the requested entry %s from the monitor backend because the DN is not below the monitor base of %s.

Severity: ERROR
Message: An attempt was made to configure the schema backend without providing a configuration entry. This is not allowed, and no schema information will be available over protocol.

Severity: ERROR
Message: An error occurred while attempting to export the base schema entry: %s.

Severity: ERROR
Message: Unable to retrieve the requested entry %s from the schema backend because the DN is equal to one of the schema entry DNs.

Severity: ERROR
Message: An unexpected error occurred while trying to open the LDIF writer for the schema backend: %s.

Severity: INFO
Message: The schema configuration has been updated so that it will now use a new set of user-defined attributes.

Severity: ERROR
Message: The Directory Server was unable to obtain a lock on entry %s after multiple attempts. This could mean that the entry is already locked by a long-running operation or that the entry has previously been locked but was not properly unlocked.

Severity: ERROR
Message: The task defined in entry %s is invalid because it has an invalid state %s.

Severity: ERROR
Message: An error occurred while trying to parse the scheduled start time value %s from task entry %s.

Severity: ERROR
Message: An error occurred while trying to parse the actual start time value %s from task entry %s.

Severity: ERROR
Message: An error occurred while trying to parse the completion time value %s from task entry %s.

Severity: ERROR
Message: Task entry %s is missing required attribute %s.

Severity: ERROR
Message: There are multiple instances of attribute %s in task entry %s.

Severity: ERROR
Message: There are multiple values for attribute %s in task entry %s.

Severity: ERROR
Message: An error occurred while executing the task defined in entry %s: %s.

Severity: ERROR
Message: The provided recurring task entry does not contain attribute %s which is needed to hold the recurring task ID.

Severity: ERROR
Message: The provided recurring task entry contains multiple attributes with type %s, which is used to hold the recurring task ID, but only a single instance is allowed.

Severity: ERROR
Message: The provided recurring task entry does not contain any values for the %s attribute, which is used to specify the recurring task ID.

Severity: ERROR
Message: The provided recurring task entry contains multiple values for the %s attribute, which is used to specify the recurring task ID, but only a single value is allowed.

Severity: ERROR
Message: The provided recurring task entry does not contain attribute %s which is needed to specify recurring task schedule.

Severity: ERROR
Message: The provided recurring task entry contains multiple attributes with type %s, which is used to hold recurring task schedule, but only a single instance is allowed.

Severity: ERROR
Message: The provided recurring task entry does not contain any values for the %s attribute, which is used to specify recurring task schedule.

Severity: ERROR
Message: The provided recurring task entry contains multiple values for the %s attribute, which is used to specify recurring task schedule, but only a single value is allowed.

Severity: ERROR
Message: An error occurred while attempting to load class %s specified in attribute %s of the provided recurring task entry: %s. Does this class exist in the Directory Server classpath?.

Severity: ERROR
Message: An error occurred while trying to create an instance of class %s as a Directory Server task. Is this class a subclass of %s?.

Severity: ERROR
Message: An error occurred while attempting to perform internal initialization on an instance of class %s with the information contained in the provided entry: %s.

Severity: ERROR
Message: The specified task data backing file %s already exists and the Directory Server will not attempt to overwrite it. Please delete or rename the existing file before attempting to use that path for the new backing file, or choose a new path.

Severity: ERROR
Message: The specified path %s for the new task data backing file appears to be an invalid path. Please choose a new path for the task data backing file.

Severity: ERROR
Message: The parent directory %s for the new task data backing file %s does not exist. Please create this directory before attempting to use this path for the new backing file or choose a new path.

Severity: ERROR
Message: The parent directory %s for the new task data backing file %s exists but is not a directory. Please choose a new path for the task data backing file.

Severity: ERROR
Message: An error occurred while attempting to determine the new path to the task data backing file: %s.

Severity: INFO
Message: The completed task retention time has been updated to %d seconds. This will take effect immediately.

Severity: INFO
Message: The path to the task data backing file has been changed to %s. A snapshot of the current task configuration has been written to that file and it will continue to be used for future updates.

Severity: ERROR
Message: New entries in the task backend may only be added immediately below %s for scheduled tasks or immediately below %s for recurring tasks.

Severity: INFO
Message: This file contains the data used by the Directory Server task scheduler backend. Do not edit this file directly, as there is a risk that those changes will be lost. Scheduled and recurring task definitions should only be edited using the administration utilities provided with the Directory Server.

Severity: ERROR
Message: Unable to add recurring task %s to the task scheduler because another recurring task already exists with the same ID.

Severity: ERROR
Message: Unable to schedule task %s because another task already exists with the same ID.

Severity: WARNING
Message: Unable to add completed task %s to the task scheduler because another task already exists with the same ID.

Severity: ERROR
Message: An error occurred while attempting to schedule the next iteration of recurring task %s: %s.

Severity: ERROR
Message: An error occurred while attempting to read an entry from the tasks backing file %s on or near line %d: %s. This is not a fatal error, so the task scheduler will attempt to continue parsing the file and schedule any additional tasks that it contains.

Severity: ERROR
Message: An error occurred while attempting to read an entry from the tasks backing file %s on or near line %d: %s. This is an unrecoverable error, and parsing cannot continue.

Severity: ERROR
Message: Entry %s read from the tasks backing file is invalid because it has no parent and does not match the task root DN of %s.

Severity: ERROR
Message: An error occurred while attempting to parse entry %s as a recurring task and add it to the scheduler: %s.

Severity: ERROR
Message: An error occurred while attempting to parse entry %s as a task and add it to the scheduler: %s.

Severity: ERROR
Message: Entry %s read from the tasks backing file %s has a DN which is not valid for a task or recurring task definition and will be ignored.

Severity: ERROR
Message: An error occurred while attempting to read from the tasks data backing file %s: %s.

Severity: ERROR
Message: An error occurred while attempting to create a new tasks backing file %s for use with the task scheduler: %s.

Severity: ERROR
Message: The provided task entry does not contain attribute %s which is needed to specify the fully-qualified name of the class providing the task logic.

Severity: ERROR
Message: The provided task entry contains multiple attributes with type %s, which is used to hold the task class name, but only a single instance is allowed.

Severity: ERROR
Message: The provided task entry does not contain any values for the %s attribute, which is used to specify the fully-qualified name of the class providing the task logic.

Severity: ERROR
Message: The provided task entry contains multiple values for the %s attribute, which is used to specify the task class name, but only a single value is allowed.

Severity: ERROR
Message: An error occurred while attempting to load class %s specified in attribute %s of the provided task entry: %s. Does this class exist in the Directory Server classpath?.

Severity: ERROR
Message: An error occurred while trying to create an instance of class %s as a Directory Server task. Is this class a subclass of %s?.

Severity: ERROR
Message: An error occurred while attempting to perform internal initialization on an instance of class %s with the information contained in the provided entry: %s.

Severity: WARNING
Message: An error occurred while attempting to rename the current tasks backing file from %s to %s: %s. The previous task configuration (which does not reflect the latest update) may be lost.

Severity: ERROR
Message: An error occurred while attempting to rename the new tasks backing file from %s to %s: %s. If the Directory Server is restarted, then the task scheduler may not work as expected.

Severity: ERROR
Message: An error occurred while attempting to write the new tasks data backing file %s: %s. Configuration information reflecting the latest update may be lost.

Severity: INFO
Message: The tasks backend is being shut down.

Severity: INFO
Message: The root DSE configuration has been updated so that configuration attribute %s will now use a value of %s.

Severity: ERROR
Message: Unable to remove pending task %s because no such task exists.

Severity: ERROR
Message: Unable to remove pending task %s because the task is no longer pending.

Severity: ERROR
Message: Unable to remove completed task %s because no such task exists in the list of completed tasks.

Severity: ERROR
Message: Unable to remove entry %s from the task backend because its DN is either not appropriate for that backend or it is not below the scheduled or recurring tasks base entry.

Severity: ERROR
Message: Unable to remove entry %s from the task backend because there is no scheduled task associated with that entry DN.

Severity: ERROR
Message: Unable to delete entry %s from the task backend because the associated task is currently running.

Severity: ERROR
Message: Unable to remove entry %s from the task backend because there is no recurring task associated with that entry DN.

Severity: ERROR
Message: Unable to process the search operation in the task backend because the provided base DN %s is not valid for entries in the task backend.

Severity: ERROR
Message: Unable to process the search operation in the task backend because there is no scheduled task associated with the provided search base entry %s.

Severity: ERROR
Message: Unable to process the search operation in the task backend because there is no recurring task associated with the provided search base entry %s.

Severity: ERROR
Message: Unwilling to update entry "%s" because modify operations are not supported in the "%s" backend.

Severity: ERROR
Message: Exactly one base DN must be provided for use with the memory-based backend.

Severity: ERROR
Message: Entry %s already exists in the memory-based backend.

Severity: ERROR
Message: Entry %s does not belong in the memory-based backend.

Severity: ERROR
Message: Unable to add entry %s because its parent entry %s does not exist in the memory-based backend.

Severity: ERROR
Message: Entry %s does not exist in the "%s" backend.

Severity: ERROR
Message: Cannot delete entry %s because it has one or more subordinate entries.

Severity: ERROR
Message: Unable to create an LDIF writer: %s.

Severity: ERROR
Message: Cannot write entry %s to LDIF: %s.

Severity: ERROR
Message: Unable to create an LDIF reader: %s.

Severity: ERROR
Message: An unrecoverable error occurred while reading from LDIF: %s.

Severity: ERROR
Message: An unexpected error occurred while processing the import: %s.

Severity: ERROR
Message: Cannot rename entry %s because it has one or more subordinate entries.

Severity: ERROR
Message: Cannot rename entry %s because the target entry is in a different backend.

Severity: ERROR
Message: Cannot rename entry %s because the new parent entry %s doesn’t exist.

Severity: ERROR
Message: An error occurred while attempting to register the base DNs %s in the Directory Server: %s.

Severity: ERROR
Message: The schema backend does not support the %s modification type.

Severity: ERROR
Message: The schema backend does not support the modification of the %s attribute type. Only attribute types, object classes, ldap syntaxes, name forms, DIT content rules, DIT structure rules, and matching rule uses may be modified.

Severity: ERROR
Message: An error occurred while attempting to write the updated schema: %s.

Severity: ERROR
Message: The server will not allow removing all values for the %s attribute type in the server schema.

Severity: ERROR
Message: Circular reference detected for attribute type %s in which the superior type chain references the attribute type itself.

Severity: ERROR
Message: Circular reference detected for objectclass %s in which the superior class chain references the objectclass itself.

Severity: ERROR
Message: Circular reference detected for DIT structure rule %s in which the superior rule chain references the DIT structure rule itself.

Severity: ERROR
Message: An error occurred while attempting to create copies of the existing schema files before applying the updates: %s. The server was able to restore the original schema configuration, so no additional cleanup should be required.

Severity: ERROR
Message: An error occurred while attempting to create copies of the existing schema files before applying the updates: %s. A problem also occurred when attempting to restore the original schema configuration, so the server may be left in an inconsistent state and could require manual cleanup.

Severity: ERROR
Message: An error occurred while attempting to write new versions of the server schema files: %s. The server was able to restore the original schema configuration, so no additional cleanup should be required.

Severity: ERROR
Message: An error occurred while attempting to write new versions of the server schema files: %s. A problem also occurred when attempting to restore the original schema configuration, so the server may be left in an inconsistent state and could require manual cleanup.

Severity: ERROR
Message: Unable to remove attribute type %s from the server schema because no such attribute type is defined.

Severity: ERROR
Message: Unable to remove objectclass %s from the server schema because no such objectclass is defined.

Severity: ERROR
Message: Unable to remove name form %s from the server schema because no such name form is defined.

Severity: ERROR
Message: Unable to remove DIT content rule %s from the server schema because no such DIT content rule is defined.

Severity: ERROR
Message: Unable to remove DIT structure rule %s from the server schema because no such DIT structure rule is defined.

Severity: ERROR
Message: Unable to remove matching rule use %s from the server schema because no such matching rule use is defined.

Severity: ERROR
Message: You do not have sufficient privileges to modify the Directory Server schema.

Severity: ERROR
Message: Unable to find a file containing concatenated schema element definitions in order to determine if any schema changes were made with the server offline. The file was expected in the %s directory and should have been named either %s or %s.

Severity: ERROR
Message: An error occurred while attempting to determine whether any schema changes had been made by directly editing the schema files with the server offline: %s.

Severity: ERROR
Message: An error occurred while attempting to write file %s containing a concatenated list of all server schema elements: %s. The server may not be able to accurately identify any schema changes made with the server offline.

Severity: ERROR
Message: The Directory Server is not configured to allow task %s to be invoked.

Severity: ERROR
Message: Indexes are not supported in the "%s" backend.

Severity: ERROR
Message: LDIF import and export operations are not supported in the "%s" backend.

Severity: ERROR
Message: The root container for backend %s has not been initialized preventing this backend from processing the requested operation.

Severity: ERROR
Message: Entry %s cannot be modified because it does not represent a task entry. Only task entries may be modified in the task backend.

Severity: ERROR
Message: Entry %s cannot be modified because it does not represent a valid task in the server.

Severity: ERROR
Message: Entry %s cannot be modified because the associated task has completed running. Completed tasks cannot be modified.

Severity: ERROR
Message: Entry %s cannot be modified because the server does not currently support modifying recurring task entries.

Severity: ERROR
Message: The task associated with entry %s is currently running. The only modification allowed for running tasks is to replace the value of the ds-task-state attribute with "cancel".

Severity: INFO
Message: Task processing was interrupted by a modify request to cancel the task.

Severity: ERROR
Message: The LDIF backend defined in configuration entry %s only supports a single base DN, but was configured for use with multiple base DNs.

Severity: ERROR
Message: LDIF file %s configured for use with the LDIF backend defined in configuration entry %s has multiple entries with a DN of %s.

Severity: ERROR
Message: LDIF file %s configured for use with the LDIF backend defined in configuration entry %s includes entry %s which is not below the base DN defined for that backend.

Severity: ERROR
Message: LDIF file %s configured for use with the LDIF backend defined in configuration entry %s contains entry %s but its parent entry has not yet been read.

Severity: ERROR
Message: An error occurred while trying to create file %s to write an updated version of the data for the LDIF backend defined in configuration entry %s: %s.

Severity: ERROR
Message: An error occurred while trying to write updated data to file %s for the LDIF backend defined in configuration entry %s: %s.

Severity: ERROR
Message: An error occurred while attempting to rename file %s to %s while writing updated data for the LDIF backend defined in configuration entry %s: %s.

Severity: ERROR
Message: Entry %s already exists in the LDIF backend.

Severity: ERROR
Message: The parent for entry %s does not exist.

Severity: ERROR
Message: Entry %s does not exist.

Severity: ERROR
Message: Entry %s has one or more subordinate entries and cannot be deleted until all of its subordinate entries are removed first.

Severity: ERROR
Message: Entry %s does not exist.

Severity: ERROR
Message: Source entry %s does not exist.

Severity: ERROR
Message: Target entry %s already exists.

Severity: ERROR
Message: The new parent DN %s does not exist.

Severity: ERROR
Message: Entry %s specified as the search base DN does not exist.

Severity: ERROR
Message: An error occurred while trying to create the writer for the LDIF export operation: %s.

Severity: ERROR
Message: An error occurred while trying to write entry %s during the LDIF export: %s.

Severity: ERROR
Message: An error occurred while trying to create the reader for the LDIF import operation: %s.

Severity: ERROR
Message: An unrecoverable error occurred while attempting to read data from the import file: %s. The LDIF import cannot continue.

Severity: INFO
Message: The change to the LDIF file path will not take effect until the backend is disabled and re-enabled.

Severity: INFO
Message: The change to the LDIF backend base DN will not take effect until the backend is disabled and re-enabled.

Severity: ERROR
Message: The target entry %s does not exist.

Severity: ERROR
Message: The target entry %s does not exist.

Severity: ERROR
Message: This backend does not provide support for the numSubordinates operational attribute.

Severity: NOTICE
Message: The backend %s is now taken offline.

Severity: ERROR
Message: The provided recurring task entry attribute %s holding the recurring task schedule has invalid number of tokens.

Severity: ERROR
Message: The provided recurring task entry attribute %s holding the recurring task schedule has invalid minute token.

Severity: ERROR
Message: The provided recurring task entry attribute %s holding the recurring task schedule has invalid hour token.

Severity: ERROR
Message: The provided recurring task entry attribute %s holding the recurring task schedule has invalid day of the month token.

Severity: ERROR
Message: The provided recurring task entry attribute %s holding the recurring task schedule has invalid month of the year token.

Severity: ERROR
Message: The provided recurring task entry attribute %s holding the recurring task schedule has invalid day of the week token.

Severity: ERROR
Message: The provided recurring task entry attribute %s holding the recurring task schedule has invalid tokens combination yielding a nonexistent calendar date.

Severity: ERROR
Message: An error occurred while attempting to export task backend data: %s.

Severity: INFO
Message: JE backend '%s' does not specify the number of cleaner threads: defaulting to %d threads.

Severity: INFO
Message: JE backend '%s' does not specify the number of lock tables: defaulting to %d.

Severity: ERROR
Message: Unable to schedule task %s because its dependency task %s is missing.

Severity: NOTICE
Message: %s task %s started execution.

Severity: NOTICE
Message: %s task %s finished execution in the state %s.

Severity: ERROR
Message: Unable to remove ldap syntax description %s from the server schema because no such ldap syntax description is defined.

Severity: ERROR
Message: An error occurred while attempting to decode the ldapsyntax description "%s": %s.

Severity: ERROR
Message: The provided recurring task schedule value has an invalid number of tokens.

Severity: ERROR
Message: The provided recurring task schedule value has an invalid minute token.

Severity: ERROR
Message: The provided recurring task schedule value has an invalid hour token.

Severity: ERROR
Message: The provided recurring task schedule value has an invalid day of the month token.

Severity: ERROR
Message: The provided recurring task schedule value has an invalid month of the year token.

Severity: ERROR
Message: The provided recurring task schedule value has an invalid day of the week token.

Severity: ERROR
Message: The schema backend does not support the Replace modification type for the %s attribute type.

Severity: ERROR
Message: An error occurred while trying to close file %s for the LDIF backend defined in configuration entry %s: %s.

Severity: ERROR
Message: The file %s written for the LDIF backend defined in configuration entry %s is 0 bytes long and unusable.

Severity: ERROR
Message: Configuration attribute ds-cfg-db-cache-size has a value of %d but the JVM has only %d available. Consider using ds-cfg-db-cache-percent.

Severity: ERROR
Message: Configuration attribute ds-cfg-db-cache-percent has a value of %d%% but the JVM has only %d%% available.

Severity: ERROR
Message: Unable to process the virtual list view request because the target assertion could not be decoded as a valid value for the '%s' attribute type.

Severity: WARNING
Message: Disk free space of %d bytes for directory %s is now below low threshold of %d bytes. Backend %s is now locked down and will no longer accept any operations from clients until sufficient disk space is restored.

Severity: WARNING
Message: Disk free space of %d bytes for directory %s is now below disk low threshold of %d bytes. Backend %s is now offline and will no longer accept any operations until sufficient disk space is restored.

Severity: ERROR
Message: An error occurred while trying to list the files to backup for backend '%s': %s.

Severity: ERROR
Message: Insufficient free memory (%d bytes) to perform import. At least %d bytes of free memory is required.

Severity: ERROR
Message: Index for attribute '%s' cannot be created for matching rule '%s' because it cannot be found in the schema. Fix the matching rule name in the config or add the matching rule to the schema.

Severity: ERROR
Message: Unable to process the virtual list view request because the target start position was before the beginning of the result set.

Severity: ERROR
Message: The entry database does not contain a record for ID %s.

Severity: ERROR
Message: Execution error during backend operation: %s.

Severity: ERROR
Message: The backend database directory could not be created: %s.

Severity: WARNING
Message: This platform does not support setting file permissions %s to the database directory %s.

Severity: WARNING
Message: An error occurred while setting file permissions for the backend database directory %s: %s.

Severity: NOTICE
Message: The change to the DB directory will not take effect until the backend is restarted. The DB files from the previous directory %s must be moved to the new directory %s after shutting down the backend to retain the existing data.

Severity: ERROR
Message: The backend database directory '%s' is not a valid directory.

Severity: ERROR
Message: The entry '%s' cannot be added because an entry with that name already exists.

Severity: ERROR
Message: The entry '%s' cannot be added because its parent entry does not exist.

Severity: ERROR
Message: There is no index configured for attribute type '%s'.

Severity: ERROR
Message: An error occurred while attempting to decode an attribute description token from the compressed schema definitions: %s.

Severity: ERROR
Message: An error occurred while attempting to decode an object class set token from the compressed schema definitions: %s.

Severity: ERROR
Message: An error occurred while attempting to store compressed schema information in the database: %s.

Severity: ERROR
Message: An error occurred while parsing the search filter %s defined for VLV index %s: %s.

Severity: ERROR
Message: Sort attribute %s for VLV index %s is not defined in the server schema.

Severity: ERROR
Message: Database exception: %s.

Severity: ERROR
Message: A plugin caused the delete operation to be aborted while deleting a subordinate entry %s.

Severity: ERROR
Message: The entry '%s' cannot be removed because it has subordinate entries.

Severity: ERROR
Message: The entry '%s' cannot be removed because it does not exist.

Severity: ERROR
Message: An entry container named '%s' is alreadly registered for base DN '%s'.

Severity: ERROR
Message: The entry database does not contain a valid record for ID %s.

Severity: ERROR
Message: I/O error occurred while exporting entry: %s.

Severity: ERROR
Message: The backend must be disabled before the import process can start.

Severity: ERROR
Message: Unable to create the temporary directory %s.

Severity: ERROR
Message: The import has been aborted because the entry '%s' does not have a parent entry.

Severity: ERROR
Message: Entry record is not compatible with this version of the backend database. Entry version: %x.

Severity: ERROR
Message: An error occurred while reading from index %s. The index seems to be corrupt and is now operating in a degraded state. The index must be rebuilt before it can return to normal operation.

Severity: ERROR
Message: The following paged results control cookie value was not recognized: %s.

Severity: ERROR
Message: A plugin caused the modify DN operation to be aborted while moving and/or renaming an entry from %s to %s.

Severity: ERROR
Message: The entry cannot be renamed to '%s' because an entry with that name already exists.

Severity: ERROR
Message: The entry '%s' cannot be renamed because it does not exist.

Severity: ERROR
Message: The entry '%s' cannot be modified because it does not exist.

Severity: ERROR
Message: The entry cannot be moved because the new parent entry '%s' does not exist.

Severity: ERROR
Message: The database environment could not be opened: %s.

Severity: ERROR
Message: Rebuilding system index(es) must be done with the backend containing the base DN disabled.

Severity: ERROR
Message: The backend database files could not be removed: %s.

Severity: ERROR
Message: The requested search operation included both the simple paged results control and the virtual list view control. These controls are mutually exclusive and cannot be used together.

Severity: ERROR
Message: The search results cannot be sorted because the given search request is not indexed.

Severity: ERROR
Message: The search base entry '%s' does not exist.

Severity: ERROR
Message: You do not have sufficient privileges to perform an unindexed search.

Severity: ERROR
Message: Unchecked exception during database transaction: %s.

Severity: ERROR
Message: There is no VLV index configured with name '%s'.

Severity: INFO
Message: The filter value exceeded the index entry limit for the %s index.

Severity: INFO
Message: %s index is invalid and needs to be rebuilt.

Severity: INFO
Message: %s index type is disabled for the %s attribute.

Severity: INFO
Message: Average number of entries referenced is %.2f/record.

Severity: INFO
Message: Free memory = %d MB, Cache miss rate = %.1f/record.

Severity: INFO
Message: Number of records that exceed the entry limit: %d.

Severity: INFO
Message: Statistics for records that have exceeded the entry limit:.

Severity: INFO
Message: File %s has %d such record(s) min=%d max=%d median=%d.

Severity: INFO
Message: Maximum number of entries referenced by any record is %d.

Severity: INFO
Message: Number of records referencing more than one entry: %d.

Severity: NOTICE
Message: The database backend %s containing %d entries has started.

Severity: NOTICE
Message: Some index keys have already exceeded the previous index entry limit in index %s. This index must be rebuilt before it can use the new limit.

Severity: NOTICE
Message: Exported %d entries and skipped %d in %d seconds (average rate %.1f/sec).

Severity: NOTICE
Message: Exported %d records and skipped %d (recent rate %.1f/sec).

Severity: NOTICE
Message: Flushing data to disk.

Severity: NOTICE
Message: Processed %d entries, imported %d, skipped %d and rejected %d in %d seconds (average rate %.1f/sec).

Severity: NOTICE
Message: Setting DB cache size to %d bytes and phase one buffer size to %d bytes.

Severity: NOTICE
Message: Index %s phase two processing completed.

Severity: NOTICE
Message: Index %s phase two started processing %d buffers in %d batches.

Severity: NOTICE
Message: Index %s %d%% complete: remaining = %d KB, rate = %d KB/s; batch %d/%d.

Severity: NOTICE
Message: Import LDIF environment close took %d seconds.

Severity: NOTICE
Message: The amount of free memory available to the import task is %d bytes. The number of phase one buffers required is %d buffers.

Severity: NOTICE
Message: Total import time was %d seconds. Phase one processing completed in %d seconds, phase two processing completed in %d seconds.

Severity: NOTICE
Message: Processed %d entries, skipped %d and rejected %d (recent rate %.1f/sec).

Severity: NOTICE
Message: %s starting import (build %s, R%s).

Severity: NOTICE
Message: Import Thread Count: %d threads.

Severity: NOTICE
Message: Due to changes in the configuration, index %s is currently operating in a degraded state and must be rebuilt before it can be used.

Severity: NOTICE
Message: Rebuild of all indexes started with %d total entries to process.

Severity: NOTICE
Message: Degraded state of index(es) %s has been cleared.

Severity: NOTICE
Message: Rebuild of all degraded indexes started with %d total entries to process.

Severity: NOTICE
Message: Rebuild complete. Processed %d entries in %d seconds (average rate %.1f/sec).

Severity: NOTICE
Message: %.1f%% Completed. Processed %d/%d entries. (recent rate %.1f/sec).

Severity: NOTICE
Message: Rebuild of index(es) %s started with %d total entries to process.

Severity: NOTICE
Message: A referral entry %s indicates that the operation must be processed at a different server.

Severity: NOTICE
Message: Checked %d records and found %d error(s) in %d seconds (average rate %.1f/sec).

Severity: NOTICE
Message: Checked %d entries and found %d error(s) in %d seconds (average rate %.1f/sec).

Severity: NOTICE
Message: Processed %d out of %d records and found %d error(s) (recent rate %.1f/sec).

Severity: WARNING
Message: The requested operation is not supported by this backend.

Severity: WARNING
Message: Unable to determine the total number of entries in the container: %s.

Severity: ERROR
Message: The database logging level string '%s' provided for configuration entry '%s' is invalid. The value must be one of OFF, SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST, or ALL. Note that these values are case sensitive.

Severity: ERROR
Message: Configuration attribute ds-cfg-db-cache-size has a value of %d which is less than the minimum: %d.

Severity: ERROR
Message: Missing ID %d%n%s.

Severity: ERROR
Message: Reference to unknown entry ID %s%n%s.

Severity: ERROR
Message: The entry with ID %s is associated with the wrong key%n%s.

Severity: ERROR
Message: Empty ID set: %n%s.

Severity: ERROR
Message: Duplicate reference to ID %d%n%s.

Severity: ERROR
Message: Reference to unknown ID %d%n%s.

Severity: ERROR
Message: Reference to entry <%s> which does not match the value%n%s.

Severity: ERROR
Message: File dn2id is missing key %s.

Severity: ERROR
Message: File dn2id has ID %d instead of %d for key %s.

Severity: ERROR
Message: File dn2id has DN <%s> referencing unknown ID %d.

Severity: ERROR
Message: File dn2id has DN <%s> referencing entry with wrong DN <%s>.

Severity: ERROR
Message: The stored entry count in id2entry (%d) does not agree with the actual number of entry records found (%d).

Severity: ERROR
Message: File id2childrenCount has wrong number of children for DN <%s> (got %d, expecting %d).

Severity: ERROR
Message: File id2ChildrenCount references non-existing EntryID <%d>.

Severity: NOTICE
Message: Rebuilding index finished: no indexes to rebuild.

Severity: NOTICE
Message: Setting DB cache size to %d MB. Using %d mb off-heap memory through %d phase one buffers of %d KB.

Severity: ERROR
Message: Ignoring schema definition '%s' because the following error occurred while it was being parsed: %s.

Severity: ERROR
Message: Schema definition could not be parsed as valid attribute value.

Severity: ERROR
Message: Attribute %s is set as confidential on a backend whose entries are still cleartext. Enable confidentiality on the backend first.

Severity: ERROR
Message: The attribute '%s' cannot enable confidentiality for keys and values at the same time.

Severity: ERROR
Message: Cannot encode entry for writing on storage: %s.

Severity: ERROR
Message: Input stream ended unexpectedly while decoding entry.

Severity: ERROR
Message: Confidentiality cannot be disabled on suffix '%s' because the following indexes have confidentiality still enabled: %s.

Severity: NOTICE
Message: Changing confidentiality for index '%s' requires the index to be rebuilt before it can be used again.

Severity: ERROR
Message: Error while enabling confidentiality with cipher %s, %d bits: %s.

Severity: ERROR
Message: The import has been aborted because the data to be imported contains duplicate copies of entry '%s'.

Severity: ERROR
Message: Proxy backend '%s' could not discover remote servers capabilities: %s.

Severity: INFO
Message: Proxy backend '%s' successfully configured failover via the service discovery mechanism '%s': primary servers are %s and secondary servers are %s.

Severity: WARNING
Message: Proxy backend '%s' cannot failover: only primary servers have been discovered via the service discovery mechanism '%s'. Primary servers are %s.

Severity: WARNING
Message: Proxy backend '%s' cannot failover: only secondary servers have been discovered via the service discovery mechanism '%s'. Secondary servers are %s.

Severity: ERROR
Message: Proxy backend '%s' is non functional because it could not find any primary nor secondary servers via the service discovery mechanism '%s'.

Severity: ERROR
Message: Proxy backend '%s' cannot find the configured service discovery mechanism '%s'.

Severity: NOTICE
Message: Connection options have changed for the proxy backend '%s'. The existing connections are being closed immediately. New ones are being opened.

Severity: NOTICE
Message: Connection pool options have changed for the proxy backend '%s'. The existing connections are being closed and re-opened.

Severity: NOTICE
Message: Service discovery mechanism has changed from '%s' to '%s' for proxy backend '%s'. The existing connections are being closed immediately.

Severity: NOTICE
Message: Remote servers changed for the proxy backend '%s'. The proxy was using: primary servers=%s, secondary servers=%s; and it will now be using: primary servers=%s, secondary servers=%s.

Severity: INFO
Message: Proxy backend '%s' automatically registered itself against the base DNs %s. It was previously registered against the base DNs %s.

Severity: ERROR
Message: No backend is associated with the base DN '%s'.

Severity: ERROR
Message: Proxy backend '%s' cannot register itself against base DN %s because this base DN is already registered against backend '%s'.

Severity: ERROR
Message: Proxy backend '%s' is being deregistered from base DN %s because local backend '%s' is registering against it. Local backends take precedence over proxy backends.

Severity: INFO
Message: The change to the LDIF backend visibility will not take effect until the backend is disabled and re-enabled.

Severity: INFO
Message: The primary servers for proxy backend '%s' are now available and will be used for proxying requests.

Severity: INFO
Message: The secondary servers for proxy backend '%s' are now available and will be used if the primary servers are unavailable.

Severity: WARNING
Message: The primary servers for proxy backend '%s' are unavailable. The secondary servers, if available, will be used for processing requests until the primary servers become available again. The last failure that prevented the primary servers from being used was: %s.

Severity: WARNING
Message: The secondary servers for proxy backend '%s' are unavailable. If the primary servers are unavailable, or become unavailable, then it will no longer be possible to proxy requests. The last failure that prevented the secondary servers from being used was: %s.

Severity: INFO
Message: The server '%s' for proxy backend '%s' is available and will be used for proxying requests.

Severity: WARNING
Message: The server '%s' for proxy backend '%s' is unavailable. The last failure that prevented the server from being used was: %s.

Severity: ERROR
Message: The partition base DN '%s' should be subordinate to one of the base DNs %s of proxy backend '%s'.

Severity: ERROR
Message: Backend database cache preload for backend '%s' is not supported in this release.

Severity: INFO
Message: Configuration of proxy backend '%s' with service discovery mechanism '%s' is in progress. Requests will not be proxied until configuration completes.

Severity: WARNING
Message: The server is performing an unindexed internal search request with base DN '%s', scope '%s', and filter '%s'. Unindexed internal searches are usually unexpected and could impact performance. Please verify that that backend’s indexes are configured correctly for these search parameters.

Severity: NOTICE
Message: Initial result code was '%s', with diagnostic message: %s.

Severity: ERROR
Message: There are insufficient resources to perform the operation.

Severity: ERROR
Message: The time-to-live (TTL) feature can only be enabled for generalized time ordering indexes.

Severity: ERROR
Message: An unexpected error occurred while purging expired entries: %s.

Severity: WARNING
Message: Unable to locate all expired entries on backend '%s' because the ttl-enabled index '%s' has reached the configured index-entry-limit.

Severity: ERROR
Message: The partition base DN '%s' shouldn’t be subordinate to one of the other partition base DNs %s of proxy backend '%s'.

Severity: WARNING
Message: The proxy backend '%s' will ignore the discovered servers '%s' from shard '%s' because they do not expose the required base DNs '%s'.

Severity: WARNING
Message: Property '%s' contains value '%s' which cannot be parsed as a long. Defaulting to '%s' bytes for small DB size.

Severity: ERROR
Message: An error occurred while trying to retrieve the key managers from the key manager provider %s.

Severity: ERROR
Message: Could not stop export-ldif threads after 30 seconds. Now forcing stop by interrupting them.

Severity: WARNING
Message: The file system used by '%s' backend does not support last file modification time. Backups will still work but will take longer and consume more space in the backup storage.

Severity: ERROR
Message: The index(es) cannot be rebuilt because the server failed to obtain a write lock for the entry '%s' after multiple attempts.

Severity: ERROR
Message: VLV index '%s' must be configured with at least one sort attribute.

Severity: ERROR
Message: Missing entry %s in index %s.

Severity: ERROR
Message: Big index for attribute '%s' cannot be created for matching rule '%s' because it is not an equality matching rule.

Severity: WARNING
Message: The subtree delete against '%s' is being performed non-atomically because it is deleting more than %s subordinate entries. To prevent inconsistency across replicas, the client must retry this same delete operation until it succeeds.

Severity: ERROR
Message: A Server Side Sort control must be specified whenever a Virtual List View control is present.

Severity: ERROR
Message: Counter of %s reports wrong number of entries for key <%s> (got %d, expecting %d).

Severity: ERROR
Message: An error occurred while attempting to send an email for the completion of %s task: Task ID: %s, Task State: %s, Scheduled Start Time: %s, Actual Start Time: %s, Completion Time: %s. The error was: %s.

Severity: ERROR
Message: Index for attribute '%s' cannot be created because the configuration contains an included attribute value '%s' which appears to be invalid according to the schema: %s.

Severity: ERROR
Message: The VLV request cannot be processed because the search is not indexed. Configure a VLV index matching the request.

Severity: WARNING
Message: Both equality and presence index types are defined for attribute '%s'. The presence index is only useful when the same value of the attribute is present at most in 'ds-cfg-index-entry-limit' number of entries, currently configured at %d.

Severity: ERROR
Message: An internal error occurred when accessing backend '%s': %s.

Severity: ERROR
Message: An internal error was detected when accessing backend '%s'.

Severity: NOTICE
Message: Starting backup for backend '%s'.

Severity: NOTICE
Message: Starting restore for backend '%s' with backup ID '%s'.

Severity: NOTICE
Message: Backup completed for backend '%s' with backup ID '%s'.

Severity: NOTICE
Message: Restore completed for backend '%s' with backup ID '%s'.

Severity: NOTICE
Message: An error occurred while attempting to backup backend '%s': %s.

Severity: NOTICE
Message: The backup process failed with one or more errors.

Severity: NOTICE
Message: The restore process failed with one or more errors.

Severity: NOTICE
Message: An error occurred while attempting to restore backend '%s' with backup ID '%s': %s.

Severity: NOTICE
Message: There are no enabled backends that support backup operation.

Severity: NOTICE
Message: The backup command was interrupted.

Severity: NOTICE
Message: Cannot read backup directory content: %s.

Severity: NOTICE
Message: Backup still in progress, new files have been created.

Severity: NOTICE
Message: Backing up file (%d/%d) '%s'.

Severity: NOTICE
Message: Verifying file (%d/%d) '%s'.

Severity: NOTICE
Message: Restoring file (%d/%d) '%s'.

Severity: NOTICE
Message: Purging backup (%d/%d) '%s'.

Severity: NOTICE
Message: The following backends do not exist or are disabled: %s. Here is the list of enabled backends that support backups: %s.

Severity: NOTICE
Message: The following backends do not support backups: %s. Here is the list of enabled backends that support backups: %s.

Severity: NOTICE
Message: The backends %s cannot be restored because they do not exist or are disabled.

Severity: NOTICE
Message: Cannot find backup with ID %s.

Severity: NOTICE
Message: There are no backups for backends %s.

Severity: NOTICE
Message: The backends %s cannot be restored while the server is running. Please stop the server first and try again with the --offline option.

Severity: NOTICE
Message: '%s' is not a valid name for a directory.

Severity: NOTICE
Message: Found backup IDs that correspond to the same backend name: %s. Make sure each backup ID corresponds to a distinct backend.

Severity: NOTICE
Message: Either the --%s or --%s argument must be provided.

Severity: NOTICE
Message: Cannot delete corrupted file '%s'.

Severity: NOTICE
Message: Deleting corrupted file from backend directory.

Severity: NOTICE
Message: Deleting corrupted file from backup storage.

Severity: NOTICE
Message: signature does not match.

Severity: NOTICE
Message: unexpected content.

Severity: NOTICE
Message: Problem with file '%s' : %s.

Severity: NOTICE
Message: IO error: %s.

Severity: NOTICE
Message: Operation was interrupted.

Severity: NOTICE
Message: File '%s' is corrupted: %s.

Severity: NOTICE
Message: File '%s' is missing.

Severity: NOTICE
Message: The directory does not exist.

Severity: NOTICE
Message: Not a directory.

Severity: NOTICE
Message: Cannot read backend files in directory '%s': %s.

Severity: NOTICE
Message: Cannot delete backend files from directory '%s': %s.

Severity: NOTICE
Message: The '%s' backend files have been removed after restore failed. The backend is now empty.

Severity: NOTICE
Message: Cannot create the backend directory '%s' before restoring: %s.

Severity: NOTICE
Message: The attempt to remove backend files from directory '%s' has failed, backend '%s' may contain corrupted data, please remove the files manually.

Severity: NOTICE
Message: The backup ID '%s' already exists.

Severity: NOTICE
Message: Cannot compute the fingerprint for backend file '%s': %s.

Severity: NOTICE
Message: Unable to access the backup storage: %s.

Severity: NOTICE
Message: No plugin found to handle the storage scheme '%s'.

Severity: NOTICE
Message: Cannot delete the backup lock file '%s', please remove this file manually: %s.

Severity: NOTICE
Message: Cannot acquire a shared lock for backend '%s': %s. This generally means that some other process has exclusive access to this backend (e.g., a restore or an LDIF import).

Severity: NOTICE
Message: Cannot release the shared lock for backend '%s': %s. This lock should automatically be cleared when the backup process exits, so no further action should be required.

Severity: NOTICE
Message: Cannot acquire an exclusive lock for backend '%s': %s. This generally means some other process is still using this backend (e.g., it is in use by the Directory Server or a backup or LDIF export is in progress).

Severity: NOTICE
Message: Cannot release the exclusive lock for backend '%s': %s. This lock should automatically be cleared when the restore process exits, so no further action should be required.

Severity: NOTICE
Message: Cannot enable backend '%s' after restoring: %s.

Severity: NOTICE
Message: Backup ID: %s.

Severity: NOTICE
Message: Backup Date: %s.

Severity: NOTICE
Message: Backend name: %s.

Severity: NOTICE
Message: Server ID: %s.

Severity: NOTICE
Message: Status: %s.

Severity: NOTICE
Message: Error: %s.

Severity: NOTICE
Message: Verified.

Severity: NOTICE
Message: Bad.

Severity: NOTICE
Message: Found %s backup(s) with the requested characteristics.

Severity: NOTICE
Message: There are no backups with the requested characteristics.

Severity: NOTICE
Message: %s backup(s) cannot be restored.

Severity: NOTICE
Message: Found %s backup(s) that cannot be fully identified due to the following error(s):.

Severity: NOTICE
Message: Backup and restore backends, manage backup files.

Severity: NOTICE
Message: Backup and restore backends.

Severity: NOTICE
Message: {backup location}.

Severity: NOTICE
Message: Indicates that the command will operate independently of the server process. It will run regardless of whether the server is started or stopped. When using this option with the %1$s sub-command, the server must be stopped; also as the command will write to server files, you should run the command as a user having the same filesystem permissions as the user running the server. Using this option with the %2$s sub-command when the server is running is possible and supported. With JE Backends, the integrity of the backup is ensured by the process. With LDIF backends, avoid simultaneous changes to the backends.

Severity: NOTICE
Message: Backup file-system path or URI for alternative storage mechanisms. File-system paths may be expressed as absolute or relative paths and are resolved relative to the current working directory when the tool is run in offline mode, or relative to the server instance directory when the tool is run in task mode. Read the documentation for further information regarding alternative backup storage mechanisms.

Severity: NOTICE
Message: Location containing backups: file-system path or URI for alternative storage mechanisms. File-system paths may be expressed as absolute or relative paths and are resolved relative to the current working directory when the tool is run in offline mode, or relative to the server instance directory when the tool is run in task mode. Read the documentation for further information regarding alternative backup storage mechanisms.

Severity: NOTICE
Message: {PROP:VALUE}.

Severity: NOTICE
Message: Assigns a value to a storage property where PROP is the name of the property and VALUE is the single value to be assigned. Specify the same property multiple times in order to assign more than one value to it.

Severity: NOTICE
Message: List the backups at the specified location.

Severity: NOTICE
Message: Show only backups taken from the provided backend.

Severity: NOTICE
Message: Show only backups taken from the provided server.

Severity: NOTICE
Message: {server ID}.

Severity: NOTICE
Message: Show only the last backup for each backend.

Severity: NOTICE
Message: Verify backups completeness, integrity and whether they can be decrypted.

Severity: NOTICE
Message: Take encrypted and signed backups of individual backends and send them to the desired location.

Severity: NOTICE
Message: The name of the backend to back up. Specify this option multiple times to backup multiple backends or skip this option to backup all the enabled backends that support backups.

Severity: NOTICE
Message: {backup ID}.

Severity: NOTICE
Message: Restore one or more backends. In order to decrypt and verify signatures on backup files, the server must have access to the master key pair used to encrypt and sign the files when they were created.

Severity: NOTICE
Message: Restore the backup having the provided ID. Specify this option multiple times to restore multiple backends.

Severity: NOTICE
Message: Restore the last backup of the provided backend. Specify this option multiple times to restore multiple backends.

Severity: NOTICE
Message: Delete one or more backups.

Severity: NOTICE
Message: The ID of the backup that should be deleted. Specify this option multiple times to purge multiple backups.

Severity: NOTICE
Message: At least one of these options must be declared: %s.

Severity: NOTICE
Message: The option '--%s' can only be used with the option '--%s'.

Severity: NOTICE
Message: {number of backups}.

Severity: NOTICE
Message: The number of backups to keep per backend. Use this option to keep the n latest backups of each backend and delete the others. If n=0, all the backups will be removed.

Severity: NOTICE
Message: {duration}.

Severity: NOTICE
Message: Delete backups that are older than the provided duration. The latest backup of each backend will always be kept unless the '--%s' option is also provided. Duration examples: '12 hours', '3 days', '1y'.

Severity: NOTICE
Message: Must be used with the '--%s' option, indicates that the last backup of each backend can be deleted if older than the provided duration.

Severity: NOTICE
Message: {backend name}.

Severity: NOTICE
Message: Purge only backups of the specified backend. Specify this option multiple times to allow purging backups of different backends. Skip this option to allow purging backups of all backends. This can only be used with options '--%s' or '--%s'.

Severity: NOTICE
Message: '%d' is not allowed: the value must be equal or greater than 0.

Severity: NOTICE
Message: Invalid value for '%s': %s.

Severity: NOTICE
Message: An error occurred while attempting to purge the backup '%s': %s.

Severity: NOTICE
Message: An error occurred while attempting to purge backup files starting with '%s': %s.

Severity: NOTICE
Message: Backup purge process failed with one or more errors.

Severity: NOTICE
Message: Purge completed successfully.

Severity: NOTICE
Message: The storage property '%s' has several values while it can have only one. The provided properties string was: "%s".

Severity: ERROR
Message: Backup id '%s' is invalid: expected to find an underscore in it.

Severity: ERROR
Message: Backup id '%s' is invalid: cannot parse '%s' as a timestamp.

Severity: NOTICE
Message: Access denied to file '%s'.

Severity: ERROR
Message: Credential file '%s' not found.

Severity: ERROR
Message: Failed to parse the credential file '%s'.

Severity: ERROR
Message: Invalid plugin type '%s', a backup plugin must be of type '%s'.

Severity: ERROR
Message: A problem occurred while connecting to cloud provider '%s' using the provided credentials: %s.

Severity: ERROR
Message: No value found for property '%s'.

Severity: ERROR
Message: No environment value '%s' found for property '%s'. If you are running the tool in offline mode, make sure the command has access to this variable, or else make sure the directory server has access to it.

Severity: ERROR
Message: Could not find file '%s' in cloud bucket '%s'.

Severity: ERROR
Message: An error occurred while uploading the file to the cloud storage: the host '%s' is an unknown host.

Severity: ERROR
Message: An error occurred while uploading the file to the cloud storage. The cloud provider returned the following error message: '%s'.

Severity: ERROR
Message: Unable to set the value for Boolean configuration attribute %s because the provided value %s was not either 'true' or 'false'.

Severity: ERROR
Message: Unable to set the value for integer configuration attribute %s because the provided value %s cannot be interpreted as an integer value: %s.

Severity: ERROR
Message: Unable to set the value for configuration attribute %s because the provided value %d is less than the lowest allowed value of %d.

Severity: ERROR
Message: Unable to set the value for configuration attribute %s because the provided value %d is greater than the largest allowed value of %d.

Severity: ERROR
Message: The specified configuration file %s does not exist or is not readable.

Severity: ERROR
Message: An error occurred while attempting to open the configuration file %s for reading: %s.

Severity: ERROR
Message: The first entry read from LDIF configuration file %s had a DN of "%s" rather than the expected "%s" which should be used as the Directory Server configuration root.

Severity: ERROR
Message: An unexpected error occurred while attempting to process the Directory Server configuration file %s: %s.

Severity: ERROR
Message: Unable to determine the Directory Server instance root from either an environment variable or based on the location of the configuration file. Please set an environment variable named %s with a value containing the absolute path to the server installation root.

Severity: ERROR
Message: An unexpected error occurred while trying to write configuration entry %s to LDIF: %s.

Severity: ERROR
Message: The Directory Server configuration may not be altered by importing a new configuration from LDIF.

Severity: WARNING
Message: There are no active access loggers defined in the Directory Server configuration. No access logging will be performed.

Severity: WARNING
Message: There are no active error loggers defined in the Directory Server configuration. No error logging will be performed.

Severity: ERROR
Message: An error occurred while attempting to create a Directory Server logger from the information in configuration entry %s: %s.

Severity: ERROR
Message: Configuration entry %s does not contain a valid objectclass for a Directory Server access, error, or debug logger definition.

Severity: ERROR
Message: Class %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server access logger: %s.

Severity: ERROR
Message: Class %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server error logger: %s.

Severity: ERROR
Message: Class %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server debug logger: %s.

Severity: ERROR
Message: Configuration entry %s does not contain attribute %s (or that attribute exists but is not accessible using JMX).

Severity: ERROR
Message: There is no method %s for any invokable component registered with configuration entry %s.

Severity: ERROR
Message: The Directory Server could not register a JMX MBean for the component associated with configuration entry %s: %s.

Severity: ERROR
Message: An unexpected error occurred while trying to export the Directory Server configuration to LDIF: %s.

Severity: ERROR
Message: Worker thread "%s" has experienced too many repeated failures while attempting to retrieve the next operation from the work queue (%d failures experienced, maximum of %d failures allowed). This worker thread will be destroyed.

Severity: ERROR
Message: An unexpected error occurred while trying to register the configuration handler base DN "%s" as a private suffix with the Directory Server: %s.

Severity: ERROR
Message: The entry cn=Backends,cn=config does not appear to exist in the Directory Server configuration. This is a required entry.

Severity: INFO
Message: The backend defined in configuration entry %s is marked as disabled and therefore will not be used.

Severity: ERROR
Message: An unexpected error occurred while attempting to determine whether the backend associated with configuration entry %s should be enabled or disabled: %s. It will be disabled.

Severity: ERROR
Message: The Directory Server was unable to load class %s and use it to create a backend instance as defined in configuration entry %s. The error that occurred was: %s. This backend will be disabled.

Severity: ERROR
Message: An error occurred while trying to initialize a backend loaded from class %s with the information in configuration entry %s: %s. This backend will be disabled.

Severity: NOTICE
Message: The requested change to configuration entry %s would cause the class for the associated backend to change from %s to %s. This change will not take effect until the backend is disabled and re-enabled, or until the Directory Server is restarted.

Severity: ERROR
Message: An error occurred while trying to initialize a connection handler loaded from class %s with the information in configuration entry %s: %s. This connection handler will be disabled.

Severity: ERROR
Message: Unable to read the Directory Server schema definitions because the schema directory %s does not exist.

Severity: ERROR
Message: Unable to read the Directory Server schema definitions because the schema directory %s exists but is not a directory.

Severity: ERROR
Message: Unable to read the Directory Server schema definitions from directory %s because an unexpected error occurred while trying to list the files in that directory: %s.

Severity: WARNING
Message: Schema configuration file %s in directory %s cannot be parsed because an unexpected error occurred while trying to open the file for reading: %s.

Severity: WARNING
Message: Schema configuration file %s in directory %s cannot be parsed because an unexpected error occurred while trying to read its contents as an LDIF entry: %s.

Severity: ERROR
Message: An unexpected error occurred that prevented the server from installing its default entry cache framework: %s.

Severity: WARNING
Message: The entry cache configuration entry "cn=Entry Caches,cn=config" does not exist in the Directory Server configuration. No entry cache will be available until this entry is created with a valid entry cache configuration.

Severity: ERROR
Message: An error occurred while attempting to initialize an instance of class %s for use as the Directory Server entry cache: %s. As a result, the entry cache will be disabled.

Severity: ERROR
Message: The configuration for the entry cache defined in configuration entry %s was not acceptable: %s.

Severity: ERROR
Message: The configuration for the entry cache defined in configuration entry %s was not acceptable: the entry cache level %d is already in use.

Severity: ERROR
Message: An error occurred while attempting to initialize an instance of class %s as a Directory Server plugin using the information in configuration entry %s: %s. This plugin will be disabled.

Severity: ERROR
Message: Class %s specified in configuration entry %s does not contain a valid extended operation handler implementation: %s.

Severity: ERROR
Message: An error occurred while trying to initialize an instance of class %s as an extended operation handler as defined in configuration entry %s: %s.

Severity: ERROR
Message: An error occurred while trying to initialize an instance of class %s as a SASL mechanism handler as defined in configuration entry %s: %s.

Severity: ERROR
Message: Entry %s cannot be removed from the Directory Server configuration because that DN does not have a parent.

Severity: ERROR
Message: Entry %s cannot be added to the Directory Server configuration because another configuration entry already exists with that DN.

Severity: ERROR
Message: Entry %s cannot be added to the Directory Server configuration because that DN does not have a parent.

Severity: ERROR
Message: Entry %s cannot be added to the Directory Server configuration because its parent entry %s does not exist.

Severity: ERROR
Message: The Directory Server is unwilling to add configuration entry %s because one of the add listeners registered with the parent entry %s rejected this change with the message: %s.

Severity: ERROR
Message: An unexpected error occurred while attempting to add configuration entry %s as a child of entry %s: %s.

Severity: ERROR
Message: Entry %s cannot be removed from the Directory Server configuration because the specified entry does not exist.

Severity: ERROR
Message: Entry %s cannot be removed from the Directory Server configuration because the specified entry has one or more subordinate entries.

Severity: ERROR
Message: Entry %s cannot be removed from the Directory Server configuration because the entry does not have a parent and removing the configuration root entry is not allowed.

Severity: ERROR
Message: Entry %s cannot be removed from the Directory Server configuration because one of the delete listeners registered with the parent entry %s rejected this change with the message: %s.

Severity: ERROR
Message: An unexpected error occurred while attempting to remove configuration entry %s as a child of entry %s: %s.

Severity: ERROR
Message: Entry %s cannot be modified because the specified entry does not exist.

Severity: ERROR
Message: Entry %s cannot be modified because one of the configuration change listeners registered for that entry rejected the change: %s.

Severity: ERROR
Message: An unexpected error occurred while attempting to modify configuration entry %s as a child of entry %s: %s.

Severity: ERROR
Message: An error occurred while attempting to export the new Directory Server configuration to file %s: %s.

Severity: ERROR
Message: An error occurred while attempting to rename the new Directory Server configuration from file %s to %s: %s.

Severity: ERROR
Message: Modify DN operations are not allowed in the Directory Server configuration.

Severity: ERROR
Message: An error occurred while trying to initialize an instance of class %s as a password storage scheme as defined in configuration entry %s: %s.

Severity: ERROR
Message: Unable to add a new password storage scheme entry with DN %s because there is already a storage scheme registered with that DN.

Severity: WARNING
Message: The backend defined in configuration entry %s has a backend ID of %s that conflicts with the backend ID for another backend in the server. The backend will be disabled.

Severity: ERROR
Message: The Directory Server was unable to acquire a shared lock for backend %s: %s. This generally means that the backend is in use by a process that requires an exclusive lock (e.g., importing from LDIF or restoring a backup). This backend will be disabled.

Severity: WARNING
Message: An error occurred while attempting to release a shared lock for backend %s: %s. This may interfere with operations that require exclusive access, including LDIF import and restoring a backup.

Severity: ERROR
Message: An error occurred while trying to initialize an instance of class %s as an identity mapper as defined in configuration entry %s: %s.

Severity: ERROR
Message: An error occurred while attempting to instantiate class %s referenced in synchronization provider configuration entry %s: %s.

Severity: ERROR
Message: An error occurred while attempting to initialize the Directory Server synchronization provider referenced in configuration entry %s: %s.

Severity: ERROR
Message: An error occurred while trying to initialize an instance of class %s as a password validator as defined in configuration entry %s: %s.

Severity: ERROR
Message: An error occurred while trying to initialize an instance of class %s as a password generator as defined in configuration entry %s: %s.

Severity: ERROR
Message: No password policies have been defined below the cn=Password Policies,cn=config entry in the Directory Server configuration. At least one password policy configuration must be defined.

Severity: ERROR
Message: The password policy defined in configuration entry %s is invalid: %s.

Severity: ERROR
Message: The Directory Server default password policy is defined as %s, but that entry does not exist or is not below the password policy configuration base cn=Password Policies,cn=config.

Severity: WARNING
Message: The specified entry %s is currently defined as the configuration entry for the default password policy. The default password policy configuration entry may not be removed.

Severity: INFO
Message: Password policy entry %s has been removed from the Directory Server configuration. Any user entries that explicitly reference this password policy will no longer be allowed to authenticate.

Severity: WARNING
Message: Access control has been disabled.

Severity: NOTICE
Message: Access control has been enabled and will use the %s implementation.

Severity: ERROR
Message: An error occurred while attempting to instantiate class %s referenced in the access control configuration entry %s: %s.

Severity: ERROR
Message: An error occurred while trying to initialize an instance of class %s as an account status notification handler as defined in configuration entry %s: %s.

Severity: ERROR
Message: Unable to add a new account status notification handler entry with DN %s because there is already a notification handler registered with that DN.

Severity: ERROR
Message: An error occurred while attempting to apply the changes contained in file %s to the server configuration at startup: %s.

Severity: ERROR
Message: One or more errors occurred while applying changes on server startup: %s.

Severity: ERROR
Message: Configuration entry %s does not contain a valid value for configuration attribute ds-cfg-db-directory-permissions (It should be an UNIX permission mode in three-digit octal notation.).

Severity: ERROR
Message: Invalid UNIX file permissions %s does not allow read and write access to the backend database directory by the backend.

Severity: ERROR
Message: No default password policy is configured for the Directory Server. The default password policy must be specified by the ds-cfg-default-password-policy attribute in the cn=config entry.

Severity: WARNING
Message: An error occurred while attempting to register backend %s with the Directory Server: %s.

Severity: ERROR
Message: An error occurred while trying to create the configuration archive directory %s: %s.

Severity: ERROR
Message: An error occurred while trying to write the current configuration to the configuration archive: %s.

Severity: ERROR
Message: You do not have sufficient privileges to perform add operations in the Directory Server configuration.

Severity: ERROR
Message: You do not have sufficient privileges to perform delete operations in the Directory Server configuration.

Severity: ERROR
Message: You do not have sufficient privileges to perform modify operations in the Directory Server configuration.

Severity: ERROR
Message: You do not have sufficient privileges to perform modify DN operations in the Directory Server configuration.

Severity: ERROR
Message: You do not have sufficient privileges to perform search operations in the Directory Server configuration.

Severity: ERROR
Message: You do not have sufficient privileges to change the set of default root privileges.

Severity: ERROR
Message: An error occurred while trying to initialize an instance of class %s as a certificate mapper as defined in configuration entry %s: %s.

Severity: ERROR
Message: An error occurred while trying to initialize an instance of class %s as a key manager provider as defined in configuration entry %s: %s.

Severity: ERROR
Message: An error occurred while trying to initialize an instance of class %s as a trust manager provider as defined in configuration entry %s: %s.

Severity: ERROR
Message: Unable to retrieve JMX attribute %s associated with configuration entry %s: %s.

Severity: ERROR
Message: %s.%s returned a result of null for entry %s.

Severity: ERROR
Message: %s.%s failed for entry %s: result code=%s, admin action required=%b, messages="%s".

Severity: WARNING
Message: %s.%s indicated that administrative action is required for entry %s: messages="%s".

Severity: INFO
Message: %s.%s succeeded but generated the following messages for entry %s: %s.

Severity: ERROR
Message: Unable to parse value "%s" from config entry "%s" as a valid search filter: %s.

Severity: ERROR
Message: An error occurred while trying to load an instance of class %s referenced in configuration entry %s as a virtual attribute provider: %s.

Severity: ERROR
Message: The virtual attribute configuration in entry "%s" is not valid because attribute type %s is single-valued but provider %s may generate multiple values.

Severity: ERROR
Message: The virtual attribute configuration in entry "%s" is not valid because attribute type %s is single-valued but the conflict behavior is configured to merge real and virtual values.

Severity: ERROR
Message: Configuration entry %s cannot be modified because the change would alter its structural object class.

Severity: ERROR
Message: An error occurred while attempting to calculate a SHA-1 digest of file %s: %s.

Severity: WARNING
Message: The Directory Server has detected that one or more external changes have been made to the configuration file %s while the server was online, but another change has caused the server configuration to be overwritten. The manual changes have not been applied, but they have been preserved in file %s.

Severity: ERROR
Message: The Directory Server encountered an error while attempting to determine whether the configuration file %s has been externally edited with the server online, and/or trying to preserve such changes: %s. Any manual changes made to that file may have been lost.

Severity: ERROR
Message: Class %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server log rotation policy: %s.

Severity: ERROR
Message: Class %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server log retention policy: %s.

Severity: ERROR
Message: An error occurred while attempting to create a Directory Server log rotation policy from the information in configuration entry %s: %s.

Severity: ERROR
Message: An error occurred while attempting to create a Directory Server log retention policy from the information in configuration entry %s: %s.

Severity: ERROR
Message: An error occurred while attempting to create a text writer for a Directory Server logger from the information in configuration entry %s: %s.

Severity: WARNING
Message: Schema configuration file %s in directory %s contains more than one entry. Only the first entry will be examined, and the additional entries will be ignored.

Severity: WARNING
Message: The plugin order definition for plugins of type %s contains an empty element. This may cause the plugin order to be evaluated incorrectly.

Severity: WARNING
Message: The plugin order definition for plugins of type %s contains multiple wildcard characters. All plugin definitions should contain exactly one wildcard element to indicate where unmatched plugins should be included in the order, and including multiple wildcards may cause the plugin order to be evaluated incorrectly.

Severity: WARNING
Message: The plugin order definition for plugins of type %s includes multiple references to the '%s' plugin. This may cause the plugin order to be evaluated incorrectly.

Severity: WARNING
Message: The plugin order definition for plugins of type %s does not include a wildcard element to indicate where unmatched plugins should be included in the order. The server will default to invoking all unnamed plugins after set of named plugins.

Severity: ERROR
Message: Unable to initialize an instance of class %s as a work queue as specified in configuration entry %s: %s.

Severity: INFO
Message: The class used to provide the Directory Server work queue implementation has been changed from %s to %s, but this change will not take effect until the server is restarted.

Severity: ERROR
Message: The attempt to apply the configuration add failed. The preliminary checks were all successful and the entry was added to the server configuration, but at least one of the configuration add listeners reported an error when attempting to apply the change: %s.

Severity: ERROR
Message: The attempt to apply the configuration delete failed. The preliminary checks were all successful and the entry was removed from the server configuration, but at least one of the configuration delete listeners reported an error when attempting to apply the change: %s.

Severity: ERROR
Message: The attempt to apply the configuration modification failed. The preliminary checks were all successful and the modified entry was written to the server configuration, but at least one of the configuration change listeners reported an error when attempting to apply the change: %s.

Severity: ERROR
Message: The configuration for the key manager provider defined in configuration entry %s was not acceptable: %s.

Severity: ERROR
Message: The configuration for the trust manager provider defined in configuration entry %s was not acceptable: %s.

Severity: ERROR
Message: The configuration for the trust manager provider defined in configuration entry %s was not acceptable: %s.

Severity: ERROR
Message: The configuration for the account status notification handler defined in configuration entry %s was not acceptable: %s.

Severity: ERROR
Message: The configuration for the certificate mapper defined in configuration entry %s was not acceptable: %s.

Severity: ERROR
Message: The configuration for the identity mapper defined in configuration entry %s was not acceptable: %s.

Severity: ERROR
Message: The configuration for the password generator defined in configuration entry %s was not acceptable: %s.

Severity: ERROR
Message: The configuration for the password storage scheme defined in configuration entry %s was not acceptable: %s.

Severity: ERROR
Message: The configuration for the password validator defined in configuration entry %s was not acceptable: %s.

Severity: ERROR
Message: The configuration for the plugin defined in configuration entry %s was not acceptable: %s.

Severity: ERROR
Message: The configuration for the SASL mechanism handler defined in configuration entry %s was not acceptable: %s.

Severity: ERROR
Message: The configuration for the virtual attribute provider defined in configuration entry %s was not acceptable: %s.

Severity: ERROR
Message: The configuration for the alert handler defined in configuration entry %s was not acceptable: %s.

Severity: ERROR
Message: An error occurred while trying to initialize an instance of class %s as an alert handler as defined in configuration entry %s: %s.

Severity: ERROR
Message: An error occurred while attempting to open the current configuration file %s for reading in order to copy it to the ".startok" file: %s.

Severity: ERROR
Message: An error occurred while attempting to copy the current configuration from file %s into temporary file %s for use as the ".startok" configuration file: %s.

Severity: ERROR
Message: An error occurred while attempting to rename file %s to %s for use as the ".startok" configuration file: %s.

Severity: NOTICE
Message: The Directory Server is starting using the last known good configuration file %s rather than the active configuration file %s.

Severity: WARNING
Message: No last known good configuration file %s exists. The server will attempt to start using the active configuration file %s.

Severity: ERROR
Message: An error occurred while trying to parse and validate Berkeley DB JE property %s: %s.

Severity: ERROR
Message: An error occurred while trying to parse and validate Berkeley DB JE property %s: the property does not follow a singular property=value form.

Severity: ERROR
Message: An error occurred while trying to parse and validate Berkeley DB JE property %s: the property shadows configuration attribute %s.

Severity: ERROR
Message: An error occurred while trying to parse and validate Berkeley DB JE property %s: the property is already defined for this component.

Severity: ERROR
Message: An error occurred while attempting to open the configured log file %s for logger %s: %s.

Severity: ERROR
Message: Invalid UNIX file permissions %s does not allow write access to the log file by the log publisher.

Severity: ERROR
Message: Invalid UNIX file permissions %s: %s.

Severity: ERROR
Message: The configuration entry '%s' is currently defined to be the default password policy, however it is not a password policy.

Severity: ERROR
Message: The default password policy value '%s' is invalid because it refers to an authentication policy which is not a password policy.

Severity: ERROR
Message: The timestamp format string "%s" is not a valid format string. The format string should conform to the syntax described in the documentation for the "java.text.SimpleDateFormat" class.

Severity: ERROR
Message: The access log filtering criteria defined in "%s" could not be parsed because it contains an invalid user DN pattern "%s".

Severity: ERROR
Message: The access log filtering criteria defined in "%s" could not be parsed because it contains an invalid target DN pattern "%s".

Severity: WARNING
Message: There are no active HTTP access loggers defined in the Directory Server configuration. No HTTP access logging will be performed.

Severity: ERROR
Message: Class %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server HTTP access logger: %s.

Severity: WARNING
Message: The log format for %s contains the following unsupported fields: %s. Their output will be replaced with a dash ("-") character.

Severity: ERROR
Message: An error occurred while attempting to update a Directory Server logger from the information in configuration entry %s: %s.

Severity: ERROR
Message: Cannot configure java.util.logging root logger level: %s. java.util.logging support is now disabled.

Severity: ERROR
Message: An error occurred while trying to initialize an instance of class %s as an HTTP endpoint as defined in configuration entry %s: %s.

Severity: ERROR
Message: An error occurred while starting the HTTP endpoint as defined in configuration entry %s: %s.

Severity: ERROR
Message: The HTTP endpoint configuration defined in %s is invalid: %s.

Severity: ERROR
Message: Cannot initialize the configuration framework: %s.

Severity: ERROR
Message: Unable to retrieve children of configuration entry with dn: %s.

Severity: ERROR
Message: Unable to load the configuration-enabled schema: %s.

Severity: ERROR
Message: Backend config error when trying to delete an entry: %s.

Severity: ERROR
Message: The HTTP endpoint configuration defined in %s is referencing a non existing authorization DN %s.

Severity: ERROR
Message: The HTTP endpoint configuration defined in %s is referencing mutually exclusive authorization DNs %s and %s.

Severity: ERROR
Message: Unable to read the configuration from %s in the REST2LDAP endpoint configuration entry %s: %s.

Severity: ERROR
Message: Invalid JSON element %s from %s in the REST2LDAP endpoint configuration entry %s: %s.

Severity: ERROR
Message: Invalid configuration element from %s in the REST2LDAP endpoint configuration entry %s: %s.

Severity: ERROR
Message: The OAuth2 authorization mechanism defined in %s contains an invalid JSON Pointer %s: %s.

Severity: ERROR
Message: The authorization mechanism defined in %s is referencing a non-existing or non-readable directory: %s.

Severity: ERROR
Message: The authorization mechanism defined in %s is referencing a non existing DN: %s.

Severity: ERROR
Message: The authorization mechanism defined in %s is referencing an invalid URL %s: %s.

Severity: ERROR
Message: Unable to configure the authorization mechanism defined in %s: %s.

Severity: ERROR
Message: The requested admin API version '%s' is unsupported. This endpoint only supports the following admin API version(s): %s.

Severity: ERROR
Message: The configuration of schema provider '%s' is not acceptable for the following reasons: %s.

Severity: ERROR
Message: The schema provider class '%s' could not be instantiated or initialized with the configuration '%s' : %s.

Severity: ERROR
Message: The core schema provider defined by '%s' has been disabled. The core schema must always be enabled.

Severity: WARNING
Message: The config schema file '%s' generated warning when trying to update schema with its content: %s.

Severity: WARNING
Message: The config schema file '%s' generated warning when trying to update schema with its content, despite allowing to overwrite definitions: %s.

Severity: ERROR
Message: Unable to configure the backend '%s' because one of its base DNs is the empty DN.

Severity: ERROR
Message: Cannot configure new SSL protocols because the following protocols are not supported: %s. Look for supported protocols in 'cn=jvm,cn=monitor'.

Severity: ERROR
Message: Cannot configure new SSL cipher suites because the following cipher suites are not supported: %s. Look for supported cipher suites in 'cn=jvm,cn=monitor'.

Severity: ERROR
Message: The metric name pattern to exclude '%s' cannot be parsed as a valid regular expression due to the following error: '%s'.

Severity: ERROR
Message: The metric name pattern to include '%s' cannot be parsed as a valid regular expression due to the following error: '%s'.

Severity: ERROR
Message: The list of keys defined for the JSON matching rule contains an invalid JSON pointer : %s.

Severity: ERROR
Message: Cannot create the property resolver due to the following error: '%s'.

Severity: ERROR
Message: Error creating SSL socket factory: %s.

Severity: ERROR
Message: The smtp-server value '%s' is invalid: %s.

Severity: ERROR
Message: Unable to resolve the host for the listen address '%s' of the LDAP connection handler %s.

Severity: WARNING
Message: The latest archived configuration file %s appears to be invalid. Forcing creation of a new one.

Severity: WARNING
Message: '%s' is DEPRECATED for removal since %s. Its usage is highly discouraged.

Severity: WARNING
Message: '%s' is LEGACY since %s. Its usage is highly discouraged.

Severity: ERROR
Message: Abandon requests cannot be canceled.

Severity: ERROR
Message: Bind requests cannot be canceled.

Severity: ERROR
Message: Unbind requests cannot be canceled.

Severity: INFO
Message: Client Unbind.

Severity: INFO
Message: Client Disconnect.

Severity: INFO
Message: Client Connection Rejected.

Severity: INFO
Message: I/O Error.

Severity: INFO
Message: Protocol Error.

Severity: INFO
Message: Server Shutdown.

Severity: INFO
Message: Administrative Termination.

Severity: INFO
Message: Security Problem.

Severity: INFO
Message: Maximum Request Size Exceeded.

Severity: INFO
Message: Administrative Limit Exceeded.

Severity: INFO
Message: Idle Time Limit Exceeded.

Severity: INFO
Message: I/O Timeout.

Severity: INFO
Message: Connection Closed by Plugin.

Severity: INFO
Message: Unknown Closure Reason.

Severity: INFO
Message: Operations Error.

Severity: INFO
Message: Invalid Credentials.

Severity: INFO
Message: Processing on this operation has been canceled because the Directory Server is shutting down.

Severity: ERROR
Message: %s encountered an uncaught exception while processing operation %s: %s.

Severity: WARNING
Message: %s is unexpectedly exiting when the Directory Server is not in the process of shutting down. This likely indicates that the thread encountered an unexpected error.

Severity: WARNING
Message: The request to process this operation has been rejected because the Directory Server has already started its shutdown process.

Severity: WARNING
Message: %s was interrupted while waiting for new work: %s. This should not happen, but the thread will resume waiting for new work so there should be no adverse effects.

Severity: WARNING
Message: An unexpected exception was caught while %s was waiting for new work: %s. This should not happen, but the thread will resume waiting for new work so there should be no adverse effects.

Severity: WARNING
Message: The work queue caught an exception while trying to cancel pending operation %s when the Directory Server was shutting down: %s.

Severity: INFO
Message: Server Error.

Severity: ERROR
Message: The Directory Server is currently running. The configuration may not be bootstrapped while the server is online.

Severity: ERROR
Message: The Directory Server may not be started before the configuration has been bootstrapped.

Severity: ERROR
Message: The Directory Server may not be started while it is already running. Please stop the running instance before attempting to start it again.

Severity: INFO
Message: The Directory Server is beginning the configuration bootstrapping process.

Severity: NOTICE
Message: %s (build %s, revision number %s) starting up.

Severity: NOTICE
Message: The Directory Server has started successfully.

Severity: ERROR
Message: An error occurred while attempting to create the JMX MBean server that will be used for monitoring, notification, and configuration interaction within the Directory Server: %s.

Severity: NOTICE
Message: The Directory Server has sent an alert notification generated by class %s (alert type %s, alert ID %s): %s.

Severity: ERROR
Message: An uncaught exception during processing for thread "%s" has caused it to terminate abnormally. The stack trace for that exception is: %s.

Severity: NOTICE
Message: The Directory Server has started the shutdown process. The shutdown was initiated by an instance of class %s and the reason provided for the shutdown was %s.

Severity: ERROR
Message: The Directory Server shutdown hook detected that the JVM is shutting down. This generally indicates that JVM received an external request to stop (e.g., through a kill signal).

Severity: ERROR
Message: An error occurred while trying to retrieve the root DSE configuration entry (cn=Root DSE,cn=config) from the Directory Server configuration: %s.

Severity: WARNING
Message: Entry "%s" contains a value "%s" for attribute %s that is invalid according to the syntax for that attribute: %s.

Severity: WARNING
Message: Entry "%s" does not contain any values for attribute "%s".

Severity: WARNING
Message: Entry "%s" does not contain any values for attribute "%s" with the specified set of options.

Severity: NOTICE
Message: The Directory Server is now stopped.

Severity: INFO
Message: %s has been stopped because the total number of worker threads in the Directory Server was reduced.

Severity: INFO
Message: Processing on this operation has been canceled because the Directory Server received a bind request on this connection, which requires that all operations in progress to be abandoned.

Severity: ERROR
Message: Unable to bind to the Directory Server because no such user exists in the server.

Severity: ERROR
Message: A fatal error occurred when executing one of the Directory Server startup plugins: %s (error ID %d). The Directory Server startup process has been aborted.

Severity: ERROR
Message: Unable to bind to the Directory Server using simple authentication because that user does not have a password.

Severity: ERROR
Message: Unable to process the bind request because it attempted to use an unknown SASL mechanism %s that is not available in the Directory Server.

Severity: ERROR
Message: The specified entry %s does not exist in the Directory Server.

Severity: INFO
Message: The operation was canceled because the client issued an abandon request (message ID %d) for this operation.

Severity: ERROR
Message: The provided entry cannot be added because it contains a null DN. This DN is reserved for the root DSE, and that entry may not be added over protocol.

Severity: ERROR
Message: The provided entry %s cannot be added because it does not have a parent and is not defined as one of the suffixes within the Directory Server.

Severity: ERROR
Message: Entry %s cannot be added because its parent entry %s does not exist in the server.

Severity: ERROR
Message: Entry %s cannot be added because the server failed to obtain a write lock for this entry after multiple attempts.

Severity: ERROR
Message: Entry %s cannot be removed because the server failed to obtain a write lock for this entry after multiple attempts.

Severity: ERROR
Message: The maximum time limit of %d seconds for processing this search operation has expired.

Severity: ERROR
Message: This search operation has sent the maximum of %d entries to the client.

Severity: ERROR
Message: The entry %s specified as the search base does not exist in the Directory Server.

Severity: ERROR
Message: Entry %s does not exist in the Directory Server.

Severity: ERROR
Message: Entry %s cannot be removed because the backend that should contain that entry has a subordinate backend with a base DN of %s that is below the target DN.

Severity: ERROR
Message: A modify DN operation cannot be performed on entry %s because the new RDN would not have a parent DN.

Severity: ERROR
Message: The modify DN operation for entry %s cannot be performed because no backend is registered to handle that DN.

Severity: ERROR
Message: The modify DN operation for entry %s cannot be performed because no backend is registered to handle the new DN %s.

Severity: ERROR
Message: The modify DN operation for entry %s cannot be performed because the backend holding the current entry is different from the backend used to handle the new DN %s. Modify DN operations may not span multiple backends.

Severity: ERROR
Message: The modify DN operation for entry %s cannot be performed because the server was unable to obtain a write lock for that DN.

Severity: ERROR
Message: The modify DN operation for entry %s cannot be performed because the server was unable to obtain a write lock for the new DN %s.

Severity: ERROR
Message: The modify DN operation for entry %s cannot be performed because that entry does not exist in the server.

Severity: ERROR
Message: Entry %s cannot be modified because the server failed to obtain a write lock for this entry after multiple attempts.

Severity: ERROR
Message: Entry %s cannot be modified because no such entry exists in the server.

Severity: ERROR
Message: Entry %s cannot be modified because the modification contained an add component for attribute %s but no values were provided.

Severity: ERROR
Message: When attempting to modify entry %s to add one or more values for attribute %s, value "%s" was found to be invalid according to the associated syntax: %s.

Severity: ERROR
Message: Entry %s cannot be modified because it would have resulted in one or more duplicate values for attribute %s: %s.

Severity: ERROR
Message: Entry %s cannot be modified because the change to attribute %s would have removed a value used in the RDN.

Severity: ERROR
Message: Entry %s cannot be modified because the attempt to update attribute %s would have removed one or more values from the attribute that were not present: %s.

Severity: ERROR
Message: Entry %s cannot be modified because an attempt was made to remove one or more values from attribute %s but this attribute is not present in the entry.

Severity: ERROR
Message: When attempting to modify entry %s to replace the set of values for attribute %s, value "%s" was found to be invalid according to the associated syntax: %s.

Severity: ERROR
Message: Entry %s cannot be modified because an attempt was made to increment the value of attribute %s which is used as an RDN attribute for the entry.

Severity: ERROR
Message: Entry %s cannot be modified because an attempt was made to increment the value of attribute %s but the request did not include a value for that attribute specifying the amount by which to increment the value.

Severity: ERROR
Message: Entry %s cannot be modified because an attempt was made to increment the value of attribute %s but the request contained multiple values, where only a single integer value is allowed.

Severity: ERROR
Message: Entry %s cannot be modified because an attempt was made to increment the value of attribute %s but that attribute did not have any values in the target entry.

Severity: ERROR
Message: Entry %s cannot be modified because an attempt was made to increment the value of attribute %s but the value "%s" could not be parsed as an integer.

Severity: ERROR
Message: Entry %s cannot be modified because the resulting entry would have violated the server schema: %s.

Severity: ERROR
Message: There is no extended operation handler registered with the Directory Server for handling extended operations with a request OID of %s.

Severity: ERROR
Message: An unexpected error was encountered while processing a search in one of the Directory Server backends: %s.

Severity: ERROR
Message: The modify DN operation for entry %s cannot be performed because the change would have violated the server schema: %s.

Severity: ERROR
Message: Object class %s cannot be added to entry %s because that class is not defined in the Directory Server schema.

Severity: ERROR
Message: The password provided by the user did not match any password(s) stored in the user’s entry.

Severity: INFO
Message: Display general system information.

Severity: ERROR
Message: An error occurred while attempting to parse the provided set of command line arguments: %s.

Severity: ERROR
Message: An error occurred while attempting to bootstrap the Directory Server: %s.

Severity: ERROR
Message: An error occurred while trying to start the Directory Server: %s.

Severity: ERROR
Message: The attempt to obtain a shared lock on file %s was rejected because an exclusive lock was already held on that file.

Severity: ERROR
Message: The attempt to obtain a shared lock on file %s was rejected because the attempt to create the lock file failed: %s.

Severity: ERROR
Message: The attempt to obtain a shared lock on file %s was rejected because the attempt to open the lock file failed: %s.

Severity: ERROR
Message: The attempt to obtain a shared lock on file %s was rejected because an error occurred while attempting to acquire the lock: %s.

Severity: ERROR
Message: The shared lock requested for file %s was not granted, which indicates that another process already holds an exclusive lock on that file.

Severity: ERROR
Message: The attempt to obtain an exclusive lock on file %s was rejected because an exclusive lock was already held on that file.

Severity: ERROR
Message: The attempt to obtain an exclusive lock on file %s was rejected because a shared lock was already held on that file.

Severity: ERROR
Message: The attempt to obtain an exclusive lock on file %s was rejected because the attempt to create the lock file failed: %s.

Severity: ERROR
Message: The attempt to obtain an exclusive lock on file %s was rejected because the attempt to open the lock file failed: %s.

Severity: ERROR
Message: The attempt to obtain an exclusive lock on file %s was rejected because an error occurred while attempting to acquire the lock: %s.

Severity: ERROR
Message: The exclusive lock requested for file %s was not granted, which indicates that another process already holds a shared or exclusive lock on that file.

Severity: ERROR
Message: The attempt to release the exclusive lock held on %s failed: %s.

Severity: ERROR
Message: The attempt to release the shared lock held on %s failed: %s.

Severity: ERROR
Message: The attempt to release the lock held on %s failed because no record of a lock on that file was found.

Severity: WARNING
Message: An error occurred while attempting to release a shared lock for backend %s: %s. This lock should be automatically cleaned when the Directory Server process exits, so no additional action should be necessary.

Severity: ERROR
Message: The Directory Server could not acquire an exclusive lock on file %s: %s. This generally means that another instance of this server is already running.

Severity: ERROR
Message: Entry %s cannot be modified because the modification attempted to update attribute %s which is defined as NO-USER-MODIFICATION in the server schema.

Severity: ERROR
Message: Entry %s cannot be added because it includes attribute %s which is defined as NO-USER-MODIFICATION in the server schema.

Severity: ERROR
Message: Entry %s cannot be renamed because the current DN includes attribute %s which is defined as NO-USER-MODIFICATION in the server schema and the deleteOldRDN flag was set in the modify DN request.

Severity: ERROR
Message: Entry %s cannot be renamed because the new RDN includes attribute %s which is defined as NO-USER-MODIFICATION in the server schema, and the target value for that attribute is not already included in the entry.

Severity: ERROR
Message: The modify DN operation for entry %s cannot be performed because a pre-operation plugin modified the entry in a way that caused it to violate the server schema: %s.

Severity: ERROR
Message: Entry %s cannot be modified because the request contained an LDAP assertion control and the associated filter did not match the contents of the entry.

Severity: ERROR
Message: Entry %s cannot be modified because the request contained a critical control with OID %s that is not supported by the Directory Server for this type of operation.

Severity: ERROR
Message: Entry %s cannot be removed because the request contained an LDAP assertion control and the associated filter did not match the contents of the entry.

Severity: ERROR
Message: Entry %s cannot be removed because the request contained a critical control with OID %s that is not supported by the Directory Server for this type of operation.

Severity: ERROR
Message: Entry %s cannot be renamed because the request contained an LDAP assertion control and the associated filter did not match the contents of the entry.

Severity: ERROR
Message: Entry %s cannot be renamed because the request contained a critical control with OID %s that is not supported by the Directory Server for this type of operation.

Severity: ERROR
Message: Entry %s cannot be added because the request contained an LDAP assertion control and the associated filter did not match the contents of the provided entry.

Severity: ERROR
Message: Entry %s cannot be added because the request contained a critical control with OID %s that is not supported by the Directory Server for this type of operation.

Severity: ERROR
Message: The search request cannot be processed because it contains an LDAP assertion control and an error occurred while trying to retrieve the base entry to compare it against the assertion filter: %s.

Severity: ERROR
Message: The search request cannot be processed because it contains an LDAP assertion control but the search base entry does not exist.

Severity: ERROR
Message: The search request cannot be processed because it contains an LDAP assertion control and the assertion filter did not match the contents of the base entry.

Severity: ERROR
Message: The search request cannot be processed because it contains a critical control with OID %s that is not supported by the Directory Server for this type of operation.

Severity: ERROR
Message: Cannot perform the compare operation on entry %s because the request contained an LDAP assertion control and the associated filter did not match the contents of the entry.

Severity: ERROR
Message: Cannot perform the compare operation on entry %s because the request contained a critical control with OID %s that is not supported by the Directory Server for this type of operation.

Severity: INFO
Message: The add operation was not actually performed in the Directory Server backend because the LDAP no-op control was present in the request.

Severity: INFO
Message: The delete operation was not actually performed in the Directory Server backend because the LDAP no-op control was present in the request.

Severity: INFO
Message: The modify operation was not actually performed in the Directory Server backend because the LDAP no-op control was present in the request.

Severity: INFO
Message: The modify DN operation was not actually performed in the Directory Server backend because the LDAP no-op control was present in the request.

Severity: ERROR
Message: Entry %s cannot be added because it is missing attribute %s that is contained in the entry’s RDN. All attributes used in the RDN must also be provided in the attribute list for the entry.

Severity: ERROR
Message: Unable to process the bind request because it contained a control with OID %s that was marked critical but this control is not supported for the bind operation.

Severity: WARNING
Message: There are multiple user-specific size limit values contained in user entry %s. The default server size limit will be used.

Severity: WARNING
Message: The user-specific size limit value %s contained in user entry %s could not be parsed as an integer. The default server size limit will be used.

Severity: WARNING
Message: There are multiple user-specific time limit values contained in user entry %s. The default server time limit will be used.

Severity: WARNING
Message: The user-specific time limit value %s contained in user entry %s could not be parsed as an integer. The default server time limit will be used.

Severity: ERROR
Message: An error occurred during preoperation synchronization processing for the add operation with connection ID %d and operation ID %d: %s.

Severity: ERROR
Message: An error occurred during postoperation synchronization processing for the add operation with connection ID %d and operation ID %d: %s.

Severity: ERROR
Message: An error occurred during preoperation synchronization processing for the delete operation with connection ID %d and operation ID %d: %s.

Severity: ERROR
Message: An error occurred during postoperation synchronization processing for the delete operation with connection ID %d and operation ID %d: %s.

Severity: ERROR
Message: An error occurred during preoperation synchronization processing for the modify operation with connection ID %d and operation ID %d: %s.

Severity: ERROR
Message: An error occurred during postoperation synchronization processing for the modify operation with connection ID %d and operation ID %d: %s.

Severity: ERROR
Message: An error occurred during preoperation synchronization processing for the modify DN operation with connection ID %d and operation ID %d: %s.

Severity: ERROR
Message: An error occurred during postoperation synchronization processing for the modify DN operation with connection ID %d and operation ID %d: %s.

Severity: ERROR
Message: An error occurred during conflict resolution synchronization processing for the add operation with connection ID %d and operation ID %d: %s.

Severity: ERROR
Message: An error occurred during conflict resolution synchronization processing for the delete operation with connection ID %d and operation ID %d: %s.

Severity: ERROR
Message: An error occurred during conflict resolution synchronization processing for the modify operation with connection ID %d and operation ID %d: %s.

Severity: ERROR
Message: An error occurred during conflict resolution synchronization processing for the modify DN operation with connection ID %d and operation ID %d: %s.

Severity: ERROR
Message: Unable to add entry %s because the Directory Server is configured in read-only mode.

Severity: ERROR
Message: Unable to add entry %s because the backend that should hold that entry is configured in read-only mode.

Severity: ERROR
Message: Unable to delete entry %s because the Directory Server is configured in read-only mode.

Severity: ERROR
Message: Unable to delete entry %s because the backend that holds that entry is configured in read-only mode.

Severity: ERROR
Message: Unable to modify entry %s because the Directory Server is configured in read-only mode.

Severity: ERROR
Message: Unable to modify entry %s because the backend that holds that entry is configured in read-only mode.

Severity: ERROR
Message: Unable to rename entry %s because the Directory Server is configured in read-only mode.

Severity: ERROR
Message: Unable to rename entry %s because the backend that holds that entry is configured in read-only mode.

Severity: ERROR
Message: Unable to process the simple bind request because it contained a bind DN but no password, which is forbidden by the server configuration.

Severity: ERROR
Message: The password policy definition contained in configuration entry "%s" is invalid because the specified password attribute "%s" is not defined in the server schema.

Severity: ERROR
Message: The password policy definition contained in configuration entry "%s" is invalid because the specified password attribute "%s" has a syntax OID of %s. The password attribute must have a syntax OID of either 1.3.6.1.4.1.26027.1.3.1 (for the user password syntax) or 1.3.6.1.4.1.4203.1.1.2 (for the authentication password syntax).

Severity: ERROR
Message: An error occurred while attempting to determine the value for attribute ds-cfg-require-change-by-time in configuration entry %s: %s.

Severity: ERROR
Message: The password policy definition contained in configuration entry "%s" is invalid because the specified last login time format "%s" is not a valid format string The last login time format string should conform to the syntax described in the API documentation for the 'java.text.SimpleDateFormat' class.

Severity: ERROR
Message: The password policy definition contained in configuration entry "%s" is invalid because the specified previous last login time format "%s" is not a valid format string The previous last login time format strings should conform to the syntax described in the API documentation for the 'java.text.SimpleDateFormat' class.

Severity: ERROR
Message: Attribute options are not allowed for the password attribute %s.

Severity: ERROR
Message: Only a single value may be provided for the password attribute %s.

Severity: ERROR
Message: Pre-encoded passwords are not allowed for the password attribute %s.

Severity: ERROR
Message: The password value for attribute %s was found to be unacceptable: %s.

Severity: ERROR
Message: The password policy defined in configuration entry %s is configured to always send at least one warning notification before the password is expired, but no warning interval has been set. If configuration attribute ds-cfg-expire-passwords-without-warning is set to "false", then configuration attribute ds-cfg-password-expiration-warning-interval must have a positive value.

Severity: ERROR
Message: A bind operation is currently in progress on the associated client connection. No other requests may be made on this client connection until the bind processing has completed.

Severity: ERROR
Message: A StartTLS operation is currently in progress on the associated client connection. No other requests may be made on this client connection until the StartTLS processing has completed.

Severity: ERROR
Message: A SASL bind operation is currently in progress on the associated client connection. No other requests may be made on this client connection until the SASL bind processing has completed.

Severity: ERROR
Message: %s must change their password before it will be allowed to request any other operations.

Severity: ERROR
Message: An error occurred while attempting to decode the ds-pwp-password-policy-dn value "%s" in user entry "%s" as a DN: %s.

Severity: ERROR
Message: User entry %s is configured to use a password policy subentry of %s but no such password policy has been defined in the server configuration.

Severity: ERROR
Message: An error occurred while attempting to decode value "%s" for attribute %s in user entry %s in accordance with the generalized time format: %s.

Severity: ERROR
Message: Unable to decode value "%s" for attribute %s in user entry %s as a Boolean value.

Severity: ERROR
Message: The entry %s cannot be added due to insufficient access rights.

Severity: ERROR
Message: The user cannot bind due to insufficient access rights.

Severity: ERROR
Message: The entry %s cannot be compared due to insufficient access rights.

Severity: ERROR
Message: The entry %s cannot be deleted due to insufficient access rights.

Severity: ERROR
Message: The extended operation %s cannot be performed due to insufficient access rights.

Severity: ERROR
Message: The entry %s cannot be renamed due to insufficient access rights.

Severity: ERROR
Message: The entry %s cannot be modified due to insufficient access rights.

Severity: ERROR
Message: The entry %s cannot be searched due to insufficient access rights.

Severity: ERROR
Message: Rejecting a simple bind request because the password policy requires secure authentication.

Severity: ERROR
Message: Rejecting a bind request because the account has been administratively disabled.

Severity: ERROR
Message: Rejecting a bind request because the account has been locked due to too many failed authentication attempts.

Severity: ERROR
Message: Rejecting a bind request because the account has been locked after the user’s password was not changed in a timely manner after an administrative reset.

Severity: ERROR
Message: Rejecting a bind request because the account has been locked after remaining idle for too long.

Severity: ERROR
Message: Rejecting a bind request because that user’s password is expired.

Severity: ERROR
Message: An error occurred while attempting to update password policy state information for user %s: %s.

Severity: ERROR
Message: Rejecting a SASL %s bind request for user %s because the password policy requires secure authentication.

Severity: ERROR
Message: Rejecting a bind request because the account has expired.

Severity: ERROR
Message: Attributes used to hold user passwords are not allowed to have any attribute options.

Severity: ERROR
Message: Users are not allowed to change their own passwords.

Severity: ERROR
Message: Password changes must be performed over a secure authentication channel.

Severity: ERROR
Message: The password cannot be changed because it has not been long enough since the last password change.

Severity: ERROR
Message: Multiple password values are not allowed in user entries.

Severity: ERROR
Message: User passwords may not be provided in pre-encoded form.

Severity: ERROR
Message: Invalid modification type %s attempted on password attribute %s.

Severity: ERROR
Message: The user entry does not have any existing passwords to remove.

Severity: ERROR
Message: The provided user password does not match any password in the user’s entry.

Severity: ERROR
Message: The password policy requires that user password changes include the current password in the request.

Severity: ERROR
Message: The password change would result in multiple password values in the user entry, which is not allowed.

Severity: ERROR
Message: The provided password value was rejected by a password validator: %s.

Severity: ERROR
Message: %s must change their password before it will be allowed to perform any other operations.

Severity: WARNING
Message: The user password is about to expire (time to expiration: %s).

Severity: ERROR
Message: The account has been locked as a result of too many failed authentication attempts (time to unlock: %s).

Severity: ERROR
Message: The account has been locked as a result of too many failed authentication attempts. It may only be unlocked by an administrator.

Severity: INFO
Message: The user password has been changed.

Severity: INFO
Message: The user password has been administratively reset.

Severity: INFO
Message: The user account has been administratively enabled.

Severity: INFO
Message: The user account has been administratively disabled.

Severity: INFO
Message: The user account has been administratively unlocked.

Severity: ERROR
Message: The specified password value already exists in the user entry.

Severity: ERROR
Message: Entry %s cannot be updated because the request did not contain any modifications.

Severity: INFO
Message: Do not detach from the terminal and continue running in the foreground. This option cannot be used with the -t, --timeout option.

Severity: INFO
Message: This utility can be used to start the Directory Server, as well as to obtain the server version and other forms of general server information.

Severity: ERROR
Message: Unable to process the request for extended operation %s because it contained an unsupported critical control with OID %s.

Severity: ERROR
Message: Unable to register backend %s with the Directory Server because another backend with the same backend ID is already registered.

Severity: ERROR
Message: Unable to register base DN %s with the Directory Server for backend %s because that base DN is already registered for backend %s.

Severity: ERROR
Message: Unable to register base DN %s with the Directory Server for backend %s because that backend already contains another base DN %s that is within the same hierarchical path.

Severity: ERROR
Message: Unable to register base DN %s with the Directory Server for backend %s because that backend already contains another base DN %s that is not subordinate to the same base DN in the parent backend.

Severity: ERROR
Message: Unable to register base DN %s with the Directory Server for backend %s because that backend already contains one or more other base DNs that are subordinate to backend %s but the new base DN is not.

Severity: WARNING
Message: Backend %s already contains entry %s which has just been registered as the base DN for backend %s. These conflicting entries can cause unexpected or errant search results, and both backends should be reinitialized to ensure that each has the correct content.

Severity: ERROR
Message: Unable to de-register base DN %s with the Directory Server because that base DN is not registered for any active backend.

Severity: WARNING
Message: Base DN %s has been deregistered from the Directory Server for backend %s. This base DN had both superior and subordinate entries in other backends, and there might be inconsistent or unexpected behavior when accessing entries in this portion of the hierarchy because of the missing entries that had been held in the de-registered backend.

Severity: ERROR
Message: Rejecting the requested operation because the connection has not been authenticated.

Severity: WARNING
Message: Entry "%s" cannot be added because it contains attribute type %s which is declared OBSOLETE in the server schema.

Severity: WARNING
Message: Entry "%s" cannot be added because it contains objectclass %s which is declared OBSOLETE in the server schema.

Severity: ERROR
Message: Entry %s cannot be modified because the modification attempted to set one or more new values for attribute %s which is marked OBSOLETE in the server schema.

Severity: ERROR
Message: Object class %s added to entry %s is marked OBSOLETE in the server schema.

Severity: ERROR
Message: The modify DN operation for entry %s cannot be performed because the new RDN includes attribute type %s which is declared OBSOLETE in the server schema.

Severity: WARNING
Message: Terminating the client connection because its associated authentication or authorization entry %s has been deleted.

Severity: ERROR
Message: You do not have sufficient privileges to reset user passwords.

Severity: ERROR
Message: You do not have sufficient privileges to access the server configuration.

Severity: ERROR
Message: You do not have sufficient privileges to add entries that include privileges.

Severity: ERROR
Message: You do not have sufficient privileges to modify the set of privileges contained in an entry.

Severity: ERROR
Message: You do not have sufficient privileges to use the proxied authorization control.

Severity: ERROR
Message: OpenDJ is configured to run as a Windows service and it cannot run in no-detach mode.

Severity: ERROR
Message: Unable to decode an entry because it had an unsupported entry version byte value of %s.

Severity: ERROR
Message: Unable to decode an entry because an unexpected exception was caught during processing: %s.

Severity: ERROR
Message: The request control with Object Identifier (OID) "%s" cannot be used due to insufficient access rights.

Severity: ERROR
Message: The connection handler %s is trying to use the listener %s which is already in use by another connection handler.

Severity: ERROR
Message: No enabled connection handler available.

Severity: ERROR
Message: Could not start connection handlers.

Severity: ERROR
Message: Unable to process the non-root bind because the server is in lockdown mode.

Severity: WARNING
Message: The Directory Server is entering lockdown mode, in which clients will only be allowed to connect via a loopback address, and only root users will be allowed to process operations.

Severity: NOTICE
Message: The Directory Server is leaving lockdown mode and will resume normal operation.

Severity: NOTICE
Message: Rejecting the requested operation because the server is in lockdown mode and will only accept requests from root users over loopback connections.

Severity: ERROR
Message: Unable to decode the provided attribute because it used an undefined attribute description token %s.

Severity: ERROR
Message: Unable to decode the provided object class set because it used an undefined token %s.

Severity: ERROR
Message: Unable to decode the provided entry encode configuration element because it has an invalid length.

Severity: ERROR
Message: Rejecting a bind request for user %s because either the entire server or the user’s backend has a writability mode of 'disabled' and password policy state updates would not be allowed.

Severity: ERROR
Message: The provided new password was found in the password history for the user.

Severity: WARNING
Message: There are multiple user-specific idle time limit values contained in user entry %s. The default server idle time limit will be used.

Severity: WARNING
Message: The user-specific idle time limit value %s contained in user entry %s could not be parsed as an integer. The default server idle time limit will be used.

Severity: INFO
Message: This connection has been terminated because it has remained idle for too long.

Severity: ERROR
Message: The password policy configuration entry "%s" is invalid because if a maximum password age is configured, then the password expiration warning interval must be shorter than the maximum password age.

Severity: ERROR
Message: The password policy configuration entry "%s" is invalid because if both a minimum password age and a maximum password age are configured, then the sum of the minimum password age and the password expiration warning interval must be shorter than the maximum password age.

Severity: ERROR
Message: An error occurred while attempting to disconnect client connection %d: %s.

Severity: ERROR
Message: The Directory Server is currently running. Environment configuration changes are not allowed with the server running.

Severity: ERROR
Message: The specified server root directory '%s' is invalid. The specified path must exist and must be a directory.

Severity: ERROR
Message: The specified config file path '%s' is invalid. The specified path must exist and must be a file.

Severity: ERROR
Message: The specified schema configuration directory '%s' is invalid. The specified path must exist and must be a directory.

Severity: ERROR
Message: The Directory Server is currently running. The environment configuration can not be altered while the server is online.

Severity: ERROR
Message: An error occurred while attempting to initialize a SSL context for server to server communication: %s.

Severity: INFO
Message: Attempt to start using the configuration that was in place at the last successful startup (if it is available) rather than using the current active configuration.

Severity: INFO
Message: Error while searching base %s to synchronize the trust store: %s.

Severity: ERROR
Message: An error occurred in the trust store synchronization thread: %s.

Severity: INFO
Message: Error while trying to add entry %s to the trust store: %s.

Severity: ERROR
Message: The password storage scheme defined in configuration entry %s does not support the auth password syntax, which is used by password attribute %s.

Severity: ERROR
Message: Password policy configuration entry %s references deprecated password storage scheme DN %s which does not support the auth password syntax.

Severity: WARNING
Message: The search filter "%s" used by group implementation %s is not indexed in backend %s. Backend initialization for this group implementation might take a very long time to complete.

Severity: ERROR
Message: CryptoManager cannot get the requested digest %s: %s.

Severity: ERROR
Message: CryptoManager cannot get the requested MAC engine %s: %s.

Severity: ERROR
Message: CryptoManager cannot get the requested encryption cipher %s: %s.

Severity: ERROR
Message: CryptoManager cannot get the preferred key wrapping cipher: %s.

Severity: ERROR
Message: CryptoManager failed to retrieve the collection of instance-key-pair public-key-certificates from ADS container "%s": %s.

Severity: ERROR
Message: CryptoManager failed to encode symmetric key attribute value: %s.

Severity: ERROR
Message: CryptoManager symmetric key attribute value "%s" syntax is invalid: incorrect number of fields.

Severity: ERROR
Message: CryptoManager symmetric key attribute value "%s" syntax is invalid. Parsing failed in field "%s" at offset %d.

Severity: ERROR
Message: CryptoManager failed to decipher the wrapped secret-key value: %s.

Severity: ERROR
Message: CryptoManager cannot find the public-key-certificate (identifier "%s") requested for symmetric key re-encoding.

Severity: ERROR
Message: CryptoManager failed to decode the key entry identifier "%s": %s.

Severity: ERROR
Message: CrytpoManager passed invalid MAC algorithm "%s": %s.

Severity: ERROR
Message: CryptoManager failed to initialize MAC engine: %s.

Severity: ERROR
Message: CryptoManager passed invalid Cipher transformation "%s": %s.

Severity: ERROR
Message: CryptoManager cannot initialize Cipher: %s.

Severity: ERROR
Message: CryptoManager failed to write the stream prologue: %s.

Severity: ERROR
Message: CryptoManager failed to decrypt the supplied data because it could not read the symmetric key identifier in the data prologue: %s.

Severity: ERROR
Message: CryptoManager failed to decrypt the supplied data because the symmetric key identifier in the data prologue does not match any known key entries.

Severity: ERROR
Message: CryptoManager failed to decrypt the supplied data because it could not read the cipher initialization vector in the data prologue.

Severity: ERROR
Message: CryptoManager failed to decrypt the supplied data because there was an error reading from the input stream: %s.

Severity: ERROR
Message: CryptoManager failed to import the symmetric key entry "%s" because it could not obtain a symmetric key attribute value that can be decoded by this instance.

Severity: ERROR
Message: CryptoManager detected a field mismatch between the key entry to be imported and an entry in the key cache that share the key identifier "%s".

Severity: ERROR
Message: CryptoManager failed to import the symmetric key entry "%s": %s.

Severity: ERROR
Message: CryptoManager failed to import the symmetric key entry "%s" because it could not add a symmetric key attribute value that can be decoded by this instance.

Severity: ERROR
Message: CryptoManager failed to instantiate a KeyGenerator for algorithm "%s": %s.

Severity: ERROR
Message: CryptoManager failed to add locally produced symmetric key entry "%s": %s.

Severity: ERROR
Message: CryptoManager cipher transformation specification "%s" is invalid: it must be of the form "algorithm/mode/padding".

Severity: ERROR
Message: CryptoManager cipher transformation specification "%s" is invalid: it must be of the form "algorithm/mode/padding".

Severity: ERROR
Message: CryptoManager failed to decrypt the supplied data because it could not read the version number in the data prologue: %s.

Severity: ERROR
Message: CryptoManager failed to decrypt the supplied data because the version "%d" in the data prologue is unknown.

Severity: ERROR
Message: CryptoManager failed to sign the wrapped key entry: %s.

Severity: ERROR
Message: The wrapped key entry is missing the following attributes: %s.

Severity: ERROR
Message: CryptoManager failed to find the master key pair with ID '%s', make sure cryptoManager has access to the master key pair that was used at the time of wrapping the key.

Severity: ERROR
Message: The wrapped key entry signature does not match the entry content.

Severity: ERROR
Message: CryptoManager failed to verify the wrapped key entry signature: %s.

Severity: ERROR
Message: The provided entry %s cannot be added because its suffix is not defined as one of the suffixes within the Directory Server.

Severity: NOTICE
Message: %s.

Severity: NOTICE
Message: Build ID: %s.

Severity: ERROR
Message: Start TLS extended operations cannot be canceled.

Severity: ERROR
Message: Cancel extended operations can not be canceled.

Severity: ERROR
Message: The modify DN operation for entry %s cannot be performed because the new superior entry %s is equal to or a subordinate of the entry to be moved.

Severity: INFO
Message: Unable to process operation because this search scope is not allowed in this network group.

Severity: ERROR
Message: Entry %s can not be added because BER encoding of %s attribute is not supported.

Severity: INFO
Message: No worker queue thread pool size specified: sizing automatically to use %d threads.

Severity: INFO
Message: Maximum time (in seconds) to wait before the command returns (the server continues the startup process, regardless). A value of '0' indicates an infinite timeout, which means that the command returns only when the server startup is completed. The default value is 60 seconds. This option cannot be used with the -N, --nodetach option.

Severity: ERROR
Message: In no-detach mode, the 'timeout' option cannot be used.

Severity: WARNING
Message: The search filter "%s" used by subentry manager is not indexed in backend %s. Backend initialization for subentry manager processing might take a very long time to complete.

Severity: ERROR
Message: The subentry %s must have either the pwdPolicy or ds-pwp-password-policy objectclasses, which is required for the Directory Server password policy.

Severity: ERROR
Message: CryptoManager failed to initialize because the specified cipher key length "%d" is beyond the allowed cryptography strength "%d" in jurisdiction policy files.

Severity: ERROR
Message: Failed to update free disk space for directory %s: %s.

Severity: ERROR
Message: The directory server is not accepting a new persistent search request because the server has already reached its limit.

Severity: ERROR
Message: This operation involves LDAP subentries which you do not have sufficient privileges to administer.

Severity: INFO
Message: Invalid Credentials.

Severity: WARNING
Message: Entry "%s" contains a value for attribute %s that is invalid according to the syntax for that attribute: %s.

Severity: ERROR
Message: When attempting to modify entry %s, one value for attribute %s was found to be invalid according to the associated syntax: %s.

Severity: ERROR
Message: When attempting to modify entry %s to replace the set of values for attribute %s, one value was found to be invalid according to the associated syntax: %s.

Severity: ERROR
Message: The password policy definition contained in configuration entry "%s" is invalid because the password validator "%s" specified in attribute "%s" cannot be found.

Severity: ERROR
Message: The password could not be validated because of misconfiguration. Please contact the administrator.

Severity: ERROR
Message: The password for user %s could not be validated because the password policy subentry %s is referring to an unknown password validator (%s). Please make sure the password policy subentry only refers to validators that exist on all replicas.

Severity: ERROR
Message: Could not get filesystem for directory %s: %s.

Severity: ERROR
Message: The free space (%s) on the disk containing directory "%s" is between low and full threshold for the following subsystems: %s. Write operations are only permitted by a user with the BYPASS_LOCKDOWN privilege until the free space rises above the threshold. Replication updates are still allowed.

Severity: ERROR
Message: The free space (%s) on the disk containing directory "%s" is below full threshold for the following subsystems: %s. Write operations to the backend, replication updates included, will fail until the free space rises above the threshold.

Severity: NOTICE
Message: The free space (%s) on the disk containing directory "%s" is now above the low threshold for the following subsystems: %s.

Severity: ERROR
Message: Cannot properly use SHA-1 using the java provider. Verify java.security is properly configured.

Severity: ERROR
Message: Cannot complete initialization of server’s backends because the root and administrative backends have not been initialized yet.

Severity: ERROR
Message: An error occurred while adding Service Discovery Mechanism '%s': %s.

Severity: ERROR
Message: Registering Service Discovery Manager’s listener failed : %s.

Severity: ERROR
Message: Discovery mechanism '%s' initialization failed : %s.

Severity: WARNING
Message: Replication server '%s' references server '%s' that could not be parsed correctly; the definition will be skipped.

Severity: ERROR
Message: Error occurred while creating an SSL context for service discovery mechanism '%s' : %s.

Severity: ERROR
Message: Could not retrieve the list of replicas from replication server '%s' for replication server group '%s'. Exception : %s.

Severity: ERROR
Message: Could not retrieve auto-configuration data from directory server '%s' for replication server group '%s'. Exception : %s".

Severity: ERROR
Message: Service discovery mechanism '%s' failed to refresh the partition information. Exception : %s",.

Severity: WARNING
Message: Settings for Replica '%s' should provide a hostname.

Severity: WARNING
Message: Cannot connect to replica '%s' for replication service discovery mechanism '%s'. The replica entry is: %s.

Severity: WARNING
Message: Cannot gather naming contexts from server %s: %s.

Severity: WARNING
Message: Scheduled discovery '%s' failed : %s.

Severity: ERROR
Message: Service discovery mechanism '%s' failed to refresh the connection options. Exception : %s",.

Severity: ERROR
Message: "%s" (low=%s, full=%s).

Severity: ERROR
Message: You do not have sufficient privileges to read directory server monitoring information.

Severity: WARNING
Message: There are multiple user-specific cursor entry limit values contained in user entry '%s'. The default server cursor entry limit will be used.

Severity: WARNING
Message: The user-specific cursor entry limit value '%s' contained in user entry '%s' could not be parsed as an integer. The default server cursor entry limit will be used.

Severity: ERROR
Message: Entry %s cannot be added because its parent entry %s is a subentry.

Severity: INFO
Message: Server in lockdown mode.

Severity: ERROR
Message: The master key with alias '%s' does not exist in the '%s' key manager. Please check that the correct key manager has been configured and that it contains the specified master keys.

Severity: ERROR
Message: The CryptoManager could not encode a symmetric because the master key with alias '%s' does not exist in the '%s' key manager. Please check that the correct key manager has been configured and that it contains the specified master keys.

Severity: ERROR
Message: The CryptoManager could was not able to obtain the deployment’s pepper. Please check that the CryptoManager has a correctly configured key manager and preferred digest mechanism.

Severity: ERROR
Message: No enabled password storage schemes in '%s' in subentry '%s'.

Severity: ERROR
Message: Cannot use both pwdValidatorPolicy and ds-pwp-validator in subentry '%s'.

Severity: ERROR
Message: The dictionary data could not be decompressed: %s.

Severity: ERROR
Message: The dictionary validator configuration is invalid.

Severity: WARNING
Message: Found %d conflicting password policy subentries for user %s, used %s.

Severity: ERROR
Message: Requested cipher for a non existing cipher key: cryptographic services were not properly initialized, programming error.

Severity: ERROR
Message: Type %d is not a valid secret key type. The Valid type is '0' for a cipher key. Secret key initialization cannot continue, check the data source and re-initialize if needed.

Severity: ERROR
Message: The subentry %s cannot use both %s and %s objectclasses.

Severity: ERROR
Message: The subentry %s using the %s objectclass cannot define validators using the old %s objectclass.

Severity: ERROR
Message: The subentry %s using the %s objectclass cannot define validators using the new %s objectclass.

Severity: ERROR
Message: The value for the '%s' attribute is not a valid duration.

Severity: ERROR
Message: The value for the '%s' attribute is not a valid integer.

Severity: ERROR
Message: The value for the '%s' attribute is not a valid boolean.

Severity: ERROR
Message: The value for the '%s' attribute is not a valid time.

Severity: ERROR
Message: The value for the '%s' attribute is not a valid string.

Severity: ERROR
Message: The value for the '%s' attribute is not a valid attribute.

Severity: ERROR
Message: The values for the '%s' attribute are not valid strings.

Severity: ERROR
Message: The value for the '%s' attribute is not a valid state update failure policy.

Severity: ERROR
Message: A values for the '%s' attribute is not a valid attribute name.

Severity: ERROR
Message: Could not start connection handler %s with listen addresses "%s". The error was: %s.

Severity: INFO
Message: Registered %d static groups, %d dynamic groups and %d virtual static groups. The static group cache is using %d bytes of memory.

Severity: INFO
Message: The following logging categories are defined for the server: %s.

Severity: ERROR
Message: An error occurred while attempting to initialize the message digest generator for the %s algorithm: %s.

Severity: ERROR
Message: An error occurred while attempting to base64-decode the password value %s: %s.

Severity: ERROR
Message: The %s password storage scheme is not reversible, so it is impossible to recover the plaintext version of an encoded password.

Severity: ERROR
Message: An error occurred while trying to register the JMX alert handler with the MBean server: %s.

Severity: ERROR
Message: An unexpected error occurred while attempting to encode a password using the storage scheme defined in class %s: %s.

Severity: ERROR
Message: The ds-cfg-include-filter attribute of configuration entry %s, which specifies a set of search filters that may be used to control which entries are included in the cache, has an invalid value of "%s": %s.

Severity: ERROR
Message: The ds-cfg-exclude-filter attribute of configuration entry %s, which specifies a set of search filters that may be used to control which entries are excluded from the cache, has an invalid value of "%s": %s.

Severity: ERROR
Message: A fatal error occurred while trying to initialize fifo entry cache: %s.

Severity: ERROR
Message: A fatal error occurred while trying to initialize soft reference entry cache: %s.

Severity: ERROR
Message: An unexpected error occurred while attempting to decode the password modify extended request sequence: %s.

Severity: ERROR
Message: The password modify extended request cannot be processed because it does not contain an authorization ID and the underlying connection is not authenticated.

Severity: ERROR
Message: The password modify extended request cannot be processed because the server was unable to obtain a write lock on user entry %s after multiple attempts.

Severity: ERROR
Message: The password modify extended request cannot be processed because the server cannot decode "%s" as a valid DN for use in the authorization ID for the operation.

Severity: ERROR
Message: The password modify extended request cannot be processed because it contained an invalid userIdentity field. The provided userIdentity string was "%s".

Severity: ERROR
Message: The password modify extended request cannot be processed because it was not possible to identify the user entry to update based on the authorization DN of "%s".

Severity: ERROR
Message: The password modify extended operation cannot be processed because the current password provided for the user is invalid.

Severity: ERROR
Message: The keystore file %s specified in attribute ds-cfg-key-store-file of configuration entry %s does not exist.

Severity: ERROR
Message: An error occurred while trying to load the keystore contents from file %s: %s.

Severity: ERROR
Message: The keystore type %s specified in attribute ds-cfg-key-store-type of configuration entry %s is not valid: %s.

Severity: ERROR
Message: An error occurred while trying to access the PKCS#11 key manager: %s.

Severity: ERROR
Message: An error occurred while trying to create a key manager factory to access the contents of keystore file %s: %s.

Severity: ERROR
Message: An error occurred while trying to create a key manager factory to access the contents of the PKCS#11 keystore: %s.

Severity: ERROR
Message: The trust store file %s specified in attribute ds-cfg-trust-store-file of configuration entry %s does not exist.

Severity: ERROR
Message: An error occurred while trying to load the trust store contents from file %s: %s.

Severity: ERROR
Message: An error occurred while trying to create a trust manager factory to access the contents of trust store file %s: %s.

Severity: ERROR
Message: The trust store type %s specified in attribute ds-cfg-trust-store-type of configuration entry %s is not valid: %s.

Severity: ERROR
Message: Could not map the provided certificate chain to a user entry because no peer certificate was available.

Severity: ERROR
Message: Could not map the provided certificate chain to a user because the peer certificate was not an X.509 certificate (peer certificate format was %s).

Severity: ERROR
Message: Could not map the provided certificate chain to a user because the peer certificate subject "%s" could not be decoded as an LDAP DN: %s.

Severity: ERROR
Message: Could not map the provided certificate chain to a user because an error occurred while attempting to retrieve the user entry with DN "%s": %s.

Severity: ERROR
Message: Could not map the provided certificate chain to a user because no user entry exists with a DN of %s.

Severity: ERROR
Message: The SASL EXTERNAL bind request could not be processed because the associated bind request does not have a reference to the client connection.

Severity: ERROR
Message: The SASL EXTERNAL bind request could not be processed because the associated client connection instance is not an instance of LDAPClientConnection.

Severity: ERROR
Message: The SASL EXTERNAL bind request could not be processed because the client did not present a certificate chain during SSL/TLS negotiation.

Severity: ERROR
Message: The SASL EXTERNAL bind request failed because the certificate chain presented by the client during SSL/TLS negotiation could not be mapped to a user entry in the Directory Server.

Severity: ERROR
Message: StartTLS cannot be used on this connection because the underlying client connection is not available.

Severity: ERROR
Message: StartTLS cannot be used on this client connection because this connection type is not capable of using StartTLS to protect its communication.

Severity: ERROR
Message: Unable to authenticate via SASL EXTERNAL because the mapped user entry %s does not have any certificates with which to verify the presented peer certificate.

Severity: ERROR
Message: Unable to authenticate via SASL EXTERNAL because the mapped user entry %s did not contain the peer certificate presented by the client.

Severity: ERROR
Message: An error occurred while attempting to validate the peer certificate presented by the client with a certificate from the user’s entry %s: %s.

Severity: ERROR
Message: SASL PLAIN authentication requires that SASL credentials be provided but none were included in the bind request.

Severity: ERROR
Message: The SASL PLAIN bind request did not include any NULL characters. NULL characters are required as delimiters between the authorization ID and authentication ID, and also between the authentication ID and the password.

Severity: ERROR
Message: The SASL PLAIN bind request did not include a second NULL character in the credentials, which is required as a delimiter between the authentication ID and the password.

Severity: ERROR
Message: The authentication ID contained in the SASL PLAIN bind request had a length of zero characters, which is not allowed. SASL PLAIN authentication does not allow an empty string for use as the authentication ID.

Severity: ERROR
Message: The password contained in the SASL PLAIN bind request had a length of zero characters, which is not allowed. SASL PLAIN authentication does not allow an empty string for use as the password.

Severity: ERROR
Message: An error occurred while attempting to decode the SASL PLAIN authentication ID "%s" because it appeared to contain a DN but DN decoding failed: %s.

Severity: ERROR
Message: The authentication ID in the SASL PLAIN bind request appears to be an empty DN. This is not allowed.

Severity: ERROR
Message: An error occurred while attempting to retrieve user entry %s as specified in the DN-based authentication ID of a SASL PLAIN bind request: %s.

Severity: ERROR
Message: The server was not able to find any user entries for the provided authentication ID of %s.

Severity: ERROR
Message: The provided password is invalid.

Severity: INFO
Message: An unsupported or unexpected callback was provided to the SASL server for use during %s authentication: %s.

Severity: ERROR
Message: An unexpected error occurred while attempting to determine the value of the ds-cfg-server-fqdn attribute in configuration entry %s: %s.

Severity: ERROR
Message: An unexpected error occurred while trying to create an %s context: %s.

Severity: ERROR
Message: An error occurred while attempting to decode the SASL %s username "%s" because it appeared to contain a DN but DN decoding failed: %s.

Severity: ERROR
Message: The username in the SASL %s bind request appears to be an empty DN. This is not allowed.

Severity: ERROR
Message: An error occurred while attempting to retrieve user entry %s as specified in the DN-based username of a SASL %s bind request: %s.

Severity: ERROR
Message: The username contained in the SASL %s bind request had a length of zero characters, which is not allowed. %s authentication does not allow an empty string for use as the username.

Severity: ERROR
Message: The server was not able to find any user entries for the provided username of %s.

Severity: ERROR
Message: The provided authorization ID %s contained an invalid DN: %s.

Severity: ERROR
Message: The entry %s specified as the authorization identity does not exist.

Severity: ERROR
Message: The entry %s specified as the authorization identity could not be retrieved: %s.

Severity: ERROR
Message: The server was unable to find any entry corresponding to authorization ID %s.

Severity: ERROR
Message: An error occurred while attempting to retrieve the clear-text password(s) for user %s in order to perform SASL %s authentication: %s.

Severity: ERROR
Message: SASL %s authentication is not possible for user %s because none of the passwords in the user entry are stored in a reversible form.

Severity: ERROR
Message: SASL %s protocol error: %s.

Severity: ERROR
Message: The authenticating user %s does not have sufficient privileges to assume a different authorization identity.

Severity: ERROR
Message: The authenticating user %s does not have sufficient access to assume a different authorization identity.

Severity: ERROR
Message: The server was unable to find any entry corresponding to authentication ID %s.

Severity: ERROR
Message: The server was unable to because both the ds-cfg-kdc-address and ds-cfg-realm attributes must be defined or neither defined.

Severity: ERROR
Message: An error occurred while attempting to map authorization ID %s to a user entry: %s.

Severity: ERROR
Message: An error occurred while attempting to write a temporary JAAS configuration file for use during GSSAPI processing: %s.

Severity: ERROR
Message: An error occurred while attempting to create the JAAS login context for GSSAPI authentication: %s.

Severity: INFO
Message: GSSAPI mechanism using a principal name of: %s.

Severity: INFO
Message: GSSAPI SASL mechanism using a server fully qualified domain name of: %s.

Severity: INFO
Message: DIGEST-MD5 SASL mechanism using a realm of: %s.

Severity: NOTICE
Message: DIGEST-MD5 SASL mechanism using a server fully qualified domain name of: %s.

Severity: ERROR
Message: You do not have sufficient privileges to use the proxied authorization control.

Severity: ERROR
Message: ID string %s could not be mapped to exactly one user. It maps at least to both '%s' and '%s'.

Severity: ERROR
Message: The internal search based on ID string %s could not be processed efficiently: %s. Check the server configuration to ensure that all associated backends are properly configured for these types of searches.

Severity: ERROR
Message: An internal failure occurred while attempting to resolve ID string %s to a user entry: %s.

Severity: ERROR
Message: ID string %s mapped to multiple users.

Severity: ERROR
Message: An error occurred while attempting to map username %s to a Directory Server entry: %s.

Severity: ERROR
Message: An error occurred while attempting to map username %s to a Directory Server entry: %s.

Severity: ERROR
Message: Unable to process the cancel request because the extended operation did not include a request value.

Severity: ERROR
Message: An error occurred while attempting to decode the value of the cancel extended request: %s.

Severity: INFO
Message: Processing on this operation was terminated as a result of receiving a cancel request (message ID %d).

Severity: ERROR
Message: Password storage scheme %s does not support use with the authentication password attribute syntax.

Severity: ERROR
Message: The configured minimum password length of %d characters is greater than the configured maximum password length of %d.

Severity: ERROR
Message: The provided password is shorter than the minimum required length of %d characters.

Severity: ERROR
Message: The provided password is longer than the maximum allowed length of %d characters.

Severity: ERROR
Message: Configuration entry "%s" does not contain attribute ds-cfg-password-character-set which specifies the sets of characters that should be used when generating the password. This is a required attribute.

Severity: ERROR
Message: Configuration entry "%s" contains multiple definitions for the %s character set.

Severity: ERROR
Message: An error occurred while attempting to decode the value(s) of the configuration attribute ds-cfg-password-character-set, which is used to hold the character set(s) for use in generating the password: %s.

Severity: ERROR
Message: The password format string "%s" references an undefined character set "%s".

Severity: ERROR
Message: The password format string "%s" contains an invalid syntax. This value should be a comma-delimited sequence of elements, where each element is the name of a character set followed by a colon and the number of characters to choose at random from that character set.

Severity: ERROR
Message: An error occurred while attempting to decode the value for configuration attribute ds-cfg-password-format, which is used to specify the format for the generated passwords: %s.

Severity: ERROR
Message: An error occurred while attempting to get the password policy for user %s: %s.

Severity: ERROR
Message: The current password must be provided for self password changes.

Severity: ERROR
Message: Password modify operations that supply the user’s current password must be performed over a secure communication channel.

Severity: ERROR
Message: End users are not allowed to change their passwords.

Severity: ERROR
Message: Password changes must be performed over a secure communication channel.

Severity: ERROR
Message: The password cannot be changed because the previous password change was too recent.

Severity: ERROR
Message: The password cannot be changed because it is expired.

Severity: ERROR
Message: No new password was provided, and no password generator has been defined that may be used to automatically create a new password.

Severity: ERROR
Message: An error occurred while attempting to create a new password using the password generator: %s.

Severity: ERROR
Message: The password policy does not allow users to supply pre-encoded passwords.

Severity: ERROR
Message: The provided new password failed the validation checks defined in the server: %s.

Severity: ERROR
Message: Unable to encode the provided password using the default scheme(s): %s.

Severity: ERROR
Message: An error occurred while attempting to determine the identity mapper to use in conjunction with the password modify extended operation defined in configuration entry %s: %s. The password modify extended operation will not be enabled for use in the server.

Severity: ERROR
Message: The provided authorization ID string "%s" could not be mapped to any user in the directory.

Severity: ERROR
Message: An error occurred while attempting to map authorization ID string "%s" to a user entry: %s.

Severity: NOTICE
Message: Account-Status-Notification type='%s' userdn='%s' id=%d msg='%s'.

Severity: ERROR
Message: An error occurred while attempting to verify the password for user %s during SASL PLAIN authentication: %s.

Severity: WARNING
Message: The password modify operation was not actually performed in the Directory Server because the LDAP no-op control was present in the request.

Severity: ERROR
Message: The user account has been administratively disabled.

Severity: ERROR
Message: The user account is locked.

Severity: ERROR
Message: Entry %s cannot be parsed as a valid static group because it does not contain the groupOfEntries, groupOfNames or groupOfUniqueNames object classes.

Severity: ERROR
Message: You do not have sufficient privileges to perform password reset operations.

Severity: ERROR
Message: The provided authorization ID was empty, which is not allowed for DIGEST-MD5 authentication.

Severity: ERROR
Message: The provided authorization ID %s contained an invalid DN: %s.

Severity: ERROR
Message: The authenticating user %s does not have sufficient privileges to specify an alternate authorization ID.

Severity: ERROR
Message: The entry corresponding to authorization DN %s does not exist in the Directory Server.

Severity: ERROR
Message: An error occurred while attempting to retrieve entry %s specified as the authorization ID: %s.

Severity: ERROR
Message: No entry corresponding to authorization ID %s was found in the server.

Severity: ERROR
Message: An error occurred while attempting to map authorization ID %s to a user entry: %s.

Severity: ERROR
Message: Could not map the provided certificate chain to a user entry because no peer certificate was available.

Severity: ERROR
Message: Could not map the provided certificate chain to a user because the peer certificate was not an X.509 certificate (peer certificate format was %s).

Severity: ERROR
Message: The certificate with subject %s could not be mapped to exactly one user. It maps at least to both '%s' and '%s'.

Severity: ERROR
Message: Configuration entry %s has value '%s' which violates the format required for attribute mappings. The expected format is 'certattr:userattr'.

Severity: ERROR
Message: Configuration entry %s contains multiple mappings for certificate attribute %s.

Severity: ERROR
Message: Mapping %s in configuration entry %s references attribute %s which is not defined in the server schema.

Severity: ERROR
Message: Configuration entry %s contains multiple mappings for user attribute %s.

Severity: ERROR
Message: Could not map the provided certificate chain to a user entry because no peer certificate was available.

Severity: ERROR
Message: Could not map the provided certificate chain to a user because the peer certificate was not an X.509 certificate (peer certificate format was %s).

Severity: ERROR
Message: Unable to decode peer certificate subject %s as a DN: %s.

Severity: ERROR
Message: Peer certificate subject %s does not contain any attributes for which a mapping has been established.

Severity: ERROR
Message: The certificate with subject %s could not be mapped to exactly one user. It maps at least to both '%s' and '%s'.

Severity: ERROR
Message: Could not map the provided certificate chain to a user entry because no peer certificate was available.

Severity: ERROR
Message: Could not map the provided certificate chain to a user because the peer certificate was not an X.509 certificate (peer certificate format was %s).

Severity: ERROR
Message: An error occurred while attempting to calculate the fingerprint for the peer certificate with subject %s: %s.

Severity: ERROR
Message: The certificate with fingerprint '%s' could not be mapped to exactly one user. It maps at least to both '%s' and '%s'.

Severity: ERROR
Message: Unable to decode value "%s" in entry "%s" as an LDAP URL: %s.

Severity: ERROR
Message: Dynamic groups do not support explicitly altering their membership.

Severity: WARNING
Message: Base DN %s specified in dynamic group %s does not exist in the server.

Severity: ERROR
Message: An error occurred while attempting perform an internal search with base DN %s and filter %s to resolve the member list for dynamic group %s: result code %s, error message %s.

Severity: ERROR
Message: The provided password differs less than the minimum required difference of %d characters.

Severity: ERROR
Message: The provided password contained too many instances of the same character appearing consecutively. The maximum number of times the same character may appear consecutively in a password is %d.

Severity: ERROR
Message: The provided password does not contain enough unique characters. The minimum number of unique characters that may appear in a user password is %d.

Severity: ERROR
Message: The %s attribute is not searchable and should not be included in otherwise unindexed search filters.

Severity: ERROR
Message: The provided password contained a word from the server’s dictionary.

Severity: ERROR
Message: The specified dictionary file %s does not exist.

Severity: ERROR
Message: An error occurred while attempting to load the dictionary from file %s: %s.

Severity: ERROR
Message: The provided password was found in another attribute in the user entry.

Severity: ERROR
Message: The provided password contained character '%s' which is not allowed for use in passwords.

Severity: ERROR
Message: The provided password did not contain enough characters from the character set '%s'. The minimum number of characters from that set that must be present in user passwords is %d.

Severity: ERROR
Message: The provided character set definition '%s' is invalid because it does not contain a colon to separate the minimum count from the character set.

Severity: ERROR
Message: The provided character set definition '%s' is invalid because the provided character set is empty.

Severity: ERROR
Message: The provided character set definition '%s' is invalid because the value before the colon must be an integer greater or equal to zero.

Severity: ERROR
Message: The provided character set definition '%s' is invalid because it contains character '%s' which has already been used.

Severity: ERROR
Message: The virtual static group defined in entry %s contains multiple target group DNs, but only one is allowed.

Severity: ERROR
Message: Unable to decode "%s" as the target DN for group %s: %s.

Severity: ERROR
Message: The virtual static group defined in entry %s does not contain a target group definition.

Severity: ERROR
Message: Target group %s referenced by virtual static group %s does not exist.

Severity: ERROR
Message: Altering membership for virtual static group %s is not allowed.

Severity: ERROR
Message: Virtual static group %s references target group %s which is itself a virtual static group. One virtual static group is not allowed to reference another as its target group.

Severity: ERROR
Message: You do not have sufficient privileges to use the password policy state extended operation.

Severity: ERROR
Message: The provided password policy state extended request did not include a request value.

Severity: ERROR
Message: An unexpected error occurred while attempting to decode password policy state extended request value: %s.

Severity: ERROR
Message: An unexpected error occurred while attempting to decode an operation from the password policy state extended request: %s.

Severity: ERROR
Message: No value was provided for the password policy state operation intended to set the disabled state for the user. Exactly one value (either 'true' or 'false') must be given.

Severity: ERROR
Message: Multiple values were provided for the password policy state operation intended to set the disabled state for the user. Exactly one value (either 'true' or 'false') must be given.

Severity: ERROR
Message: The value provided for the password policy state operation intended to set the disabled state for the user was invalid. The value must be either 'true' or 'false'.

Severity: ERROR
Message: Multiple values were provided for the password policy state operation intended to set the account expiration time for the user. Exactly one value must be given.

Severity: ERROR
Message: The value %s provided for the password policy state operation used to set the account expiration time was invalid: %s. The value should be specified using the generalized time format.

Severity: ERROR
Message: Multiple values were provided for the password policy state operation intended to set the password changed time for the user. Exactly one value must be given.

Severity: ERROR
Message: The value %s provided for the password policy state operation used to set the password changed time was invalid: %s. The value should be specified using the generalized time format.

Severity: ERROR
Message: Multiple values were provided for the password policy state operation intended to set the password warned time for the user. Exactly one value must be given.

Severity: ERROR
Message: The value %s provided for the password policy state operation used to set the password warned time was invalid: %s. The value should be specified using the generalized time format.

Severity: ERROR
Message: Multiple values were provided for the password policy state operation intended to add an authentication failure time for the user. Exactly one value must be given.

Severity: ERROR
Message: The value %s provided for the password policy state operation used to update the authentication failure times was invalid: %s. The value should be specified using the generalized time format.

Severity: ERROR
Message: Multiple values were provided for the password policy state operation intended to set the last login time for the user. Exactly one value must be given.

Severity: ERROR
Message: The value %s provided for the password policy state operation used to set the last login time was invalid: %s. The value should be specified using the generalized time format.

Severity: ERROR
Message: No value was provided for the password policy state operation intended to set the reset state for the user. Exactly one value (either 'true' or 'false') must be given.

Severity: ERROR
Message: Multiple values were provided for the password policy state operation intended to set the reset state for the user. Exactly one value (either 'true' or 'false') must be given.

Severity: ERROR
Message: The value provided for the password policy state operation intended to set the reset state for the user was invalid. The value must be either 'true' or 'false'.