| | |
| | | # CDDL HEADER END |
| | | # |
| | | # Copyright 2006-2009 Sun Microsystems, Inc. |
| | | |
| | | |
| | | |
| | | # |
| | | # Global directives |
| | | # |
| | | global.category=PROTOCOL |
| | | |
| | | # |
| | | # Format string definitions |
| | | # |
| | |
| | | MILD_ERR_LDAP_CLIENT_DECODE_INVALID_MULTIBYTE_LENGTH_169=\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u306f\u3001\u5024\u306e\u9577\u3055\u3092\u8868\u73fe\u3059\u308b\u305f\u3081\u306b\u8907\u6570\u30d0\u30a4\u30c8\u3092\u4f7f\u7528\u3059\u308b ASN.1 \u8981\u7d20\u3092\u6301\u3064\u8981\u6c42\u3092\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u30b5\u30fc\u30d0\u30fc\u306b\u9001\u4fe1\u3057\u307e\u3057\u305f\u3002 \u3053\u306e\u8981\u6c42\u306f\u3001\u9577\u3055\u3092\u8868\u73fe\u3059\u308b\u305f\u3081\u306b %d \u30d0\u30a4\u30c8\u5fc5\u8981\u3067\u3042\u308b\u3053\u3068\u3092\u793a\u3057\u3066\u3044\u307e\u3057\u305f\u304c\u3001\u3053\u308c\u306f\u8a31\u53ef\u3055\u308c\u3066\u3044\u308b\u6700\u5927\u5236\u9650\u306e 4 \u30d0\u30a4\u30c8\u3092\u8d85\u904e\u3057\u3066\u3044\u307e\u3059 |
| | | MILD_ERR_LDAP_CLIENT_DECODE_ASN1_FAILED_170=\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u306f\u3001ASN.1 \u8981\u7d20\u3068\u3057\u3066\u6b63\u3057\u304f\u5fa9\u53f7\u5316\u3067\u304d\u306a\u3044\u8981\u6c42\u3092\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u30b5\u30fc\u30d0\u30fc\u306b\u9001\u4fe1\u3057\u307e\u3057\u305f: %s |
| | | MILD_ERR_LDAP_CLIENT_DECODE_LDAP_MESSAGE_FAILED_171=\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u306f\u3001LDAP \u30e1\u30c3\u30bb\u30fc\u30b8\u3068\u3057\u3066\u6b63\u3057\u304f\u5fa9\u53f7\u5316\u3067\u304d\u306a\u3044\u8981\u6c42\u3092\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u30b5\u30fc\u30d0\u30fc\u306b\u9001\u4fe1\u3057\u307e\u3057\u305f: %s |
| | | ###SEVERE_ERR_LDAP_CLIENT_INVALID_DECODE_STATE_172=An internal error has \ |
| | | ### occurred within the Directory Server to cause it to lose track of where it is \ |
| | | ### in decoding requests on this client connection. It had an invalid decode \ |
| | | ### state of %d, and this connection must be terminated |
| | | SEVERE_ERR_LDAP_CLIENT_INVALID_DECODE_STATE_172=An internal error has occurred within the Directory Server to cause it to lose track of where it is in decoding requests on this client connection. It had an invalid decode state of %d, and this connection must be terminated |
| | | MILD_ERR_LDAP_CLIENT_DECODE_INVALID_REQUEST_TYPE_173=\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u306f\u3001\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u8981\u6c42\u3068\u3057\u3066\u6709\u52b9\u306a\u30e1\u30c3\u30bb\u30fc\u30b8\u3067\u306a\u3044 LDAP \u30e1\u30c3\u30bb\u30fc\u30b8\u3092\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u30b5\u30fc\u30d0\u30fc\u306b\u9001\u4fe1\u3057\u307e\u3057\u305f: %s |
| | | MILD_ERR_LDAP_CLIENT_CANNOT_CONVERT_MESSAGE_TO_OPERATION_174=\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u30b5\u30fc\u30d0\u30fc\u306f\u3001\u30af\u30e9\u30a4\u30a2\u30f3\u30c8 (%s) \u304b\u3089\u8aad\u307f\u8fbc\u307e\u308c\u305f LDAP \u30e1\u30c3\u30bb\u30fc\u30b8\u3092\u51e6\u7406\u306e\u305f\u3081\u306b\u5185\u90e8\u64cd\u4f5c\u306b\u5909\u63db\u3059\u308b\u3053\u3068\u304c\u3067\u304d\u307e\u305b\u3093\u3067\u3057\u305f: %s |
| | | MILD_ERR_LDAP_ABANDON_INVALID_MESSAGE_TYPE_175=\u6307\u5b9a\u3055\u308c\u305f LDAP \u30e1\u30c3\u30bb\u30fc\u30b8 (%s) \u3092\u5ec3\u68c4\u64cd\u4f5c\u306b\u5909\u63db\u3067\u304d\u307e\u305b\u3093: %s |
| | | MILD_ERR_LDAP_UNBIND_INVALID_MESSAGE_TYPE_176=\u6307\u5b9a\u3055\u308c\u305f LDAP \u30e1\u30c3\u30bb\u30fc\u30b8 (%s) \u3092\u30a2\u30f3\u30d0\u30a4\u30f3\u30c9\u64cd\u4f5c\u306b\u5909\u63db\u3067\u304d\u307e\u305b\u3093: %s |
| | | ###FATAL_ERR_LDAP_CONNHANDLER_OPEN_SELECTOR_FAILED_177=The LDAP connection \ |
| | | ### handler defined in configuration entry %s was unable to open a selector to \ |
| | | ### allow it to multiplex the associated accept sockets: %s. This connection \ |
| | | ### handler will be disabled |
| | | ###SEVERE_ERR_LDAP_CONNHANDLER_CREATE_CHANNEL_FAILED_178=The LDAP connection \ |
| | | ### handler defined in configuration entry %s was unable to create a server \ |
| | | ### socket channel to accept connections on %s:%d: %s. The Directory Server \ |
| | | ### will not listen for new connections on that address |
| | | ###FATAL_ERR_LDAP_CONNHANDLER_NO_ACCEPTORS_179=The LDAP connection handler \ |
| | | ### defined in configuration entry %s was unable to create any of the socket \ |
| | | ### channels on any of the configured addresses. This connection handler will be \ |
| | | ### disabled |
| | | FATAL_ERR_LDAP_CONNHANDLER_OPEN_SELECTOR_FAILED_177=The LDAP connection handler defined in configuration entry %s was unable to open a selector to allow it to multiplex the associated accept sockets: %s. This connection handler will be disabled |
| | | SEVERE_ERR_LDAP_CONNHANDLER_CREATE_CHANNEL_FAILED_178=The LDAP connection handler defined in configuration entry %s was unable to create a server socket channel to accept connections on %s:%d: %s. The Directory Server will not listen for new connections on that address |
| | | FATAL_ERR_LDAP_CONNHANDLER_NO_ACCEPTORS_179=The LDAP connection handler defined in configuration entry %s was unable to create any of the socket channels on any of the configured addresses. This connection handler will be disabled |
| | | MILD_ERR_LDAP_CONNHANDLER_DENIED_CLIENT_180=\u30af\u30e9\u30a4\u30a2\u30f3\u30c8 %s \u304b\u3089 %s \u3078\u306e\u63a5\u7d9a\u8a66\u884c\u306f\u62d2\u5426\u3055\u308c\u307e\u3057\u305f\u3002\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u306f\u3001\u62d2\u5426\u3055\u308c\u308b\u30a2\u30c9\u30ec\u30b9\u7bc4\u56f2\u306e 1 \u3064\u306b\u542b\u307e\u308c\u3066\u3044\u307e\u3057\u305f |
| | | MILD_ERR_LDAP_CONNHANDLER_DISALLOWED_CLIENT_181=\u30af\u30e9\u30a4\u30a2\u30f3\u30c8 %s \u304b\u3089 %s \u3078\u306e\u63a5\u7d9a\u8a66\u884c\u306f\u62d2\u5426\u3055\u308c\u307e\u3057\u305f\u3002\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u306f\u3001\u8a31\u53ef\u3055\u308c\u308b\u30a2\u30c9\u30ec\u30b9\u7bc4\u56f2\u306e 1 \u3064\u306b\u542b\u307e\u308c\u3066\u3044\u307e\u305b\u3093\u3067\u3057\u305f |
| | | INFO_LDAP_CONNHANDLER_UNABLE_TO_REGISTER_CLIENT_182=\u5185\u90e8\u30a8\u30e9\u30fc\u306e\u305f\u3081\u3001\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u30b5\u30fc\u30d0\u30fc\u306f\u3001%s \u304b\u3089 %s \u3078\u306e\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u63a5\u7d9a\u3092\u9069\u5207\u306a\u8981\u6c42\u30cf\u30f3\u30c9\u30e9\u306b\u6b63\u3057\u304f\u767b\u9332\u3067\u304d\u307e\u305b\u3093\u3067\u3057\u305f: %s |
| | | MILD_ERR_LDAP_CONNHANDLER_CANNOT_ACCEPT_CONNECTION_183=\u69cb\u6210\u30a8\u30f3\u30c8\u30ea %s \u3067\u5b9a\u7fa9\u3055\u308c\u305f LDAP \u63a5\u7d9a\u30cf\u30f3\u30c9\u30e9\u306f\u3001\u65b0\u3057\u3044\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u63a5\u7d9a\u3092\u53d7\u3051\u5165\u308c\u308b\u3053\u3068\u304c\u3067\u304d\u307e\u305b\u3093\u3067\u3057\u305f: %s |
| | | ###FATAL_ERR_LDAP_CONNHANDLER_CONSECUTIVE_ACCEPT_FAILURES_184=The LDAP \ |
| | | ### connection handler defined in configuration entry %s has experienced \ |
| | | ### consecutive failures while trying to accept client connections: %s. This \ |
| | | ### connection handler will be disabled |
| | | ###FATAL_ERR_LDAP_CONNHANDLER_UNCAUGHT_ERROR_185=The LDAP connection handler \ |
| | | ### defined in configuration entry %s caught an unexpected error while trying to \ |
| | | ### listen for new connections: %s. This connection handler will be disabled |
| | | ###FATAL_ERR_LDAP_REQHANDLER_OPEN_SELECTOR_FAILED_186=%s was unable to open a \ |
| | | ### selector to multiplex reads from clients: %s. This request handler cannot \ |
| | | ### continue processing |
| | | ###FATAL_ERR_LDAP_REQHANDLER_CANNOT_REGISTER_187=%s was unable to register this \ |
| | | ### client connection with the selector: %s |
| | | ###FATAL_ERR_LDAP_REQHANDLER_REJECT_DUE_TO_SHUTDOWN_188=This connection could \ |
| | | ### not be registered with a request handler because the Directory Server is \ |
| | | ### shutting down |
| | | ###FATAL_ERR_LDAP_REQHANDLER_REJECT_DUE_TO_QUEUE_FULL_189=This connection could \ |
| | | ### not be registered with a request handler because the pending queue associated \ |
| | | ### with %s is too full |
| | | ###FATAL_ERR_LDAP_REQHANDLER_DEREGISTER_DUE_TO_SHUTDOWN_190=This client \ |
| | | ### connection is being deregistered from the associated request handler because \ |
| | | ### the Directory Server is shutting down |
| | | FATAL_ERR_LDAP_CONNHANDLER_CONSECUTIVE_ACCEPT_FAILURES_184=The LDAP connection handler defined in configuration entry %s has experienced consecutive failures while trying to accept client connections: %s. This connection handler will be disabled |
| | | FATAL_ERR_LDAP_CONNHANDLER_UNCAUGHT_ERROR_185=The LDAP connection handler defined in configuration entry %s caught an unexpected error while trying to listen for new connections: %s. This connection handler will be disabled |
| | | FATAL_ERR_LDAP_REQHANDLER_OPEN_SELECTOR_FAILED_186=%s was unable to open a selector to multiplex reads from clients: %s. This request handler cannot continue processing |
| | | FATAL_ERR_LDAP_REQHANDLER_CANNOT_REGISTER_187=%s was unable to register this client connection with the selector: %s |
| | | FATAL_ERR_LDAP_REQHANDLER_REJECT_DUE_TO_SHUTDOWN_188=This connection could not be registered with a request handler because the Directory Server is shutting down |
| | | FATAL_ERR_LDAP_REQHANDLER_REJECT_DUE_TO_QUEUE_FULL_189=This connection could not be registered with a request handler because the pending queue associated with %s is too full |
| | | FATAL_ERR_LDAP_REQHANDLER_DEREGISTER_DUE_TO_SHUTDOWN_190=This client connection is being deregistered from the associated request handler because the Directory Server is shutting down |
| | | MILD_ERR_ASN1_READER_MAX_SIZE_EXCEEDED_191=\u8aad\u307f\u8fbc\u307e\u308c\u305f\u30c7\u30fc\u30bf\u3092 ASN.1 \u8981\u7d20\u3068\u3057\u3066\u5fa9\u53f7\u5316\u3067\u304d\u307e\u305b\u3093\u3002\u5fa9\u53f7\u5316\u3055\u308c\u305f\u8981\u7d20\u306e\u9577\u3055 %d \u30d0\u30a4\u30c8\u306f\u3001\u8a31\u53ef\u3055\u308c\u3066\u3044\u308b\u6700\u5927\u9577 %d \u30d0\u30a4\u30c8\u3092\u8d85\u3048\u3066\u3044\u307e\u3059\u3002 \u914d\u4e0b\u306e\u5165\u529b\u30b9\u30c8\u30ea\u30fc\u30e0\u304c\u9589\u3058\u3089\u308c\u3066\u304a\u308a\u3001\u3053\u306e\u30ea\u30fc\u30c0\u30fc\u306f\u4f7f\u7528\u3067\u304d\u306a\u304f\u306a\u3063\u3066\u3044\u307e\u3059 |
| | | MILD_ERR_LDAP_FILTER_STRING_NULL_192=\u6307\u5b9a\u3055\u308c\u305f\u6587\u5b57\u5217\u3092 LDAP \u691c\u7d22\u30d5\u30a3\u30eb\u30bf\u3068\u3057\u3066\u5fa9\u53f7\u5316\u3067\u304d\u307e\u305b\u3093\u3002\u6587\u5b57\u5217\u304c NULL \u3067\u3057\u305f |
| | | MILD_ERR_LDAP_FILTER_UNCAUGHT_EXCEPTION_193=\u6307\u5b9a\u3055\u308c\u305f\u6587\u5b57\u5217 %s \u3092 LDAP \u691c\u7d22\u30d5\u30a3\u30eb\u30bf\u3068\u3057\u3066\u5fa9\u53f7\u5316\u3067\u304d\u307e\u305b\u3093\u3002\u51e6\u7406\u4e2d\u306b\u4e88\u671f\u3057\u306a\u3044\u4f8b\u5916\u304c\u30b9\u30ed\u30fc\u3055\u308c\u307e\u3057\u305f: %s |
| | |
| | | MILD_ERR_LDAP_FILTER_SUBSTRING_NO_ASTERISKS_200=\u6307\u5b9a\u3055\u308c\u305f\u691c\u7d22\u30d5\u30a3\u30eb\u30bf "%s" \u3092\u30c7\u30b3\u30fc\u30c9\u3067\u304d\u307e\u305b\u3093\u3067\u3057\u305f\u3002\u4f4d\u7f6e %d \u3068 %d \u306e\u9593\u306e\u90e8\u5206\u6587\u5b57\u5217\u30d5\u30a3\u30eb\u30bf\u5024\u3068\u601d\u308f\u308c\u308b\u3082\u306e\u306b\u3001\u30a2\u30b9\u30bf\u30ea\u30b9\u30af\u30ef\u30a4\u30eb\u30c9\u30ab\u30fc\u30c9\u6587\u5b57\u304c\u3042\u308a\u307e\u305b\u3093\u3067\u3057\u305f |
| | | MILD_ERR_LDAP_FILTER_EXTENSIBLE_MATCH_NO_COLON_201=\u6307\u5b9a\u3055\u308c\u305f\u691c\u7d22\u30d5\u30a3\u30eb\u30bf "%s" \u3092\u30c7\u30b3\u30fc\u30c9\u3067\u304d\u307e\u305b\u3093\u3067\u3057\u305f\u3002\u4f4d\u7f6e %d \u3067\u59cb\u307e\u308b\u62e1\u5f35\u4e00\u81f4\u30b3\u30f3\u30dd\u30fc\u30cd\u30f3\u30c8\u306b\u3001\u5c5e\u6027\u578b\u540d\u306e\u672b\u5c3e\u3092\u793a\u3059\u30b3\u30ed\u30f3\u304c\u3042\u308a\u307e\u305b\u3093\u3067\u3057\u305f |
| | | MILD_ERR_LDAP_DISCONNECT_DUE_TO_INVALID_REQUEST_TYPE_202=\u3053\u306e\u63a5\u7d9a\u3092\u9589\u3058\u3066\u3044\u307e\u3059\u3002\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u304c\u3001\u8981\u6c42\u30e1\u30c3\u30bb\u30fc\u30b8\u306b\u306f\u8a31\u53ef\u3055\u308c\u306a\u3044\u30bf\u30a4\u30d7 %s (LDAP \u30e1\u30c3\u30bb\u30fc\u30b8 ID %d) \u306e\u7121\u52b9\u306a\u30e1\u30c3\u30bb\u30fc\u30b8\u3092\u9001\u4fe1\u3057\u307e\u3057\u305f |
| | | ###SEVERE_ERR_LDAP_DISCONNECT_DUE_TO_PROCESSING_FAILURE_203=An unexpected \ |
| | | ### failure occurred while trying to process a request of type %s (LDAP message \ |
| | | ### ID %d): %s. The client connection will be terminated |
| | | SEVERE_ERR_LDAP_DISCONNECT_DUE_TO_PROCESSING_FAILURE_203=An unexpected failure occurred while trying to process a request of type %s (LDAP message ID %d): %s. The client connection will be terminated |
| | | MILD_ERR_LDAP_INVALID_BIND_AUTH_TYPE_204=\u30d0\u30a4\u30f3\u30c9\u8981\u6c42\u30e1\u30c3\u30bb\u30fc\u30b8 (LDAP \u30e1\u30c3\u30bb\u30fc\u30b8 ID %d) \u306b\u3001\u7121\u52b9\u306a\u8a8d\u8a3c\u30bf\u30a4\u30d7\u306e %s \u304c\u542b\u307e\u308c\u3066\u3044\u307e\u3057\u305f\u3002\u3053\u308c\u306f\u30d7\u30ed\u30c8\u30b3\u30eb\u30a8\u30e9\u30fc\u3067\u3042\u308a\u3001\u3053\u306e\u63a5\u7d9a\u306f RFC 2251 \u30bb\u30af\u30b7\u30e7\u30f3 4.2.3 \u306b\u3088\u308a\u7d42\u4e86\u3057\u307e\u3059 |
| | | MILD_ERR_LDAP_DISCONNECT_DUE_TO_BIND_PROTOCOL_ERROR_205=\u3053\u306e\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u63a5\u7d9a\u306f\u7d42\u4e86\u4e2d\u3067\u3059\u3002\u30d0\u30a4\u30f3\u30c9\u8981\u6c42\u3092\u51e6\u7406\u4e2d\u306b\u30d7\u30ed\u30c8\u30b3\u30eb\u30a8\u30e9\u30fc\u304c\u767a\u751f\u3057\u307e\u3057\u305f\u3002 LDAP \u30e1\u30c3\u30bb\u30fc\u30b8 ID \u306f %d \u3067\u3001\u30d0\u30a4\u30f3\u30c9\u5fdc\u7b54\u306e\u30a8\u30e9\u30fc\u30e1\u30c3\u30bb\u30fc\u30b8\u306f %s \u3067\u3057\u305f |
| | | MILD_ERR_LDAPV2_SKIPPING_EXTENDED_RESPONSE_206=\u62e1\u5f35\u5fdc\u7b54\u30e1\u30c3\u30bb\u30fc\u30b8\u3092 LDAPv2 \u30af\u30e9\u30a4\u30a2\u30f3\u30c8 (\u63a5\u7d9a ID=%d\u3001\u64cd\u4f5c ID=%d) \u306b\u9001\u4fe1\u3057\u3088\u3046\u3068\u3057\u307e\u3057\u305f: %s\u3002LDAPv2 \u3067\u306f\u62e1\u5f35\u64cd\u4f5c\u306f\u8a31\u53ef\u3055\u308c\u306a\u3044\u305f\u3081\u3001\u3053\u306e\u5fdc\u7b54\u306f\u9001\u4fe1\u3055\u308c\u307e\u305b\u3093 |
| | |
| | | MILD_ERR_LDAPV2_CLIENTS_NOT_ALLOWED_210=\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u30b5\u30fc\u30d0\u30fc\u306f LDAPv2 \u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u3078\u306e\u30a2\u30af\u30bb\u30b9\u3092\u62d2\u5426\u3059\u308b\u3088\u3046\u306b\u69cb\u6210\u3055\u308c\u3066\u3044\u307e\u3059\u3002 \u3053\u306e\u63a5\u7d9a\u306f\u9589\u3058\u3089\u308c\u307e\u3059 |
| | | MILD_ERR_LDAPV2_EXTENDED_REQUEST_NOT_ALLOWED_211=\u63a5\u7d9a ID %d \u3092\u6301\u3064\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u304c LDAPv2 \u3092\u4f7f\u7528\u3057\u3066\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u30b5\u30fc\u30d0\u30fc\u3078\u306e\u8a8d\u8a3c\u3092\u5b9f\u884c\u3057\u307e\u3057\u305f\u304c\u3001\u62e1\u5f35\u64cd\u4f5c\u8981\u6c42\u3092\u9001\u4fe1\u3057\u3088\u3046\u3068\u3057\u307e\u3057\u305f (LDAP \u30e1\u30c3\u30bb\u30fc\u30b8 ID %d)\u3002\u3053\u308c\u306f LDAPv2 \u3067\u306f\u8a31\u53ef\u3055\u308c\u307e\u305b\u3093\u3002 \u63a5\u7d9a\u306f\u7d42\u4e86\u3057\u307e\u3059 |
| | | MILD_ERR_LDAP_STATS_INVALID_MONITOR_INITIALIZATION_212=\u69cb\u6210\u30a8\u30f3\u30c8\u30ea %s \u3067\u306e\u5b9a\u7fa9\u306b\u5f93\u3063\u3066\u3001LDAP \u7d71\u8a08\u30e2\u30cb\u30bf\u30fc\u30d7\u30ed\u30d0\u30a4\u30c0\u3092\u521d\u671f\u5316\u3057\u3088\u3046\u3068\u3057\u307e\u3057\u305f\u3002\u3053\u306e\u30e2\u30cb\u30bf\u30fc\u30d7\u30ed\u30d0\u30a4\u30c0\u306f\u3001\u69cb\u6210\u5185\u304b\u3089\u3067\u306f\u306a\u304f\u3001\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u30b5\u30fc\u30d0\u30fc\u81ea\u4f53\u306e\u4e2d\u3067\u306e\u307f\u52d5\u7684\u306b\u4f5c\u6210\u3059\u3079\u304d\u3067\u3059 |
| | | ###SEVERE_ERR_LDAP_REQHANDLER_UNEXPECTED_SELECT_EXCEPTION_213=The LDAP request \ |
| | | ### handler thread "%s" encountered an unexpected error that would have caused \ |
| | | ### the thread to die: %s. The error has been caught and the request handler \ |
| | | ### should continue operating as normal |
| | | SEVERE_ERR_LDAP_REQHANDLER_UNEXPECTED_SELECT_EXCEPTION_213=The LDAP request handler thread "%s" encountered an unexpected error that would have caused the thread to die: %s. The error has been caught and the request handler should continue operating as normal |
| | | MILD_ERR_LDAP_CONNHANDLER_REJECTED_BY_SERVER_214=\u3053\u306e\u63a5\u7d9a\u3092\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u30b5\u30fc\u30d0\u30fc\u306b\u767b\u9332\u3057\u3088\u3046\u3068\u3057\u307e\u3057\u305f\u304c\u3001\u62d2\u5426\u3055\u308c\u307e\u3057\u305f\u3002 \u8a31\u53ef\u3055\u308c\u3066\u3044\u308b\u6700\u5927\u6570\u306e\u540c\u6642\u63a5\u7d9a\u304c\u30b5\u30fc\u30d0\u30fc\u3067\u3059\u3067\u306b\u78ba\u7acb\u3055\u308c\u3066\u3044\u308b\u304b\u3001\u307e\u305f\u306f\u30b5\u30fc\u30d0\u30fc\u304c\u5236\u9650\u4ed8\u304d\u30a2\u30af\u30bb\u30b9\u30e2\u30fc\u30c9\u306b\u306a\u3063\u3066\u3044\u308b\u53ef\u80fd\u6027\u304c\u3042\u308a\u307e\u3059 |
| | | INFO_LDAP_CONNHANDLER_DESCRIPTION_LISTEN_ADDRESS_215=\u3053\u306e\u63a5\u7d9a\u30cf\u30f3\u30c9\u30e9\u304c\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u63a5\u7d9a\u3092\u53d7\u3051\u5165\u308c\u308b\u3053\u3068\u304c\u3067\u304d\u308b\u30a2\u30c9\u30ec\u30b9\u307e\u305f\u306f\u30a2\u30c9\u30ec\u30b9\u30bb\u30c3\u30c8\u3002 \u5024\u3092\u6307\u5b9a\u3057\u306a\u3044\u5834\u5408\u3001\u30b5\u30fc\u30d0\u30fc\u306f\u30a2\u30af\u30c6\u30a3\u30d6\u306a\u30a2\u30c9\u30ec\u30b9\u3059\u3079\u3066\u306e\u63a5\u7d9a\u3092\u53d7\u3051\u5165\u308c\u307e\u3059\u3002 \u3053\u306e\u8a2d\u5b9a\u5c5e\u6027\u3078\u306e\u5909\u66f4\u306f\u3001\u63a5\u7d9a\u30cf\u30f3\u30c9\u30e9\u3092\u7121\u52b9\u306b\u3057\u3066\u518d\u5ea6\u6709\u52b9\u306b\u3059\u308b\u304b\u3001\u307e\u305f\u306f\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u30b5\u30fc\u30d0\u30fc\u3092\u518d\u8d77\u52d5\u3059\u308b\u307e\u3067\u6709\u52b9\u306b\u306a\u308a\u307e\u305b\u3093 |
| | | INFO_LDAP_CONNHANDLER_DESCRIPTION_LISTEN_PORT_216=\u3053\u306e\u63a5\u7d9a\u30cf\u30f3\u30c9\u30e9\u304c\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u63a5\u7d9a\u3092\u53d7\u3051\u5165\u308c\u308b\u3053\u3068\u304c\u3067\u304d\u308b TCP \u30dd\u30fc\u30c8\u3002 \u3053\u306e\u8a2d\u5b9a\u5c5e\u6027\u3078\u306e\u5909\u66f4\u306f\u3001\u63a5\u7d9a\u30cf\u30f3\u30c9\u30e9\u3092\u7121\u52b9\u306b\u3057\u3066\u518d\u5ea6\u6709\u52b9\u306b\u3059\u308b\u304b\u3001\u307e\u305f\u306f\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u30b5\u30fc\u30d0\u30fc\u3092\u518d\u8d77\u52d5\u3059\u308b\u307e\u3067\u6709\u52b9\u306b\u306a\u308a\u307e\u305b\u3093 |
| | |
| | | INFO_LDAP_CONNHANDLER_DESCRIPTION_ALLOW_STARTTLS_227=\u3053\u306e\u63a5\u7d9a\u30cf\u30f3\u30c9\u30e9\u3067\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u304c StartTLS \u62e1\u5f35\u64cd\u4f5c\u3092\u4f7f\u7528\u3057\u3066 SSL LDAP \u4ee5\u5916\u306e\u63a5\u7d9a\u3092\u4ecb\u3057\u305f\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u30fc\u4fdd\u8b77\u3055\u308c\u305f\u901a\u4fe1\u3092\u958b\u59cb\u3059\u308b\u3053\u3068\u3092\u8a31\u53ef\u3059\u308b\u304b\u3069\u3046\u304b\u3092\u793a\u3057\u307e\u3059\u3002 \u63a5\u7d9a\u30cf\u30f3\u30c9\u30e9\u3067 SSL \u304c\u6709\u52b9\u306b\u306a\u3063\u3066\u3044\u308b\u5834\u5408\u3001\u3053\u308c\u306f\u4f7f\u7528\u3067\u304d\u307e\u305b\u3093\u3002 \u3053\u306e\u8a2d\u5b9a\u5c5e\u6027\u3078\u306e\u5909\u66f4\u306f LDAP \u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u306b\u5bfe\u3057\u3066\u305f\u3060\u3061\u306b\u6709\u52b9\u306b\u306a\u308a\u307e\u3059 |
| | | INFO_LDAP_CONNHANDLER_DESCRIPTION_SSL_CLIENT_AUTH_POLICY_228=SSL \u30d9\u30fc\u30b9\u306e\u63a5\u7d9a\u3092\u78ba\u7acb\u3059\u308b\u3068\u304d\u3001\u307e\u305f\u306f\u78ba\u7acb\u3055\u308c\u305f\u63a5\u7d9a\u3067 StartTLS \u3092\u4f7f\u7528\u3057\u3066\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u30fc\u4fdd\u8b77\u3055\u308c\u305f\u30c1\u30e3\u30cd\u30eb\u3092\u958b\u59cb\u3059\u308b\u3068\u304d\u306b\u3001\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u306b\u305d\u308c\u81ea\u4f53\u306e\u8a3c\u660e\u66f8\u3092\u63d0\u793a\u3059\u308b\u3088\u3046\u306b\u8981\u6c42\u3059\u308b\u3053\u3068\u306b\u95a2\u3057\u3066\u4f7f\u7528\u3059\u3079\u304d\u30dd\u30ea\u30b7\u30fc\u3002 \u3053\u306e\u8a2d\u5b9a\u5c5e\u6027\u3078\u306e\u5909\u66f4\u306f\u3001\u63a5\u7d9a\u30cf\u30f3\u30c9\u30e9\u3092\u7121\u52b9\u306b\u3057\u3066\u518d\u5ea6\u6709\u52b9\u306b\u3059\u308b\u304b\u3001\u307e\u305f\u306f\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u30b5\u30fc\u30d0\u30fc\u3092\u518d\u8d77\u52d5\u3059\u308b\u307e\u3067\u6709\u52b9\u306b\u306a\u308a\u307e\u305b\u3093 |
| | | INFO_LDAP_CONNHANDLER_DESCRIPTION_SSL_CERT_NICKNAME_229=SSL \u30d9\u30fc\u30b9\u306e\u63a5\u7d9a\u3092\u53d7\u3051\u4ed8\u3051\u308b\u3068\u304d\u3001\u307e\u305f\u306f StartTLS \u30cd\u30b4\u30b7\u30a8\u30fc\u30b7\u30e7\u30f3\u3092\u5b9f\u884c\u3059\u308b\u3068\u304d\u306b\u63a5\u7d9a\u30cf\u30f3\u30c9\u30e9\u3067\u4f7f\u7528\u3059\u3079\u304d\u8a3c\u660e\u66f8\u306e\u30cb\u30c3\u30af\u30cd\u30fc\u30e0\u3002 \u3053\u306e\u8a2d\u5b9a\u5c5e\u6027\u3078\u306e\u5909\u66f4\u306f\u3001\u63a5\u7d9a\u30cf\u30f3\u30c9\u30e9\u3092\u7121\u52b9\u306b\u3057\u3066\u518d\u5ea6\u6709\u52b9\u306b\u3059\u308b\u304b\u3001\u307e\u305f\u306f\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u30b5\u30fc\u30d0\u30fc\u3092\u518d\u8d77\u52d5\u3059\u308b\u307e\u3067\u6709\u52b9\u306b\u306a\u308a\u307e\u305b\u3093 |
| | | ###SEVERE_ERR_LDAP_CONNHANDLER_UNKNOWN_LISTEN_ADDRESS_230=The specified listen \ |
| | | ### address "%s" in configuration entry "%s" could not be resolved: %s. Please \ |
| | | ### make sure that name resolution is properly configured on this system |
| | | ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_LISTEN_ADDRESS_231=An unexpected \ |
| | | ### error occurred while processing the ds-cfg-listen-address attribute in \ |
| | | ### configuration entry %s, which is used to specify the address or set of \ |
| | | ### addresses on which to listen for client connections: %s |
| | | ###SEVERE_ERR_LDAP_CONNHANDLER_NO_LISTEN_PORT_232=No listen port was defined \ |
| | | ### using configuration ds-cfg-listen-port in configuration entry %s. This is a \ |
| | | ### required attribute |
| | | ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_LISTEN_PORT_233=An unexpected \ |
| | | ### error occurred while processing the ds-cfg-listen-port attribute in \ |
| | | ### configuration entry %s, which is used to specify the port on which to listen \ |
| | | ### for client connections: %s |
| | | ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_ALLOWED_CLIENTS_234=An \ |
| | | ### unexpected error occurred while processing the ds-cfg-allowed-client \ |
| | | ### attribute in configuration entry %s, which is used to specify the address \ |
| | | ### mask(s) of the clients that are allowed to establish connections to this \ |
| | | ### connection handler: %s |
| | | ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_DENIED_CLIENTS_235=An unexpected \ |
| | | ### error occurred while processing the ds-cfg-denied-client attribute in \ |
| | | ### configuration entry %s, which is used to specify the address mask(s) of the \ |
| | | ### clients that are not allowed to establish connections to this connection \ |
| | | ### handler: %s |
| | | ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_ALLOW_LDAPV2_236=An unexpected \ |
| | | ### error occurred while processing the ds-cfg-allow-ldap-v2 attribute in \ |
| | | ### configuration entry %s, which is used to indicate whether LDAPv2 clients will \ |
| | | ### be allowed to access this connection handler: %s |
| | | ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_NUM_REQUEST_HANDLERS_237=An \ |
| | | ### unexpected error occurred while processing the ds-cfg-num-request-handlers \ |
| | | ### attribute in configuration entry %s, which is used to specify the number of \ |
| | | ### request handlers to use to read requests from clients: %s |
| | | ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_SEND_REJECTION_NOTICE_238=An \ |
| | | ### unexpected error occurred while processing the ds-cfg-send-rejection-notice \ |
| | | ### attribute in configuration entry %s, which is used to indicate whether to \ |
| | | ### send a notice of disconnection message to rejected client connections: %s |
| | | ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_USE_TCP_KEEPALIVE_239=An \ |
| | | ### unexpected error occurred while processing the ds-cfg-use-tcp-keep-alive \ |
| | | ### attribute in configuration entry %s, which is used to periodically send TCP \ |
| | | ### Keep-Alive messages over idle connections: %s |
| | | ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_USE_TCP_NODELAY_240=An \ |
| | | ### unexpected error occurred while processing the ds-cfg-use-tcp-no-delay \ |
| | | ### attribute in configuration entry %s, which is used to determine whether to \ |
| | | ### immediately flush responses to clients: %s |
| | | ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_ALLOW_REUSE_ADDRESS_241=An \ |
| | | ### unexpected error occurred while processing the ds-cfg-allow-tcp-reuse-address \ |
| | | ### attribute in configuration entry %s, which is used to determine whether to \ |
| | | ### set the SO_REUSEADDR option on the listen socket: %s |
| | | ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_MAX_REQUEST_SIZE_242=An \ |
| | | ### unexpected error occurred while processing the ds-cfg-max-request-size \ |
| | | ### attribute in configuration entry %s, which is used to determine the maximum \ |
| | | ### size in bytes that can be used for a client request: %s |
| | | ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_USE_SSL_243=An unexpected error \ |
| | | ### occurred while processing the ds-cfg-use-ssl attribute in configuration entry \ |
| | | ### %s, which is used to indicate whether to use SSL when accepting client \ |
| | | ### connections: %s |
| | | ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_HAVE_SSL_AND_STARTTLS_244=The LDAP \ |
| | | ### connection handler defined in configuration entry %s is configured to \ |
| | | ### communicate over SSL and also to allow clients to use the StartTLS extended \ |
| | | ### operation. These options can not be used at the same time, so clients will \ |
| | | ### not be allowed to use the StartTLS operation |
| | | ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_ALLOW_STARTTLS_245=An unexpected \ |
| | | ### error occurred while processing the ds-cfg-allow-start-tls attribute in \ |
| | | ### configuration entry %s, which is used to indicate whether clients can use the \ |
| | | ### StartTLS extended operation: %s |
| | | ###SEVERE_ERR_LDAP_CONNHANDLER_INVALID_SSL_CLIENT_AUTH_POLICY_246=The SSL client \ |
| | | ### authentication policy "%s" specified in attribute \ |
| | | ### ds-cfg-ssl-client-auth-policy of configuration entry %s is invalid. The \ |
| | | ### value must be one of "disabled", "optional", or "required" |
| | | ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_SSL_CLIENT_AUTH_POLICY_247=An \ |
| | | ### unexpected error occurred while processing the ds-cfg-ssl-client-auth-policy \ |
| | | ### attribute in configuration entry %s, which is used to specify the policy that \ |
| | | ### should be used for requesting/requiring SSL client authentication: %s |
| | | ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_SSL_CERT_NICKNAME_248=An \ |
| | | ### unexpected error occurred while processing the ds-cfg-ssl-cert-nickname \ |
| | | ### attribute in configuration entry %s, which is used to specify the nickname of \ |
| | | ### the certificate to use for accepting SSL/TLS connections: %s |
| | | ###SEVERE_ERR_LDAP_CONNHANDLER_INVALID_ADDRESS_MASK_249=The string %s defined in \ |
| | | ### attribute %s of configuration entry %s could not be decoded as a valid \ |
| | | ### address mask: %s |
| | | SEVERE_ERR_LDAP_CONNHANDLER_UNKNOWN_LISTEN_ADDRESS_230=The specified listen address "%s" in configuration entry "%s" could not be resolved: %s. Please make sure that name resolution is properly configured on this system |
| | | SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_LISTEN_ADDRESS_231=An unexpected error occurred while processing the ds-cfg-listen-address attribute in configuration entry %s, which is used to specify the address or set of addresses on which to listen for client connections: %s |
| | | SEVERE_ERR_LDAP_CONNHANDLER_NO_LISTEN_PORT_232=No listen port was defined using configuration ds-cfg-listen-port in configuration entry %s. This is a required attribute |
| | | SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_LISTEN_PORT_233=An unexpected error occurred while processing the ds-cfg-listen-port attribute in configuration entry %s, which is used to specify the port on which to listen for client connections: %s |
| | | SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_ALLOWED_CLIENTS_234=An unexpected error occurred while processing the ds-cfg-allowed-client attribute in configuration entry %s, which is used to specify the address mask(s) of the clients that are allowed to establish connections to this connection handler: %s |
| | | SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_DENIED_CLIENTS_235=An unexpected error occurred while processing the ds-cfg-denied-client attribute in configuration entry %s, which is used to specify the address mask(s) of the clients that are not allowed to establish connections to this connection handler: %s |
| | | SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_ALLOW_LDAPV2_236=An unexpected error occurred while processing the ds-cfg-allow-ldap-v2 attribute in configuration entry %s, which is used to indicate whether LDAPv2 clients will be allowed to access this connection handler: %s |
| | | SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_NUM_REQUEST_HANDLERS_237=An unexpected error occurred while processing the ds-cfg-num-request-handlers attribute in configuration entry %s, which is used to specify the number of request handlers to use to read requests from clients: %s |
| | | SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_SEND_REJECTION_NOTICE_238=\u69cb\u6210\u30a8\u30f3\u30c8\u30ea %s \u5185\u306e ds-cfg-send-rejection-notice \u5c5e\u6027\u306e\u51e6\u7406\u4e2d\u306b\u3001\u4e88\u671f\u3057\u306a\u3044\u30a8\u30e9\u30fc\u304c\u767a\u751f\u3057\u307e\u3057\u305f\u3002\u3053\u306e\u5c5e\u6027\u306f\u62d2\u5426\u3055\u308c\u305f\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u63a5\u7d9a\u306b\u5207\u65ad\u30e1\u30c3\u30bb\u30fc\u30b8\u306e\u901a\u77e5\u3092\u9001\u4fe1\u3059\u308b\u304b\u3069\u3046\u304b\u3092\u793a\u3059\u305f\u3081\u306b\u4f7f\u7528\u3055\u308c\u307e\u3059: %s |
| | | SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_USE_TCP_KEEPALIVE_239=An unexpected error occurred while processing the ds-cfg-use-tcp-keep-alive attribute in configuration entry %s, which is used to periodically send TCP Keep-Alive messages over idle connections: %s |
| | | SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_USE_TCP_NODELAY_240=An unexpected error occurred while processing the ds-cfg-use-tcp-no-delay attribute in configuration entry %s, which is used to determine whether to immediately flush responses to clients: %s |
| | | SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_ALLOW_REUSE_ADDRESS_241=An unexpected error occurred while processing the ds-cfg-allow-tcp-reuse-address attribute in configuration entry %s, which is used to determine whether to set the SO_REUSEADDR option on the listen socket: %s |
| | | SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_MAX_REQUEST_SIZE_242=An unexpected error occurred while processing the ds-cfg-max-request-size attribute in configuration entry %s, which is used to determine the maximum size in bytes that can be used for a client request: %s |
| | | SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_USE_SSL_243=An unexpected error occurred while processing the ds-cfg-use-ssl attribute in configuration entry %s, which is used to indicate whether to use SSL when accepting client connections: %s |
| | | SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_HAVE_SSL_AND_STARTTLS_244=The LDAP connection handler defined in configuration entry %s is configured to communicate over SSL and also to allow clients to use the StartTLS extended operation. These options can not be used at the same time, so clients will not be allowed to use the StartTLS operation |
| | | SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_ALLOW_STARTTLS_245=An unexpected error occurred while processing the ds-cfg-allow-start-tls attribute in configuration entry %s, which is used to indicate whether clients can use the StartTLS extended operation: %s |
| | | SEVERE_ERR_LDAP_CONNHANDLER_INVALID_SSL_CLIENT_AUTH_POLICY_246=The SSL client authentication policy "%s" specified in attribute ds-cfg-ssl-client-auth-policy of configuration entry %s is invalid. The value must be one of "disabled", "optional", or "required" |
| | | SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_SSL_CLIENT_AUTH_POLICY_247=An unexpected error occurred while processing the ds-cfg-ssl-client-auth-policy attribute in configuration entry %s, which is used to specify the policy that should be used for requesting/requiring SSL client authentication: %s |
| | | SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_SSL_CERT_NICKNAME_248=An unexpected error occurred while processing the ds-cfg-ssl-cert-nickname attribute in configuration entry %s, which is used to specify the nickname of the certificate to use for accepting SSL/TLS connections: %s |
| | | SEVERE_ERR_LDAP_CONNHANDLER_INVALID_ADDRESS_MASK_249=The string %s defined in attribute %s of configuration entry %s could not be decoded as a valid address mask: %s |
| | | INFO_LDAP_CONNHANDLER_NEW_ALLOWED_CLIENTS_250=\u8a31\u53ef\u3055\u308c\u308b\u65b0\u3057\u3044\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u30a2\u30c9\u30ec\u30b9\u30de\u30b9\u30af\u30bb\u30c3\u30c8\u304c\u69cb\u6210\u30a8\u30f3\u30c8\u30ea %s \u306b\u9069\u7528\u3055\u308c\u307e\u3057\u305f |
| | | INFO_LDAP_CONNHANDLER_NEW_DENIED_CLIENTS_251=\u62d2\u5426\u3055\u308c\u308b\u65b0\u3057\u3044\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u30a2\u30c9\u30ec\u30b9\u30de\u30b9\u30af\u30bb\u30c3\u30c8\u304c\u69cb\u6210\u30a8\u30f3\u30c8\u30ea %s \u306b\u9069\u7528\u3055\u308c\u307e\u3057\u305f |
| | | INFO_LDAP_CONNHANDLER_NEW_ALLOW_LDAPV2_252=\u69cb\u6210\u30a8\u30f3\u30c8\u30ea %2$s \u3067\u3001ds-cfg-allow-ldap-v2 \u5c5e\u6027\u306e\u5024\u304c %1$s \u306b\u66f4\u65b0\u3055\u308c\u307e\u3057\u305f |
| | |
| | | INFO_LDAP_CONNHANDLER_NEW_MAX_REQUEST_SIZE_256=\u69cb\u6210\u30a8\u30f3\u30c8\u30ea %2$s \u3067\u3001ds-cfg-max-request-size \u5c5e\u6027\u306e\u5024\u304c %1$s \u306b\u66f4\u65b0\u3055\u308c\u307e\u3057\u305f |
| | | INFO_LDAP_CONNHANDLER_NEW_ALLOW_STARTTLS_257=\u69cb\u6210\u30a8\u30f3\u30c8\u30ea %2$s \u3067\u3001ds-cfg-allow-start-tls \u5c5e\u6027\u306e\u5024\u304c %1$s \u306b\u66f4\u65b0\u3055\u308c\u307e\u3057\u305f |
| | | INFO_LDAP_CONNHANDLER_DESCRIPTION_KEEP_STATS_258=\u63a5\u7d9a\u30cf\u30f3\u30c9\u30e9\u3067 LDAP \u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u901a\u4fe1\u306b\u95a2\u3059\u308b\u7d71\u8a08\u3092\u4fdd\u6301\u3059\u308b\u304b\u3069\u3046\u304b\u3092\u793a\u3057\u307e\u3059\u3002 \u3053\u306e\u60c5\u5831\u3092\u4fdd\u6301\u3059\u308b\u3068\u3001\u30d1\u30d5\u30a9\u30fc\u30de\u30f3\u30b9\u304c\u308f\u305a\u304b\u306b\u4f4e\u4e0b\u3059\u308b\u53ef\u80fd\u6027\u304c\u3042\u308a\u307e\u3059\u304c\u3001\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u306e\u4f7f\u7528\u30d1\u30bf\u30fc\u30f3\u3092\u7406\u89e3\u3059\u308b\u305f\u3081\u306b\u5f79\u7acb\u3066\u308b\u3053\u3068\u304c\u3067\u304d\u307e\u3059\u3002 \u3053\u306e\u8a2d\u5b9a\u5c5e\u6027\u3078\u306e\u5909\u66f4\u306f\u305f\u3060\u3061\u306b\u6709\u52b9\u306b\u306a\u308a\u307e\u3059\u304c\u3001\u9069\u7528\u5bfe\u8c61\u306f\u65b0\u3057\u3044\u63a5\u7d9a\u3060\u3051\u3067\u3059\u3002\u307e\u305f\u3001\u3059\u3067\u306b\u53ce\u96c6\u3055\u308c\u305f\u7d71\u8a08\u30c7\u30fc\u30bf\u304c\u5b58\u5728\u3059\u308b\u5834\u5408\u306b\u65e2\u5b58\u306e\u7d71\u8a08\u30c7\u30fc\u30bf\u304c\u6d88\u53bb\u3055\u308c\u308b\u3068\u3044\u3046\u526f\u4f5c\u7528\u304c\u3042\u308a\u307e\u3059 |
| | | ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_KEEP_STATS_259=An unexpected \ |
| | | ### error occurred while processing the ds-cfg-keep-stats attribute in \ |
| | | ### configuration entry %s, which is used to indicate whether LDAP usage \ |
| | | ### statistics should be enabled for this connection handler: %s |
| | | SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_KEEP_STATS_259=An unexpected error occurred while processing the ds-cfg-keep-stats attribute in configuration entry %s, which is used to indicate whether LDAP usage statistics should be enabled for this connection handler: %s |
| | | INFO_LDAP_CONNHANDLER_NEW_KEEP_STATS_260=\u69cb\u6210\u30a8\u30f3\u30c8\u30ea %2$s \u3067\u3001ds-cfg-keep-stats \u5c5e\u6027\u306e\u5024\u304c %1$s \u306b\u66f4\u65b0\u3055\u308c\u307e\u3057\u305f |
| | | MILD_ERR_ASN1_LONG_SET_VALUE_INVALID_LENGTH_261=\u6307\u5b9a\u3055\u308c\u305f\u30d0\u30a4\u30c8\u914d\u5217\u3092 ASN.1 \u30ed\u30f3\u30b0\u8981\u7d20\u306e\u5024\u3068\u3057\u3066\u5fa9\u53f7\u5316\u3067\u304d\u307e\u305b\u3093\u3002\u914d\u5217\u306e\u9577\u3055\u304c 1 \u304b\u3089 8 \u30d0\u30a4\u30c8\u306e\u7bc4\u56f2\u306b\u3042\u308a\u307e\u305b\u3093\u3067\u3057\u305f (\u6307\u5b9a\u3055\u308c\u305f\u9577\u3055\u306f %d) |
| | | MILD_ERR_ASN1_LONG_DECODE_ELEMENT_INVALID_LENGTH_262=\u6307\u5b9a\u3055\u308c\u305f ASN.1 \u8981\u7d20\u3092\u30ed\u30f3\u30b0\u8981\u7d20\u3068\u3057\u3066\u5fa9\u53f7\u5316\u3067\u304d\u307e\u305b\u3093\u3002\u8981\u7d20\u5024\u306e\u9577\u3055\u304c 1 \u304b\u3089 8 \u30d0\u30a4\u30c8\u306e\u7bc4\u56f2\u306b\u3042\u308a\u307e\u305b\u3093\u3067\u3057\u305f (\u5b9f\u969b\u306e\u9577\u3055\u306f %d) |
| | | MILD_ERR_ASN1_LONG_DECODE_ARRAY_INVALID_LENGTH_263=\u6307\u5b9a\u3055\u308c\u305f\u30d0\u30a4\u30c8\u914d\u5217\u3092 ASN.1 \u30ed\u30f3\u30b0\u8981\u7d20\u3068\u3057\u3066\u5fa9\u53f7\u5316\u3067\u304d\u307e\u305b\u3093\u3002\u5fa9\u53f7\u5316\u3055\u308c\u305f\u5024\u306e\u9577\u3055\u304c 1 \u304b\u3089 8 \u30d0\u30a4\u30c8\u306e\u7bc4\u56f2\u306b\u3042\u308a\u307e\u305b\u3093\u3067\u3057\u305f (\u5fa9\u53f7\u5316\u3055\u308c\u305f\u9577\u3055\u306f %d) |
| | | ###SEVERE_ERR_INTERNAL_CANNOT_DECODE_DN_264=An unexpected error occurred while \ |
| | | ### trying to decode the DN %s used for internal operations as a root user: %s |
| | | SEVERE_ERR_INTERNAL_CANNOT_DECODE_DN_264=An unexpected error occurred while trying to decode the DN %s used for internal operations as a root user: %s |
| | | INFO_LDAP_CONNHANDLER_DESCRIPTION_SSL_ENABLED_PROTOCOLS_265=SSL \u307e\u305f\u306f StartTLS \u901a\u4fe1\u3067\u306e\u4f7f\u7528\u304c\u8a31\u53ef\u3055\u308c\u308b SSL \u30d7\u30ed\u30c8\u30b3\u30eb\u306e\u540d\u524d\u3002 \u3053\u306e\u8a2d\u5b9a\u5c5e\u6027\u3078\u306e\u5909\u66f4\u306f\u305f\u3060\u3061\u306b\u6709\u52b9\u306b\u306a\u308a\u307e\u3059\u304c\u3001\u5f71\u97ff\u304c\u53ca\u3076\u306e\u306f\u5909\u66f4\u5f8c\u306b\u4f5c\u6210\u3055\u308c\u305f\u65b0\u3057\u3044 SSL/TLS \u30d9\u30fc\u30b9\u306e\u30bb\u30c3\u30b7\u30e7\u30f3\u3060\u3051\u3067\u3059 |
| | | ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_SSL_PROTOCOLS_266=An unexpected \ |
| | | ### error occurred while processing the ds-cfg-ssl-protocol attribute in \ |
| | | ### configuration entry %s, which is used to specify the names of the SSL \ |
| | | ### protocols to allow for SSL/TLS sessions: %s |
| | | SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_SSL_PROTOCOLS_266=An unexpected error occurred while processing the ds-cfg-ssl-protocol attribute in configuration entry %s, which is used to specify the names of the SSL protocols to allow for SSL/TLS sessions: %s |
| | | INFO_LDAP_CONNHANDLER_DESCRIPTION_SSL_ENABLED_CIPHERS_267=SSL \u307e\u305f\u306f StartTLS \u901a\u4fe1\u3067\u306e\u4f7f\u7528\u304c\u8a31\u53ef\u3055\u308c\u308b SSL \u6697\u53f7\u5316\u65b9\u5f0f\u7fa4\u306e\u540d\u524d\u3002 \u3053\u306e\u8a2d\u5b9a\u5c5e\u6027\u3078\u306e\u5909\u66f4\u306f\u305f\u3060\u3061\u306b\u6709\u52b9\u306b\u306a\u308a\u307e\u3059\u304c\u3001\u5f71\u97ff\u304c\u53ca\u3076\u306e\u306f\u5909\u66f4\u5f8c\u306b\u4f5c\u6210\u3055\u308c\u305f\u65b0\u3057\u3044 SSL/TLS \u30d9\u30fc\u30b9\u306e\u30bb\u30c3\u30b7\u30e7\u30f3\u3060\u3051\u3067\u3059 |
| | | ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_SSL_CIPHERS_268=An unexpected \ |
| | | ### error occurred while processing the ds-cfg-ssl-protocol attribute in \ |
| | | ### configuration entry %s, which is used to specify the names of the SSL cipher \ |
| | | ### suites to allow for SSL/TLS sessions: %s |
| | | SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_SSL_CIPHERS_268=An unexpected error occurred while processing the ds-cfg-ssl-protocol attribute in configuration entry %s, which is used to specify the names of the SSL cipher suites to allow for SSL/TLS sessions: %s |
| | | INFO_LDAP_CONNHANDLER_NEW_SSL_PROTOCOLS_269=\u69cb\u6210\u30a8\u30f3\u30c8\u30ea %2$s \u3067\u3001ds-cfg-ssl-protocol \u5c5e\u6027\u306e\u5024\u304c %1$s \u306b\u66f4\u65b0\u3055\u308c\u307e\u3057\u305f |
| | | INFO_LDAP_CONNHANDLER_NEW_SSL_CIPHERS_270=\u69cb\u6210\u30a8\u30f3\u30c8\u30ea %2$s \u3067\u3001ds-cfg-ssl-cipher-suite \u5c5e\u6027\u306e\u5024\u304c %1$s \u306b\u66f4\u65b0\u3055\u308c\u307e\u3057\u305f |
| | | MILD_ERR_LDAP_TLS_EXISTING_SECURITY_PROVIDER_271=\u3053\u306e\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u63a5\u7d9a\u3067 TLS \u63a5\u7d9a\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u30fc\u30d7\u30ed\u30d0\u30a4\u30c0\u3092\u6709\u52b9\u306b\u3067\u304d\u307e\u305b\u3093\u3002\u3059\u3067\u306b %s \u30d7\u30ed\u30d0\u30a4\u30c0\u3092\u4f7f\u7528\u3057\u3066\u3044\u307e\u3059\u3002 StartTLS \u306f\u3001\u5e73\u6587\u63a5\u7d9a\u3067\u306e\u307f\u4f7f\u7528\u3067\u304d\u307e\u3059 |
| | |
| | | MILD_ERR_LDAP_INTERMEDIATE_RESPONSE_CANNOT_DECODE_VALUE_317=\u4e2d\u9593\u5fdc\u7b54\u5024\u3092\u5fa9\u53f7\u5316\u4e2d\u306b\u30a8\u30e9\u30fc\u304c\u767a\u751f\u3057\u307e\u3057\u305f: %s |
| | | MILD_ERR_LDAP_INTERMEDIATE_RESPONSE_INVALID_ELEMENT_TYPE_318=\u4e2d\u9593\u5fdc\u7b54\u30b7\u30fc\u30b1\u30f3\u30b9\u8981\u7d20\u306b\u3001OID \u307e\u305f\u306f\u5024\u306b\u9069\u3055\u306a\u3044\u7121\u52b9\u306a BER \u30bf\u30a4\u30d7 %s \u304c\u542b\u307e\u308c\u3066\u3044\u307e\u3057\u305f |
| | | INFO_LDAP_CONNHANDLER_DESCRIPTION_BACKLOG_319=\u30ad\u30e5\u30fc\u30b5\u30a4\u30ba\u3092\u53d7\u3051\u5165\u308c\u307e\u3059\u3002\u3053\u308c\u306f\u3001\u62d2\u5426\u3055\u308c\u308b\u524d\u306b\u30d0\u30c3\u30af\u30ed\u30b0\u306e\u30ad\u30e5\u30fc\u306b\u5165\u308c\u308b\u3053\u3068\u304c\u8a31\u53ef\u3055\u308c\u308b\u65b0\u3057\u3044\u63a5\u7d9a\u8a66\u884c\u306e\u56de\u6570\u3092\u5236\u5fa1\u3057\u307e\u3059\u3002 \u3053\u308c\u3092\u5909\u66f4\u3059\u308b\u5fc5\u8981\u304c\u3042\u308b\u306e\u306f\u3001\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u30b5\u30fc\u30d0\u30fc\u304c\u591a\u6570\u306e\u65b0\u3057\u3044\u63a5\u7d9a\u8a66\u884c\u3092\u540c\u6642\u306b\u53d7\u3051\u53d6\u308b\u3053\u3068\u304c\u4e88\u671f\u3055\u308c\u308b\u5834\u5408\u3060\u3051\u306e\u306f\u305a\u3067\u3059\u3002 \u3053\u306e\u8a2d\u5b9a\u5c5e\u6027\u3078\u306e\u5909\u66f4\u306f\u3001\u63a5\u7d9a\u30cf\u30f3\u30c9\u30e9\u3092\u7121\u52b9\u306b\u3057\u3066\u518d\u5ea6\u6709\u52b9\u306b\u3059\u308b\u304b\u3001\u307e\u305f\u306f\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u30b5\u30fc\u30d0\u30fc\u3092\u518d\u8d77\u52d5\u3059\u308b\u307e\u3067\u6709\u52b9\u306b\u306a\u308a\u307e\u305b\u3093 |
| | | ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_BACKLOG_320=An unexpected error \ |
| | | ### occurred while processing the ds-cfg-accept-backlog attribute in \ |
| | | ### configuration entry %s, which is used to specify the accept backlog size: %s |
| | | ###SEVERE_ERR_MVFILTER_INVALID_LDAP_FILTER_TYPE_321=The provided LDAP filter \ |
| | | ### "%s" cannot be used as a matched values filter because filters of type %s are \ |
| | | ### not allowed for use in matched values filters |
| | | ###SEVERE_ERR_MVFILTER_INVALID_DN_ATTRIBUTES_FLAG_322=The provided LDAP filter \ |
| | | ### "%s" cannot be used as a matched values filter because it is an extensible \ |
| | | ### match filter that contains the dnAttributes flag, which is not allowed for \ |
| | | ### matched values filters |
| | | ###SEVERE_ERR_MVFILTER_INVALID_AVA_SEQUENCE_SIZE_323=The provided matched values \ |
| | | ### filter could not be decoded because there were an invalid number of elements \ |
| | | ### in the attribute value assertion (expected 2, got %d) |
| | | ###SEVERE_ERR_MVFILTER_CANNOT_DECODE_AVA_324=An error occurred while attempting \ |
| | | ### to decode the attribute value assertion in the provided matched values \ |
| | | ### filter: %s |
| | | ###SEVERE_ERR_MVFILTER_INVALID_SUBSTRING_SEQUENCE_SIZE_325=The provided matched \ |
| | | ### values filter could not be decoded because there were an invalid number of \ |
| | | ### elements in the substring sequence (expected 2, got %d) |
| | | ###SEVERE_ERR_MVFILTER_NO_SUBSTRING_ELEMENTS_326=The provided matched values \ |
| | | ### filter could not be decoded because there were no subInitial, subAny, or \ |
| | | ### subFinal components in the substring filter |
| | | ###SEVERE_ERR_MVFILTER_MULTIPLE_SUBINITIALS_327=The provided matched values \ |
| | | ### filter could not be decoded because there were multiple subInitial components \ |
| | | ### in the substring filter |
| | | ###SEVERE_ERR_MVFILTER_MULTIPLE_SUBFINALS_328=The provided matched values filter \ |
| | | ### could not be decoded because there were multiple subFinal components in the \ |
| | | ### substring filter |
| | | ###SEVERE_ERR_MVFILTER_INVALID_SUBSTRING_ELEMENT_TYPE_329=The provided matched \ |
| | | ### values filter could not be decoded because there was an invalid element of \ |
| | | ### type %s in the substring filter |
| | | ###SEVERE_ERR_MVFILTER_CANNOT_DECODE_SUBSTRINGS_330=The provided matched values \ |
| | | ### filter could not be decoded because an error occurred while decoding the \ |
| | | ### substring filter component: %s |
| | | ###SEVERE_ERR_MVFILTER_CANNOT_DECODE_PRESENT_TYPE_331=The provided matched \ |
| | | ### values filter could not be decoded because an error occurred while decoding \ |
| | | ### the presence filter component: %s |
| | | ###SEVERE_ERR_MVFILTER_INVALID_EXTENSIBLE_SEQUENCE_SIZE_332=The provided matched \ |
| | | ### values filter could not be decoded because there were an invalid number of \ |
| | | ### elements in the extensible match sequence (expected 2 or 3, found %d) |
| | | ###SEVERE_ERR_MVFILTER_MULTIPLE_MATCHING_RULE_IDS_333=The provided matched \ |
| | | ### values filter could not be decoded because there were multiple matching rule \ |
| | | ### ID elements found in the extensible match filter sequence |
| | | ###SEVERE_ERR_MVFILTER_MULTIPLE_ATTRIBUTE_TYPES_334=The provided matched values \ |
| | | ### filter could not be decoded because there were multiple attribute type \ |
| | | ### elements found in the extensible match filter sequence |
| | | ###SEVERE_ERR_MVFILTER_MULTIPLE_ASSERTION_VALUES_335=The provided matched values \ |
| | | ### filter could not be decoded because there were multiple assertion value \ |
| | | ### elements found in the extensible match filter sequence |
| | | ###SEVERE_ERR_MVFILTER_INVALID_EXTENSIBLE_ELEMENT_TYPE_336=The provided matched \ |
| | | ### values filter could not be decoded because there was an invalid element of \ |
| | | ### type %s in the extensible match filter |
| | | ###SEVERE_ERR_MVFILTER_CANNOT_DECODE_EXTENSIBLE_MATCH_337=The provided matched \ |
| | | ### values filter could not be decoded because an error occurred while decoding \ |
| | | ### the extensible match filter component: %s |
| | | ###SEVERE_ERR_MVFILTER_INVALID_ELEMENT_TYPE_338=The provided matched values \ |
| | | ### filter could not be decoded because it had an invalid BER type of %s |
| | | ###SEVERE_ERR_MATCHEDVALUES_NO_CONTROL_VALUE_339=Cannot decode the provided \ |
| | | ### matched values control because it does not have a value |
| | | ###SEVERE_ERR_MATCHEDVALUES_CANNOT_DECODE_VALUE_AS_SEQUENCE_340=Cannot decode \ |
| | | ### the provided matched values control because an error occurred while \ |
| | | ### attempting to decode the value as an ASN.1 sequence: %s |
| | | ###SEVERE_ERR_MATCHEDVALUES_NO_FILTERS_341=Cannot decode the provided matched \ |
| | | ### values control because the control value does not specify any filters for use \ |
| | | ### in matching attribute values |
| | | ###SEVERE_ERR_PWEXPIRED_CONTROL_INVALID_VALUE_342=Cannot decode the provided \ |
| | | ### control as a password expired control because the provided control had a \ |
| | | ### value that could not be parsed as an integer |
| | | ###SEVERE_ERR_PWEXPIRING_NO_CONTROL_VALUE_343=Cannot decode the provided \ |
| | | ### password expiring control because it does not have a value |
| | | ###SEVERE_ERR_PWEXPIRING_CANNOT_DECODE_SECONDS_UNTIL_EXPIRATION_344=Cannot \ |
| | | ### decode the provided control as a password expiring control because an error \ |
| | | ### occurred while attempting to decode the number of seconds until expiration: \ |
| | | ### %s |
| | | SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_BACKLOG_320=An unexpected error occurred while processing the ds-cfg-accept-backlog attribute in configuration entry %s, which is used to specify the accept backlog size: %s |
| | | SEVERE_ERR_MVFILTER_INVALID_LDAP_FILTER_TYPE_321=The provided LDAP filter "%s" cannot be used as a matched values filter because filters of type %s are not allowed for use in matched values filters |
| | | SEVERE_ERR_MVFILTER_INVALID_DN_ATTRIBUTES_FLAG_322=The provided LDAP filter "%s" cannot be used as a matched values filter because it is an extensible match filter that contains the dnAttributes flag, which is not allowed for matched values filters |
| | | SEVERE_ERR_MVFILTER_INVALID_AVA_SEQUENCE_SIZE_323=The provided matched values filter could not be decoded because there were an invalid number of elements in the attribute value assertion (expected 2, got %d) |
| | | SEVERE_ERR_MVFILTER_CANNOT_DECODE_AVA_324=An error occurred while attempting to decode the attribute value assertion in the provided matched values filter: %s |
| | | SEVERE_ERR_MVFILTER_INVALID_SUBSTRING_SEQUENCE_SIZE_325=The provided matched values filter could not be decoded because there were an invalid number of elements in the substring sequence (expected 2, got %d) |
| | | SEVERE_ERR_MVFILTER_NO_SUBSTRING_ELEMENTS_326=The provided matched values filter could not be decoded because there were no subInitial, subAny, or subFinal components in the substring filter |
| | | SEVERE_ERR_MVFILTER_MULTIPLE_SUBINITIALS_327=The provided matched values filter could not be decoded because there were multiple subInitial components in the substring filter |
| | | SEVERE_ERR_MVFILTER_MULTIPLE_SUBFINALS_328=The provided matched values filter could not be decoded because there were multiple subFinal components in the substring filter |
| | | SEVERE_ERR_MVFILTER_INVALID_SUBSTRING_ELEMENT_TYPE_329=The provided matched values filter could not be decoded because there was an invalid element of type %s in the substring filter |
| | | SEVERE_ERR_MVFILTER_CANNOT_DECODE_SUBSTRINGS_330=The provided matched values filter could not be decoded because an error occurred while decoding the substring filter component: %s |
| | | SEVERE_ERR_MVFILTER_CANNOT_DECODE_PRESENT_TYPE_331=The provided matched values filter could not be decoded because an error occurred while decoding the presence filter component: %s |
| | | SEVERE_ERR_MVFILTER_INVALID_EXTENSIBLE_SEQUENCE_SIZE_332=The provided matched values filter could not be decoded because there were an invalid number of elements in the extensible match sequence (expected 2 or 3, found %d) |
| | | SEVERE_ERR_MVFILTER_MULTIPLE_MATCHING_RULE_IDS_333=The provided matched values filter could not be decoded because there were multiple matching rule ID elements found in the extensible match filter sequence |
| | | SEVERE_ERR_MVFILTER_MULTIPLE_ATTRIBUTE_TYPES_334=The provided matched values filter could not be decoded because there were multiple attribute type elements found in the extensible match filter sequence |
| | | SEVERE_ERR_MVFILTER_MULTIPLE_ASSERTION_VALUES_335=The provided matched values filter could not be decoded because there were multiple assertion value elements found in the extensible match filter sequence |
| | | SEVERE_ERR_MVFILTER_INVALID_EXTENSIBLE_ELEMENT_TYPE_336=The provided matched values filter could not be decoded because there was an invalid element of type %s in the extensible match filter |
| | | SEVERE_ERR_MVFILTER_CANNOT_DECODE_EXTENSIBLE_MATCH_337=The provided matched values filter could not be decoded because an error occurred while decoding the extensible match filter component: %s |
| | | SEVERE_ERR_MVFILTER_INVALID_ELEMENT_TYPE_338=The provided matched values filter could not be decoded because it had an invalid BER type of %s |
| | | SEVERE_ERR_MATCHEDVALUES_NO_CONTROL_VALUE_339=Cannot decode the provided matched values control because it does not have a value |
| | | SEVERE_ERR_MATCHEDVALUES_CANNOT_DECODE_VALUE_AS_SEQUENCE_340=Cannot decode the provided matched values control because an error occurred while attempting to decode the value as an ASN.1 sequence: %s |
| | | SEVERE_ERR_MATCHEDVALUES_NO_FILTERS_341=Cannot decode the provided matched values control because the control value does not specify any filters for use in matching attribute values |
| | | SEVERE_ERR_PWEXPIRED_CONTROL_INVALID_VALUE_342=Cannot decode the provided control as a password expired control because the provided control had a value that could not be parsed as an integer |
| | | SEVERE_ERR_PWEXPIRING_NO_CONTROL_VALUE_343=Cannot decode the provided password expiring control because it does not have a value |
| | | SEVERE_ERR_PWEXPIRING_CANNOT_DECODE_SECONDS_UNTIL_EXPIRATION_344=Cannot decode the provided control as a password expiring control because an error occurred while attempting to decode the number of seconds until expiration: %s |
| | | MILD_WARN_LDAP_CLIENT_DUPLICATE_MESSAGE_ID_345=\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u30b5\u30fc\u30d0\u30fc\u306f\u3059\u3067\u306b\u3001\u540c\u3058\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u63a5\u7d9a\u3067\u540c\u3058\u30e1\u30c3\u30bb\u30fc\u30b8 ID %d \u306e\u5225\u306e\u8981\u6c42\u3092\u51e6\u7406\u3057\u3066\u3044\u307e\u3059 |
| | | MILD_WARN_LDAP_CLIENT_CANNOT_ENQUEUE_346=\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u8981\u6c42\u3092\u30ef\u30fc\u30af\u30ad\u30e5\u30fc\u306b\u8ffd\u52a0\u4e2d\u306b\u3001\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u30b5\u30fc\u30d0\u30fc\u3067\u4e88\u671f\u3057\u306a\u3044\u30a8\u30e9\u30fc\u304c\u767a\u751f\u3057\u307e\u3057\u305f: %s |
| | | INFO_JMX_CONNHANDLER_DESCRIPTION_LISTEN_PORT_347=\u3053\u306e\u63a5\u7d9a\u30cf\u30f3\u30c9\u30e9\u304c\u7ba1\u7406\u63a5\u7d9a\u3092\u53d7\u3051\u5165\u308c\u308b\u3053\u3068\u304c\u3067\u304d\u308b TCP \u30dd\u30fc\u30c8\u3002 \u3053\u306e\u8a2d\u5b9a\u5c5e\u6027\u3078\u306e\u5909\u66f4\u306f\u3001\u63a5\u7d9a\u30cf\u30f3\u30c9\u30e9\u3092\u7121\u52b9\u306b\u3057\u3066\u518d\u5ea6\u6709\u52b9\u306b\u3059\u308b\u304b\u3001\u307e\u305f\u306f\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u30b5\u30fc\u30d0\u30fc\u3092\u518d\u8d77\u52d5\u3059\u308b\u307e\u3067\u6709\u52b9\u306b\u306a\u308a\u307e\u305b\u3093 |
| | | ###SEVERE_ERR_JMX_CONNHANDLER_NO_LISTEN_PORT_348=No listen port was defined \ |
| | | ### using configuration ds-cfg-listen-port in configuration entry %s. This is a \ |
| | | ### required attribute |
| | | ###SEVERE_ERR_JMX_CONNHANDLER_CANNOT_DETERMINE_LISTEN_PORT_349=An unexpected \ |
| | | ### error occurred while processing the ds-cfg-listen-port attribute in \ |
| | | ### configuration entry %s, which is used to specify the port on which to listen \ |
| | | ### for client connections: %s |
| | | SEVERE_ERR_JMX_CONNHANDLER_NO_LISTEN_PORT_348=No listen port was defined using configuration ds-cfg-listen-port in configuration entry %s. This is a required attribute |
| | | SEVERE_ERR_JMX_CONNHANDLER_CANNOT_DETERMINE_LISTEN_PORT_349=An unexpected error occurred while processing the ds-cfg-listen-port attribute in configuration entry %s, which is used to specify the port on which to listen for client connections: %s |
| | | INFO_JMX_CONNHANDLER_DESCRIPTION_USE_SSL_350=\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u304b\u3089\u306e\u63a5\u7d9a\u3092\u53d7\u3051\u4ed8\u3051\u308b\u3068\u304d\u306b\u3053\u306e\u63a5\u7d9a\u30cf\u30f3\u30c9\u30e9\u3067 SSL \u3092\u4f7f\u7528\u3059\u308b\u304b\u3069\u3046\u304b\u3092\u793a\u3057\u307e\u3059\u3002 \u3053\u306e\u8a2d\u5b9a\u5c5e\u6027\u3078\u306e\u5909\u66f4\u306f\u3001\u63a5\u7d9a\u30cf\u30f3\u30c9\u30e9\u3092\u7121\u52b9\u306b\u3057\u3066\u518d\u5ea6\u6709\u52b9\u306b\u3059\u308b\u304b\u3001\u307e\u305f\u306f\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u30b5\u30fc\u30d0\u30fc\u3092\u518d\u8d77\u52d5\u3059\u308b\u307e\u3067\u6709\u52b9\u306b\u306a\u308a\u307e\u305b\u3093 |
| | | ###SEVERE_ERR_JMX_CONNHANDLER_CANNOT_DETERMINE_USE_SSL_351=An unexpected error \ |
| | | ### occurred while processing the ds-cfg-use-ssl attribute in configuration entry \ |
| | | ### %s, which is used to indicate whether to use SSL when accepting client \ |
| | | ### connections: %s |
| | | SEVERE_ERR_JMX_CONNHANDLER_CANNOT_DETERMINE_USE_SSL_351=An unexpected error occurred while processing the ds-cfg-use-ssl attribute in configuration entry %s, which is used to indicate whether to use SSL when accepting client connections: %s |
| | | INFO_JMX_CONNHANDLER_DESCRIPTION_SSL_CERT_NICKNAME_352=SSL \u30d9\u30fc\u30b9\u306e\u63a5\u7d9a\u3092\u53d7\u3051\u4ed8\u3051\u308b\u3068\u304d\u3001\u307e\u305f\u306f StartTLS \u30cd\u30b4\u30b7\u30a8\u30fc\u30b7\u30e7\u30f3\u3092\u5b9f\u884c\u3059\u308b\u3068\u304d\u306b\u63a5\u7d9a\u30cf\u30f3\u30c9\u30e9\u3067\u4f7f\u7528\u3059\u3079\u304d\u8a3c\u660e\u66f8\u306e\u30cb\u30c3\u30af\u30cd\u30fc\u30e0\u3002 \u3053\u306e\u8a2d\u5b9a\u5c5e\u6027\u3078\u306e\u5909\u66f4\u306f\u3001\u63a5\u7d9a\u30cf\u30f3\u30c9\u30e9\u3092\u7121\u52b9\u306b\u3057\u3066\u518d\u5ea6\u6709\u52b9\u306b\u3059\u308b\u304b\u3001\u307e\u305f\u306f\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u30b5\u30fc\u30d0\u30fc\u3092\u518d\u8d77\u52d5\u3059\u308b\u307e\u3067\u6709\u52b9\u306b\u306a\u308a\u307e\u305b\u3093 |
| | | ###SEVERE_ERR_JMX_CONNHANDLER_CANNOT_DETERMINE_SSL_CERT_NICKNAME_353=An \ |
| | | ### unexpected error occurred while processing the ds-cfg-ssl-cert-nickname \ |
| | | ### attribute in configuration entry %s, which is used to specify the nickname of \ |
| | | ### the certificate to use for accepting SSL/TLS connections: %s |
| | | ###SEVERE_ERR_PWPOLICYREQ_CONTROL_HAS_VALUE_354=Cannot decode the provided \ |
| | | ### control as a password policy request control because the provided control had \ |
| | | ### a value but the password policy request control should not have a value |
| | | ###SEVERE_ERR_PWPOLICYRES_NO_CONTROL_VALUE_355=Cannot decode the provided \ |
| | | ### password policy response control because it does not have a value |
| | | ###SEVERE_ERR_PWPOLICYRES_INVALID_WARNING_TYPE_356=Cannot decode the provided \ |
| | | ### password policy response control because the warning element has an invalid \ |
| | | ### type of %s |
| | | ###SEVERE_ERR_PWPOLICYRES_INVALID_ERROR_TYPE_357=Cannot decode the provided \ |
| | | ### password policy response control because the error element has an invalid \ |
| | | ### type of %d |
| | | ###SEVERE_ERR_PWPOLICYRES_INVALID_ELEMENT_TYPE_358=Cannot decode the provided \ |
| | | ### password policy response control because the value sequence has an element \ |
| | | ### with an invalid type of %s |
| | | ###SEVERE_ERR_PWPOLICYRES_DECODE_ERROR_359=Cannot decode the provided password \ |
| | | ### policy response control: %s |
| | | SEVERE_ERR_JMX_CONNHANDLER_CANNOT_DETERMINE_SSL_CERT_NICKNAME_353=An unexpected error occurred while processing the ds-cfg-ssl-cert-nickname attribute in configuration entry %s, which is used to specify the nickname of the certificate to use for accepting SSL/TLS connections: %s |
| | | SEVERE_ERR_PWPOLICYREQ_CONTROL_HAS_VALUE_354=Cannot decode the provided control as a password policy request control because the provided control had a value but the password policy request control should not have a value |
| | | SEVERE_ERR_PWPOLICYRES_NO_CONTROL_VALUE_355=Cannot decode the provided password policy response control because it does not have a value |
| | | SEVERE_ERR_PWPOLICYRES_INVALID_WARNING_TYPE_356=Cannot decode the provided password policy response control because the warning element has an invalid type of %s |
| | | SEVERE_ERR_PWPOLICYRES_INVALID_ERROR_TYPE_357=Cannot decode the provided password policy response control because the error element has an invalid type of %d |
| | | SEVERE_ERR_PWPOLICYRES_INVALID_ELEMENT_TYPE_358=Cannot decode the provided password policy response control because the value sequence has an element with an invalid type of %s |
| | | SEVERE_ERR_PWPOLICYRES_DECODE_ERROR_359=Cannot decode the provided password policy response control: %s |
| | | INFO_PWPERRTYPE_DESCRIPTION_PASSWORD_EXPIRED_360=passwordExpired |
| | | INFO_PWPERRTYPE_DESCRIPTION_ACCOUNT_LOCKED_361=accountLocked |
| | | INFO_PWPERRTYPE_DESCRIPTION_CHANGE_AFTER_RESET_362=changeAfterReset |
| | |
| | | MILD_ERR_PROXYAUTH1_UNUSABLE_ACCOUNT_372=\u30d7\u30ed\u30ad\u30b7\u8a2d\u5b9a\u3055\u308c\u305f\u8a8d\u53ef V1 \u5236\u5fa1\u3092\u30e6\u30fc\u30b6\u30fc %s \u306b\u5bfe\u3057\u3066\u4f7f\u7528\u3059\u308b\u3053\u3068\u306f\u3001\u30d1\u30b9\u30ef\u30fc\u30c9\u30dd\u30ea\u30b7\u30fc\u69cb\u6210\u306b\u3088\u3063\u3066\u8a31\u53ef\u3055\u308c\u307e\u305b\u3093 |
| | | MILD_ERR_PROXYAUTH2_CANNOT_LOCK_USER_373=\u30d7\u30ed\u30ad\u30b7\u8a2d\u5b9a\u3055\u308c\u305f\u8a8d\u53ef V2 \u5236\u5fa1\u59a5\u5f53\u6027\u691c\u67fb\u306e\u305f\u3081\u306e\u3001\u30e6\u30fc\u30b6\u30fc\u30a8\u30f3\u30c8\u30ea %s \u306e\u30ed\u30c3\u30af\u3092\u53d6\u5f97\u3067\u304d\u307e\u305b\u3093 |
| | | MILD_ERR_PROXYAUTH2_UNUSABLE_ACCOUNT_374=\u30d7\u30ed\u30ad\u30b7\u8a2d\u5b9a\u3055\u308c\u305f\u8a8d\u53ef V2 \u5236\u5fa1\u3092\u30e6\u30fc\u30b6\u30fc %s \u306b\u5bfe\u3057\u3066\u4f7f\u7528\u3059\u308b\u3053\u3068\u306f\u3001\u30d1\u30b9\u30ef\u30fc\u30c9\u30dd\u30ea\u30b7\u30fc\u69cb\u6210\u306b\u3088\u3063\u3066\u8a31\u53ef\u3055\u308c\u307e\u305b\u3093 |
| | | ###SEVERE_ERR_ACCTUSABLEREQ_CONTROL_HAS_VALUE_375=Cannot decode the provided \ |
| | | ### control as an account availability request control because the provided \ |
| | | ### control had a value but the account availability request control should not \ |
| | | ### have a value |
| | | ###SEVERE_ERR_ACCTUSABLERES_NO_CONTROL_VALUE_376=Cannot decode the provided \ |
| | | ### account availability response control because it does not have a value |
| | | ###SEVERE_ERR_ACCTUSABLERES_UNKNOWN_UNAVAILABLE_TYPE_377=The account \ |
| | | ### availability response control indicated that the account was unavailable but \ |
| | | ### had an unknown unavailable element type of %s |
| | | ###SEVERE_ERR_ACCTUSABLERES_UNKNOWN_VALUE_ELEMENT_TYPE_378=The account \ |
| | | ### availability response control had an unknown ACCOUNT_USABLE_RESPONSE element \ |
| | | ### type of %s |
| | | ###SEVERE_ERR_ACCTUSABLERES_DECODE_ERROR_379=Cannot decode the provided account \ |
| | | ### availability response control: %s |
| | | ###SEVERE_ERR_ADDRESSMASK_PREFIX_DECODE_ERROR_380=Cannot decode the provided \ |
| | | ### address mask prefix because an invalid value was specified. The permitted \ |
| | | ### values for IPv4are 0 to32 and for IPv6 0 to128 |
| | | ###SEVERE_ERR_ADDRESSMASK_WILDCARD_DECODE_ERROR_381=Cannot decode the provided \ |
| | | ### address mask because an prefix mask was specified with an wild card "*" match \ |
| | | ### character |
| | | ###SEVERE_ERR_ADDRESSMASK_FORMAT_DECODE_ERROR_382=Cannot decode the provided \ |
| | | ### address mask because the it has an invalid format |
| | | SEVERE_ERR_ACCTUSABLEREQ_CONTROL_HAS_VALUE_375=Cannot decode the provided control as an account availability request control because the provided control had a value but the account availability request control should not have a value |
| | | SEVERE_ERR_ACCTUSABLERES_NO_CONTROL_VALUE_376=Cannot decode the provided account availability response control because it does not have a value |
| | | SEVERE_ERR_ACCTUSABLERES_UNKNOWN_UNAVAILABLE_TYPE_377=The account availability response control indicated that the account was unavailable but had an unknown unavailable element type of %s |
| | | SEVERE_ERR_ACCTUSABLERES_UNKNOWN_VALUE_ELEMENT_TYPE_378=The account availability response control had an unknown ACCOUNT_USABLE_RESPONSE element type of %s |
| | | SEVERE_ERR_ACCTUSABLERES_DECODE_ERROR_379=Cannot decode the provided account availability response control: %s |
| | | SEVERE_ERR_ADDRESSMASK_PREFIX_DECODE_ERROR_380=Cannot decode the provided address mask prefix because an invalid value was specified. The permitted values for IPv4are 0 to32 and for IPv6 0 to128 |
| | | SEVERE_ERR_ADDRESSMASK_WILDCARD_DECODE_ERROR_381=Cannot decode the provided address mask because an prefix mask was specified with an wild card "*" match character |
| | | SEVERE_ERR_ADDRESSMASK_FORMAT_DECODE_ERROR_382=Cannot decode the provided address mask because the it has an invalid format |
| | | MILD_ERR_LDAP_NO_CLEAR_SECURITY_PROVIDER_383=LDAP \u63a5\u7d9a\u30cf\u30f3\u30c9\u30e9 %s \u306f\u5e73\u6587\u5fdc\u7b54\u3092\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u306b\u9001\u4fe1\u3067\u304d\u307e\u305b\u3093\u3067\u3057\u305f\u3002\u5e73\u6587\u306e\u63a5\u7d9a\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u30fc\u30d7\u30ed\u30d0\u30a4\u30c0\u3078\u306e\u53c2\u7167\u304c\u3042\u308a\u307e\u305b\u3093 |
| | | MILD_ERR_LDAP_ATTRIBUTE_DUPLICATE_VALUES_384=\u6307\u5b9a\u3055\u308c\u305f LDAP \u5c5e\u6027 %s \u306b\u3001\u91cd\u8907\u3059\u308b\u5024\u304c\u542b\u307e\u308c\u3066\u3044\u307e\u3059 |
| | | MILD_ERR_LDAP_FILTER_UNKNOWN_MATCHING_RULE_385=\u6307\u5b9a\u3055\u308c\u305f LDAP \u691c\u7d22\u30d5\u30a3\u30eb\u30bf\u304c\u4e0d\u660e\u306a\u30de\u30c3\u30c1\u30f3\u30b0\u30eb\u30fc\u30eb %s \u3092\u53c2\u7167\u3057\u3066\u3044\u307e\u3059 |
| | | MILD_ERR_LDAP_FILTER_VALUE_WITH_NO_ATTR_OR_MR_386=\u6307\u5b9a\u3055\u308c\u305f LDAP \u691c\u7d22\u30d5\u30a3\u30eb\u30bf\u306b\u8868\u660e\u5024\u304c\u3042\u308a\u307e\u3059\u304c\u3001\u5c5e\u6027\u5024\u307e\u305f\u306f\u30de\u30c3\u30c1\u30f3\u30b0\u30eb\u30fc\u30eb ID \u304c\u542b\u307e\u308c\u3066\u3044\u307e\u305b\u3093 |
| | | ###FATAL_ERR_LDAP_REQHANDLER_DETECTED_JVM_ISSUE_CR6322825_387=Unable to call \ |
| | | ### select() in the LDAP connection handler: %s. It appears that your JVM may \ |
| | | ### be susceptible to the issue described at \ |
| | | ### http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6322825, and it is unable \ |
| | | ### to handle LDAP requests in its current configuration. Please upgrade to a \ |
| | | ### newer JVM that does not exhibit this behavior (Java 5.0 Update 8 or higher) \ |
| | | ### or set the number of available file descriptors to a value greater than or \ |
| | | ### equal to 8193 (e.g., by issuing the command 'ulimit -n 8193') before starting \ |
| | | ### the Directory Server |
| | | FATAL_ERR_LDAP_REQHANDLER_DETECTED_JVM_ISSUE_CR6322825_387=Unable to call select() in the LDAP connection handler: %s. It appears that your JVM may be susceptible to the issue described at http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6322825, and it is unable to handle LDAP requests in its current configuration. Please upgrade to a newer JVM that does not exhibit this behavior (Java 5.0 Update 8 or higher) or set the number of available file descriptors to a value greater than or equal to 8193 (e.g., by issuing the command 'ulimit -n 8193') before starting the Directory Server |
| | | MILD_ERR_PROXYAUTH1_CONTROL_NOT_CRITICAL_388=\u8981\u6c42\u306e\u51e6\u7406\u3092\u62d2\u5426\u3057\u307e\u3059\u3002\u30af\u30ea\u30c6\u30a3\u30ab\u30eb\u3068\u30de\u30fc\u30af\u3055\u308c\u3066\u3044\u306a\u3044\u3001\u30d7\u30ed\u30ad\u30b7\u8a2d\u5b9a\u3055\u308c\u305f\u8a8d\u53ef V1 \u5236\u5fa1\u304c\u542b\u307e\u308c\u3066\u3044\u307e\u3059\u3002 \u30d7\u30ed\u30ad\u30b7\u8a2d\u5b9a\u3055\u308c\u305f\u8a8d\u53ef\u5236\u5fa1\u306b\u306f\u3001\u5e38\u306b "true" \u306e\u91cd\u5927\u6027\u304c\u5fc5\u8981\u3067\u3059 |
| | | MILD_ERR_PROXYAUTH2_CONTROL_NOT_CRITICAL_389=\u8981\u6c42\u306e\u51e6\u7406\u3092\u62d2\u5426\u3057\u307e\u3059\u3002\u30af\u30ea\u30c6\u30a3\u30ab\u30eb\u3068\u30de\u30fc\u30af\u3055\u308c\u3066\u3044\u306a\u3044\u3001\u30d7\u30ed\u30ad\u30b7\u8a2d\u5b9a\u3055\u308c\u305f\u8a8d\u53ef V2 \u5236\u5fa1\u304c\u542b\u307e\u308c\u3066\u3044\u307e\u3059\u3002 \u30d7\u30ed\u30ad\u30b7\u8a2d\u5b9a\u3055\u308c\u305f\u8a8d\u53ef\u5236\u5fa1\u306b\u306f\u3001\u5e38\u306b "true" \u306e\u91cd\u5927\u6027\u304c\u5fc5\u8981\u3067\u3059 |
| | | INFO_LDAP_CONNHANDLER_DESCRIPTION_KEYMANAGER_DN_390=\u3053\u306e LDAP \u63a5\u7d9a\u30cf\u30f3\u30c9\u30e9\u3067\u4f7f\u7528\u3059\u3079\u304d\u9375\u30de\u30cd\u30fc\u30b8\u30e3\u30fc\u30d7\u30ed\u30d0\u30a4\u30c0\u306e\u69cb\u6210\u30a8\u30f3\u30c8\u30ea\u306e DN\u3002 \u3053\u306e\u5c5e\u6027\u3078\u306e\u5909\u66f4\u306f\u305f\u3060\u3061\u306b\u6709\u52b9\u306b\u306a\u308a\u307e\u3059\u304c\u3001\u5bfe\u8c61\u3068\u306a\u308b\u306e\u306f\u3001\u95a2\u9023\u4ed8\u3051\u3089\u308c\u305f\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u63a5\u7d9a\u306e\u9375\u30de\u30cd\u30fc\u30b8\u30e3\u30fc\u30d7\u30ed\u30d0\u30a4\u30c0\u3078\u306e\u4ee5\u964d\u306e\u30a2\u30af\u30bb\u30b9\u8a66\u884c\u3060\u3051\u3067\u3059 |
| | | ###SEVERE_ERR_LDAP_CONNHANDLER_INVALID_KEYMANAGER_DN_391=Configuration attribute \ |
| | | ### ds-cfg-key-manager-provider of configuration entry %s has an invalid value \ |
| | | ### %s which does not reference an enabled key manager provider |
| | | ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_KEYMANAGER_DN_392=An error \ |
| | | ### occurred while processing the ds-cfg-key-manager-provider attribute in \ |
| | | ### configuration entry %s, which is used to specify the key manager provider for \ |
| | | ### use with the LDAP connection handler: %s |
| | | SEVERE_ERR_LDAP_CONNHANDLER_INVALID_KEYMANAGER_DN_391=Configuration attribute ds-cfg-key-manager-provider of configuration entry %s has an invalid value %s which does not reference an enabled key manager provider |
| | | SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_KEYMANAGER_DN_392=An error occurred while processing the ds-cfg-key-manager-provider attribute in configuration entry %s, which is used to specify the key manager provider for use with the LDAP connection handler: %s |
| | | INFO_LDAP_CONNHANDLER_DESCRIPTION_TRUSTMANAGER_DN_393=\u3053\u306e LDAP \u63a5\u7d9a\u30cf\u30f3\u30c9\u30e9\u3067\u4f7f\u7528\u3059\u3079\u304d\u30c8\u30e9\u30b9\u30c8\u30de\u30cd\u30fc\u30b8\u30e3\u30fc\u30d7\u30ed\u30d0\u30a4\u30c0\u306e\u69cb\u6210\u30a8\u30f3\u30c8\u30ea\u306e DN\u3002 \u3053\u306e\u5c5e\u6027\u3078\u306e\u5909\u66f4\u306f\u305f\u3060\u3061\u306b\u6709\u52b9\u306b\u306a\u308a\u307e\u3059\u304c\u3001\u5bfe\u8c61\u3068\u306a\u308b\u306e\u306f\u3001\u95a2\u9023\u4ed8\u3051\u3089\u308c\u305f\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u63a5\u7d9a\u306e\u30c8\u30e9\u30b9\u30c8\u30de\u30cd\u30fc\u30b8\u30e3\u30fc\u30d7\u30ed\u30d0\u30a4\u30c0\u3078\u306e\u4ee5\u964d\u306e\u30a2\u30af\u30bb\u30b9\u8a66\u884c\u3060\u3051\u3067\u3059 |
| | | ###SEVERE_ERR_LDAP_CONNHANDLER_INVALID_TRUSTMANAGER_DN_394=Configuration \ |
| | | ### attribute ds-cfg-trust-manager-provider of configuration entry %s has an \ |
| | | ### invalid value %s which does not reference an enabled trust manager provider |
| | | ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_TRUSTMANAGER_DN_395=An error \ |
| | | ### occurred while processing the ds-cfg-trust-manager-provider attribute in \ |
| | | ### configuration entry %s, which is used to specify the trust manager provider \ |
| | | ### for use with the LDAP connection handler: %s |
| | | SEVERE_ERR_LDAP_CONNHANDLER_INVALID_TRUSTMANAGER_DN_394=Configuration attribute ds-cfg-trust-manager-provider of configuration entry %s has an invalid value %s which does not reference an enabled trust manager provider |
| | | SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_TRUSTMANAGER_DN_395=An error occurred while processing the ds-cfg-trust-manager-provider attribute in configuration entry %s, which is used to specify the trust manager provider for use with the LDAP connection handler: %s |
| | | INFO_LDAP_CONNHANDLER_NEW_KEYMANAGER_DN_396=\u69cb\u6210\u30a8\u30f3\u30c8\u30ea %2$s \u3067\u3001ds-cfg-key-manager-provider \u5c5e\u6027\u306e\u5024\u304c %1$s \u306b\u66f4\u65b0\u3055\u308c\u307e\u3057\u305f |
| | | INFO_LDAP_CONNHANDLER_NEW_TRUSTMANAGER_DN_397=\u69cb\u6210\u30a8\u30f3\u30c8\u30ea %2$s \u3067\u3001ds-cfg-trust-manager-provider \u5c5e\u6027\u306e\u5024\u304c %1$s \u306b\u66f4\u65b0\u3055\u308c\u307e\u3057\u305f |
| | | INFO_JMX_CONNHANDLER_DESCRIPTION_KEYMANAGER_DN_398=SSL \u30d9\u30fc\u30b9\u306e\u63a5\u7d9a\u3092\u53d7\u3051\u4ed8\u3051\u308b\u3068\u304d\u3001\u307e\u305f\u306f StartTLS \u30cd\u30b4\u30b7\u30a8\u30fc\u30b7\u30e7\u30f3\u3092\u5b9f\u884c\u3059\u308b\u3068\u304d\u306b\u63a5\u7d9a\u30cf\u30f3\u30c9\u30e9\u3067\u4f7f\u7528\u3059\u3079\u304d\u9375\u30de\u30cd\u30fc\u30b8\u30e3\u30fc\u30d7\u30ed\u30d0\u30a4\u30c0\u306e DN\u3002 \u3053\u306e\u8a2d\u5b9a\u5c5e\u6027\u3078\u306e\u5909\u66f4\u306f\u305f\u3060\u3061\u306b\u6709\u52b9\u306b\u306a\u308a\u307e\u3059 |
| | | ###SEVERE_ERR_JMX_CONNHANDLER_INVALID_KEYMANAGER_DN_399=An error occurred while \ |
| | | ### processing the ds-cfg-key-manager-provider attribute in configuration \ |
| | | ### entry %s, because the provided key manager DN %s does not refer to an enabled \ |
| | | ### key manager provider |
| | | ###SEVERE_ERR_JMX_CONNHANDLER_CANNOT_DETERMINE_KEYMANAGER_DN_400=An unexpected \ |
| | | ### error occurred while processing the ds-cfg-key-manager-provider attribute \ |
| | | ### in configuration entry %s, which is used to specify the DN of the key manager \ |
| | | ### provider to use for accepting SSL/TLS connections: %s |
| | | SEVERE_ERR_JMX_CONNHANDLER_INVALID_KEYMANAGER_DN_399=An error occurred while processing the ds-cfg-key-manager-provider attribute in configuration entry %s, because the provided key manager DN %s does not refer to an enabled key manager provider |
| | | SEVERE_ERR_JMX_CONNHANDLER_CANNOT_DETERMINE_KEYMANAGER_DN_400=An unexpected error occurred while processing the ds-cfg-key-manager-provider attribute in configuration entry %s, which is used to specify the DN of the key manager provider to use for accepting SSL/TLS connections: %s |
| | | MILD_ERR_LDAP_CONNHANDLER_CANNOT_SET_SECURITY_PROVIDER_401=\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u63a5\u7d9a\u306e\u63a5\u7d9a\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u30fc\u30d7\u30ed\u30d0\u30a4\u30c0\u3092\u69cb\u6210\u4e2d\u306b\u30a8\u30e9\u30fc\u304c\u767a\u751f\u3057\u307e\u3057\u305f: %s |
| | | ###SEVERE_ERR_LDAP_CONNHANDLER_NO_KEYMANAGER_DN_402=The LDAP connection handler \ |
| | | ### defined in configuration entry %s is configured to use either SSL or \ |
| | | ### StartTLS, but does not specify which key manager provider should be used |
| | | ###SEVERE_ERR_LDAP_CONNHANDLER_NO_TRUSTMANAGER_DN_403=The LDAP connection \ |
| | | ### handler defined in configuration entry %s is configured to use either SSL or \ |
| | | ### StartTLS, but does not specify which trust manager provider should be used |
| | | SEVERE_ERR_LDAP_CONNHANDLER_NO_KEYMANAGER_DN_402=The LDAP connection handler defined in configuration entry %s is configured to use either SSL or StartTLS, but does not specify which key manager provider should be used |
| | | SEVERE_ERR_LDAP_CONNHANDLER_NO_TRUSTMANAGER_DN_403=The LDAP connection handler defined in configuration entry %s is configured to use either SSL or StartTLS, but does not specify which trust manager provider should be used |
| | | INFO_LDAPS_CONNHANDLER_DESCRIPTION_ENABLE_404=LDAPS \u63a5\u7d9a\u30cf\u30f3\u30c9\u30e9\u3092\u6709\u52b9\u306b\u3059\u308b\u304b\u3069\u3046\u304b\u3092\u6307\u5b9a\u3057\u307e\u3059 |
| | | MILD_ERR_LDAP_FILTER_NOT_EXACTLY_ONE_405=\u6307\u5b9a\u3055\u308c\u305f\u691c\u7d22\u30d5\u30a3\u30eb\u30bf "%s" \u3092\u5fa9\u53f7\u5316\u3067\u304d\u307e\u305b\u3093\u3067\u3057\u305f\u3002\u4f4d\u7f6e %d \u3068 %d \u306e\u9593\u306e NOT \u30d5\u30a3\u30eb\u30bf\u306b\u30d5\u30a3\u30eb\u30bf\u30b3\u30f3\u30dd\u30fc\u30cd\u30f3\u30c8\u304c\u6b63\u78ba\u306b 1 \u3064\u542b\u307e\u308c\u3066\u3044\u307e\u305b\u3093\u3067\u3057\u305f |
| | | INFO_SORTREQ_CONTROL_NO_VALUE_406=\u6307\u5b9a\u3055\u308c\u305f\u5236\u5fa1\u3092\u30b5\u30fc\u30d0\u30fc\u5074\u30bd\u30fc\u30c8\u8981\u6c42\u5236\u5fa1\u3068\u3057\u3066\u5fa9\u53f7\u5316\u3067\u304d\u307e\u305b\u3093\u3002\u5236\u5fa1\u5024\u304c\u542b\u307e\u308c\u3066\u3044\u307e\u305b\u3093 |
| | |
| | | MILD_ERR_LDAP_FILTER_INVALID_CHAR_IN_ATTR_TYPE_429=\u6307\u5b9a\u3055\u308c\u305f\u691c\u7d22\u30d5\u30a3\u30eb\u30bf\u306e\u4f4d\u7f6e %3$d \u306b\u7121\u52b9\u306a\u6587\u5b57 '%2$s' \u304c\u3042\u308b\u7121\u52b9\u306a\u5c5e\u6027\u578b '%1$s' \u304c\u542b\u307e\u308c\u3066\u3044\u307e\u3059 |
| | | MILD_ERR_LDAP_FILTER_EXTENSIBLE_MATCH_NO_AD_OR_MR_430=\u6307\u5b9a\u3055\u308c\u305f\u691c\u7d22\u30d5\u30a3\u30eb\u30bf "%s" \u3092\u5fa9\u53f7\u5316\u3067\u304d\u307e\u305b\u3093\u3067\u3057\u305f\u3002\u4f4d\u7f6e %d \u3067\u59cb\u307e\u308b\u62e1\u5f35\u4e00\u81f4\u30b3\u30f3\u30dd\u30fc\u30cd\u30f3\u30c8\u306b\u5c5e\u6027\u306e\u8aac\u660e\u307e\u305f\u306f\u30de\u30c3\u30c1\u30f3\u30b0\u30eb\u30fc\u30eb ID \u304c\u542b\u307e\u308c\u3066\u3044\u307e\u305b\u3093\u3002 \u3053\u308c\u3089\u306e\u5c11\u306a\u304f\u3068\u3082 1 \u3064\u3092\u6307\u5b9a\u3059\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059 |
| | | MILD_ERR_LDAPV2_CONTROLS_NOT_ALLOWED_431=LDAPv2 \u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u3067\u8981\u6c42\u5236\u5fa1\u3092\u4f7f\u7528\u3059\u308b\u3053\u3068\u306f\u8a31\u53ef\u3055\u308c\u307e\u305b\u3093 |
| | | ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_BIND_432=The LDAP connection handler \ |
| | | ### defined in configuration entry %s was unable to bind to %s:%d: %s |
| | | ###SEVERE_ERR_JMX_CONNHANDLER_CANNOT_BIND_433=The JMX connection handler defined \ |
| | | ### in configuration entry %s was unable to bind to port %d: %s |
| | | SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_BIND_432=The LDAP connection handler defined in configuration entry %s was unable to bind to %s:%d: %s |
| | | SEVERE_ERR_JMX_CONNHANDLER_CANNOT_BIND_433=The JMX connection handler defined in configuration entry %s was unable to bind to port %d: %s |
| | | MILD_ERR_JMX_ADD_INSUFFICIENT_PRIVILEGES_434=JMX \u3092\u4ecb\u3057\u3066\u8ffd\u52a0\u64cd\u4f5c\u3092\u5b9f\u884c\u3059\u308b\u305f\u3081\u306e\u5341\u5206\u306a\u6a29\u9650\u304c\u3042\u308a\u307e\u305b\u3093 |
| | | MILD_ERR_JMX_DELETE_INSUFFICIENT_PRIVILEGES_435=JMX \u3092\u4ecb\u3057\u3066\u524a\u9664\u64cd\u4f5c\u3092\u5b9f\u884c\u3059\u308b\u305f\u3081\u306e\u5341\u5206\u306a\u6a29\u9650\u304c\u3042\u308a\u307e\u305b\u3093 |
| | | MILD_ERR_JMX_MODIFY_INSUFFICIENT_PRIVILEGES_436=JMX \u3092\u4ecb\u3057\u3066\u5909\u66f4\u64cd\u4f5c\u3092\u5b9f\u884c\u3059\u308b\u305f\u3081\u306e\u5341\u5206\u306a\u6a29\u9650\u304c\u3042\u308a\u307e\u305b\u3093 |
| | |
| | | MILD_ERR_INTERNALOS_INVALID_REQUEST_442=\u6307\u5b9a\u3055\u308c\u305f LDAP \u30e1\u30c3\u30bb\u30fc\u30b8\u306b\u3001\u8981\u6c42\u306e\u7121\u52b9\u306a\u64cd\u4f5c\u30bf\u30a4\u30d7 (%s) \u304c\u3042\u308a\u307e\u3057\u305f |
| | | MILD_ERR_INTERNALOS_SASL_BIND_NOT_SUPPORTED_443=\u5185\u90e8 LDAP \u30bd\u30b1\u30c3\u30c8\u3092\u4ecb\u3057\u305f SASL \u30d0\u30a4\u30f3\u30c9\u64cd\u4f5c\u306f\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u307e\u305b\u3093 |
| | | MILD_ERR_INTERNALOS_STARTTLS_NOT_SUPPORTED_444=\u5185\u90e8 LDAP \u30bd\u30b1\u30c3\u30c8\u3092\u4ecb\u3057\u305f StartTLS \u64cd\u4f5c\u306f\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u307e\u305b\u3093 |
| | | ###SEVERE_WARN_LDIF_CONNHANDLER_LDIF_DIRECTORY_NOT_DIRECTORY_445=The value %s \ |
| | | ### specified as the LDIF directory path for the LDIF connection handler defined \ |
| | | ### in configuration entry %s exists but is not a directory. The specified path \ |
| | | ### must be a directory. The LDIF connection handler will start, but will not \ |
| | | ### be able to proces any changes until this path is changed to a directory |
| | | SEVERE_WARN_LDIF_CONNHANDLER_LDIF_DIRECTORY_NOT_DIRECTORY_445=The value %s specified as the LDIF directory path for the LDIF connection handler defined in configuration entry %s exists but is not a directory. The specified path must be a directory. The LDIF connection handler will start, but will not be able to proces any changes until this path is changed to a directory |
| | | MILD_WARN_LDIF_CONNHANDLER_LDIF_DIRECTORY_MISSING_446=\u69cb\u6210\u30a8\u30f3\u30c8\u30ea %s \u3067\u5b9a\u7fa9\u3055\u308c\u305f LDIF \u63a5\u7d9a\u30cf\u30f3\u30c9\u30e9\u304c\u53c2\u7167\u3059\u308b\u30c7\u30a3\u30ec\u30af\u30c8\u30ea %s \u304c\u5b58\u5728\u3057\u307e\u305b\u3093\u3002 LDIF \u63a5\u7d9a\u30cf\u30f3\u30c9\u30e9\u306f\u8d77\u52d5\u3057\u307e\u3059\u304c\u3001\u3053\u306e\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u304c\u4f5c\u6210\u3055\u308c\u308b\u307e\u3067\u3001\u5909\u66f4\u3092\u51e6\u7406\u3059\u308b\u3053\u3068\u306f\u3067\u304d\u307e\u305b\u3093 |
| | | MILD_ERR_LDIF_CONNHANDLER_CANNOT_READ_CHANGE_RECORD_NONFATAL_447=LDIF \u30d5\u30a1\u30a4\u30eb\u304b\u3089\u5909\u66f4\u30ec\u30b3\u30fc\u30c9\u3092\u8aad\u307f\u8fbc\u307f\u4e2d\u306b\u30a8\u30e9\u30fc\u304c\u767a\u751f\u3057\u307e\u3057\u305f: %s\u3002\u3053\u306e\u5909\u66f4\u306f\u30b9\u30ad\u30c3\u30d7\u3055\u308c\u307e\u3059\u304c\u3001LDIF \u30d5\u30a1\u30a4\u30eb\u306e\u51e6\u7406\u306f\u7d9a\u884c\u3057\u307e\u3059 |
| | | MILD_ERR_LDIF_CONNHANDLER_CANNOT_READ_CHANGE_RECORD_FATAL_448=LDIF \u30d5\u30a1\u30a4\u30eb\u304b\u3089\u5909\u66f4\u30ec\u30b3\u30fc\u30c9\u3092\u8aad\u307f\u8fbc\u307f\u4e2d\u306b\u30a8\u30e9\u30fc\u304c\u767a\u751f\u3057\u307e\u3057\u305f: %s\u3002\u3053\u306e LDIF \u30d5\u30a1\u30a4\u30eb\u306e\u51e6\u7406\u306f\u3053\u308c\u4ee5\u4e0a\u5b9f\u884c\u3067\u304d\u307e\u305b\u3093 |
| | |
| | | INFO_LDIF_CONNHANDLER_ERROR_MESSAGE_451=\u8ffd\u52a0\u60c5\u5831: %s |
| | | INFO_LDIF_CONNHANDLER_MATCHED_DN_452=\u4e00\u81f4\u3057\u305f DN: %s |
| | | INFO_LDIF_CONNHANDLER_REFERRAL_URL_453=\u30ea\u30d5\u30a7\u30e9\u30eb URL: %s |
| | | ###SEVERE_ERR_LDIF_CONNHANDLER_IO_ERROR_454=An I/O error occurred while the LDIF \ |
| | | ### connection handler was processing LDIF file %s: %s |
| | | ###SEVERE_ERR_LDIF_CONNHANDLER_CANNOT_RENAME_455=An error occurred while the \ |
| | | ### LDIF connection handler was attempting to rename partially-processed file \ |
| | | ### from %s to %s: %s |
| | | ###SEVERE_ERR_LDIF_CONNHANDLER_CANNOT_DELETE_456=An error occurred while the \ |
| | | ### LDIF connection handler was attempting to delete processed file %s: %s |
| | | ###SEVERE_ERR_CONNHANDLER_ADDRESS_INUSE_457=Address already in use |
| | | SEVERE_ERR_LDIF_CONNHANDLER_IO_ERROR_454=An I/O error occurred while the LDIF connection handler was processing LDIF file %s: %s |
| | | SEVERE_ERR_LDIF_CONNHANDLER_CANNOT_RENAME_455=An error occurred while the LDIF connection handler was attempting to rename partially-processed file from %s to %s: %s |
| | | SEVERE_ERR_LDIF_CONNHANDLER_CANNOT_DELETE_456=An error occurred while the LDIF connection handler was attempting to delete processed file %s: %s |
| | | SEVERE_ERR_CONNHANDLER_ADDRESS_INUSE_457=Address already in use |
| | | INFO_SNMP_CONNHANDLER_DESCRIPTION_LISTEN_PORT_1458=\u3053\u306e\u63a5\u7d9a\u30cf\u30f3\u30c9\u30e9\u304c SNMP \u8981\u6c42\u3092\u53d7\u3051\u4ed8\u3051\u308b SNMP \u30dd\u30fc\u30c8\u3002 \u3053\u306e\u8a2d\u5b9a\u5c5e\u6027\u3078\u306e\u5909\u66f4\u306f\u3001\u63a5\u7d9a\u30cf\u30f3\u30c9\u30e9\u3092\u7121\u52b9\u306b\u3057\u3066\u518d\u5ea6\u6709\u52b9\u306b\u3059\u308b\u304b\u3001\u307e\u305f\u306f\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u30b5\u30fc\u30d0\u30fc\u3092\u518d\u8d77\u52d5\u3059\u308b\u307e\u3067\u6709\u52b9\u306b\u306a\u308a\u307e\u305b\u3093 |
| | | ###SEVERE_ERR_SNMP_CONNHANDLER_NO_LISTEN_PORT_1459=No listen port was defined \ |
| | | ### using configuration ds-cfg-listen-port in configuration entry %s. This is a \ |
| | | ### required attribute |
| | | ###SEVERE_ERR_SNMP_CONNHANDLER_CANNOT_DETERMINE_LISTEN_PORT_1460=An unexpected \ |
| | | ### error occurred while processing the ds-cfg-listen-port attribute in \ |
| | | ### configuration entry %s, which is used to specify the port on which to listen \ |
| | | ### for client connections: %s |
| | | ###SEVERE_ERR_SNMP_CONNHANDLER_CANNOT_BE_STARTED_1461=An unexpected \ |
| | | ### error occurred when this connection handler started |
| | | ###SEVERE_ERR_SNMP_CONNHANDLER_NO_CONFIGURATION_1462=No Configuration was defined \ |
| | | ### for this connection handler. The configuration parameters ds-cfg-listen-port \ |
| | | ### and ds-cfg-trap-port are required by the connection handler to start |
| | | ###SEVERE_ERR_SNMP_CONNHANDLER_TRAPS_DESTINATION_1463=Traps Destination %s is \ |
| | | ### an unknown host. Traps will not be sent to this destination |
| | | ###SEVERE_ERR_SNMP_CONNHANDLER_NO_OPENDMK_JARFILES_1464=You do not have the \ |
| | | ### appropriate OpenDMK jar files to enable the SNMP Connection Handler. \ |
| | | ### Please go under http://opendmk.dev.java.net and set the \ |
| | | ### opendmk-jarfile configuration parameter to set the full path \ |
| | | ### of the required jdmkrt.jar file. The SNMP connection Handler didn't started |
| | | ###SEVERE_ERR_SNMP_CONNHANDLER_BAD_CONFIGURATION_1465=Cannot initialize the \ |
| | | ### SNMP Connection Handler. Please check the configuration attributes |
| | | ###SEVERE_ERR_SNMP_CONNHANDLER_NO_VALID_TRAP_DESTINATIONS_1466=No valid trap \ |
| | | ### destinations has been found. No trap will be sent |
| | | ###SEVERE_ERR_ASN1_READ_ERROR_1500=An error occured while accessing the \ |
| | | ### underlying data source: %s |
| | | ###SEVERE_ERR_ASN1_EOF_ERROR_1501=An unexpected end of file reached while trying \ |
| | | ### to read %d bytes from the underlying data source |
| | | ###SEVERE_ERR_ASN1_INVALID_STATE_1502=Invalid reader state: %d |
| | | ###SEVERE_ERR_SUBTREE_DELETE_INVALID_CONTROL_VALUE_1503=Cannot decode the provided \ |
| | | ### subtree delete control because it contains a value |
| | | SEVERE_ERR_SNMP_CONNHANDLER_NO_LISTEN_PORT_1459=No listen port was defined using configuration ds-cfg-listen-port in configuration entry %s. This is a required attribute |
| | | SEVERE_ERR_SNMP_CONNHANDLER_CANNOT_DETERMINE_LISTEN_PORT_1460=An unexpected error occurred while processing the ds-cfg-listen-port attribute in configuration entry %s, which is used to specify the port on which to listen for client connections: %s |
| | | SEVERE_ERR_SNMP_CONNHANDLER_CANNOT_BE_STARTED_1461=An unexpected error occurred when this connection handler started |
| | | SEVERE_ERR_SNMP_CONNHANDLER_NO_CONFIGURATION_1462=No Configuration was defined for this connection handler. The configuration parameters ds-cfg-listen-port and ds-cfg-trap-port are required by the connection handler to start |
| | | SEVERE_ERR_SNMP_CONNHANDLER_TRAPS_DESTINATION_1463=Traps Destination %s is an unknown host. Traps will not be sent to this destination |
| | | SEVERE_ERR_SNMP_CONNHANDLER_NO_OPENDMK_JARFILES_1464=You do not have the appropriate OpenDMK jar files to enable the SNMP Connection Handler. Please go under http://opendmk.dev.java.net and set the opendmk-jarfile configuration parameter to set the full path of the required jdmkrt.jar file. The SNMP connection Handler didn't started |
| | | SEVERE_ERR_SNMP_CONNHANDLER_BAD_CONFIGURATION_1465=Cannot initialize the SNMP Connection Handler. Please check the configuration attributes |
| | | SEVERE_ERR_SNMP_CONNHANDLER_NO_VALID_TRAP_DESTINATIONS_1466=No valid trap destinations has been found. No trap will be sent |
| | | SEVERE_ERR_ASN1_READ_ERROR_1500=An error occured while accessing the underlying data source: %s |
| | | SEVERE_ERR_ASN1_EOF_ERROR_1501=An unexpected end of file reached while trying to read %d bytes from the underlying data source |
| | | SEVERE_ERR_ASN1_INVALID_STATE_1502=Invalid reader state: %d |
| | | SEVERE_ERR_SUBTREE_DELETE_INVALID_CONTROL_VALUE_1503=Cannot decode the provided subtree delete control because it contains a value |
| | | SEVERE_ERR_CONNHANDLER_SSL_CANNOT_INITIALIZE_1504=LDAP \u63a5\u7d9a\u30cf\u30f3\u30c9\u30e9\u3067\u4f7f\u7528\u3059\u308b SSL \u30b3\u30f3\u30c6\u30ad\u30b9\u30c8\u306e\u521d\u671f\u5316\u4e2d\u306b\u30a8\u30e9\u30fc\u304c\u767a\u751f\u3057\u307e\u3057\u305f: %s |
| | | MILD_ERR_LDAP_UNSUPPORTED_PROTOCOL_VERSION_1505=Directory Server \u306f LDAP \u30d7\u30ed\u30c8\u30b3\u30eb\u30d0\u30fc\u30b8\u30e7\u30f3 %d \u3092\u30b5\u30dd\u30fc\u30c8\u3057\u3066\u3044\u307e\u305b\u3093\u3002\u3053\u306e\u63a5\u7d9a\u3092\u7d42\u4e86\u3057\u307e\u3059 |
| | | ###SEVERE_ERR_SNMP_CONNHANDLER_OPENDMK_JARFILES_DOES_NOT_EXIST_1506=The specified \ |
| | | ### OpenDMK jar file '%s' could not be found. Verify that the value set in the \ |
| | | ### opendmk-jarfile configuration parameter of the SNMP connection handler is the \ |
| | | ### valid path to the jdmkrt.jar file and that the file is accessible |
| | | ###SEVERE_ERR_SNMP_CONNHANDLER_OPENDMK_JARFILES_NOT_OPERATIONAL_1507=The required \ |
| | | ### classes could not be loaded using jar file '%s'. Verify that the jar file \ |
| | | ### is not corrupted |
| | | SEVERE_ERR_SNMP_CONNHANDLER_OPENDMK_JARFILES_DOES_NOT_EXIST_1506=The specified OpenDMK jar file '%s' could not be found. Verify that the value set in the opendmk-jarfile configuration parameter of the SNMP connection handler is the valid path to the jdmkrt.jar file and that the file is accessible |
| | | SEVERE_ERR_SNMP_CONNHANDLER_OPENDMK_JARFILES_NOT_OPERATIONAL_1507=The required classes could not be loaded using jar file '%s'. Verify that the jar file is not corrupted |
| | | MILD_ERR_CANNOT_DECODE_CONTROL_VALUE_1508=Cannot decode the provided control %s because an error occurred while attempting to decode the control value: %s |
| | | |