| Name | Severity | Alarm Severity | OID | Summary | Description |
| access-control-change | INFO | 1.3.6.1.4.1.30221.2.10.3.73 | Access Control Change | Indicates that a change has been made to the set of access controls defined in the Directory Server | |
| access-control-disabled | WARNING | 1.3.6.1.4.1.30221.2.10.3.1 | Access Control Evaluation Disabled | Indicates that access control evaluation has been disabled | |
| access-control-enabled | INFO | 1.3.6.1.4.1.30221.2.10.3.2 | Access Control Evaluation Enabled | Indicates that access control evaluation has been enabled | |
| access-control-parse-failure | ERROR | 1.3.6.1.4.1.30221.2.10.3.3 | Error Parsing Access Control Rule | Indicates that an error occurred while attempting to parse an access control rule | |
| access-log-criteria-matched | INFO | 1.3.6.1.4.1.30221.2.10.3.64 | Admin Alert Access Log Criteria Matched | Indicates that the server has processed an operation which matched the criteria for the admin alert access log publisher | |
| alarm-cleared | INFO | 1.3.6.1.4.1.30221.2.10.3.120 | [standard alert summary or gauge name] | Indicates that an alarm condition previously observed changed in severity | |
| alarm-critical | ERROR | 1.3.6.1.4.1.30221.2.10.3.124 | [standard alert summary or gauge name] | Indicates that an alarm condition was observed at critical severity | |
| alarm-major | WARNING | 1.3.6.1.4.1.30221.2.10.3.123 | [standard alert summary or gauge name] | Indicates that an alarm condition was observed at major severity | |
| alarm-minor | WARNING | 1.3.6.1.4.1.30221.2.10.3.122 | [standard alert summary or gauge name] | Indicates that an alarm condition was observed at minor severity | |
| alarm-warning | WARNING | 1.3.6.1.4.1.30221.2.10.3.121 | [standard alert summary or gauge name] | Indicates that an alarm condition was observed at warning severity | |
| backend-disabled | WARNING | WARNING | 1.3.6.1.4.1.30221.2.10.3.94 | Backend Disabled | Indicates that a backend is disabled |
| backend-initialization-failed | ERROR | 1.3.6.1.4.1.30221.2.10.3.78 | Backend Initialization Failed | Indicates that the attempt to initialize a backend failed | |
| backup-failed | ERROR | 1.3.6.1.4.1.30221.2.10.3.100 | Error Performing Backup | Indicates that an error occurred while trying to perform a backup | |
| cannot-acquire-shared-backend-lock | ERROR | 1.3.6.1.4.1.30221.2.10.3.4 | Error Acquiring Shared Backend Lock | Indicates that an error occurred while attempting to acquire a shared backend lock | |
| cannot-copy-schema-files | ERROR | 1.3.6.1.4.1.30221.2.10.3.5 | Error Copying Schema Files During Update | Indicates that an error occurred while attempting to copy schema files during a schema update | |
| cannot-decode-entry | ERROR | 1.3.6.1.4.1.30221.2.10.3.6 | Error Decoding Backend Entry | Indicates that an error occurred while attempting to decode an entry stored in a backend | |
| cannot-find-recurring-task | ERROR | 1.3.6.1.4.1.30221.2.10.3.7 | Recurring Task Definition Not Found | Indicates that the definition for a recurring task could not be found | |
| cannot-register-backend | ERROR | 1.3.6.1.4.1.30221.2.10.3.8 | Error Registering Backend | Indicates that an error occurred while trying to register a backend | |
| cannot-release-shared-backend-lock | ERROR | 1.3.6.1.4.1.30221.2.10.3.9 | Error Releasing Shared Backend Lock | Indicates that an error occurred while trying to release a shared backend lock | |
| cannot-rename-current-task-file | ERROR | 1.3.6.1.4.1.30221.2.10.3.10 | Error Renaming Current Task Backing File | Indicates that an error occurred while trying rename the current task backing file | |
| cannot-rename-new-task-file | ERROR | 1.3.6.1.4.1.30221.2.10.3.11 | Error Renaming New Task Backing File | Indicates that an error occurred while trying rename the new task backing file | |
| cannot-restore-backup | ERROR | 1.3.6.1.4.1.30221.2.10.3.12 | Error Restoring Backup | Indicates that an error occurred while trying to restore a backup | |
| cannot-schedule-recurring-task-iteration | ERROR | 1.3.6.1.4.1.30221.2.10.3.13 | Error Scheduling Recurring Task Iteration | Indicates that an error occurred while trying to schedule a recurring task iteration | |
| cannot-write-configuration | ERROR | 1.3.6.1.4.1.30221.2.10.3.14 | Error Writing Updated Server Configuration | Indicates that an error occurred while trying to write the updated server configuration | |
| cannot-write-new-schema-files | ERROR | 1.3.6.1.4.1.30221.2.10.3.15 | Error Writing Updated Schema Files | Indicates that an error occurred while trying to write updated schema files | |
| cannot-write-server-state-file | ERROR | 1.3.6.1.4.1.30221.2.10.3.48 | Error Writing Server State File | Indicates that an error occurred while attempting to write the server state file | |
| cannot-write-task-backing-file | ERROR | 1.3.6.1.4.1.30221.2.10.3.16 | Error Writing Task Backing File | Indicates that an error occurred while trying to write the task backing file | |
| config-change | INFO | 1.3.6.1.4.1.30221.2.10.3.70 | Configuration Change | Indicates that a configuration change has been made in the Directory Server | |
| continuous-garbage-collection-detected | WARNING | WARNING | 1.3.6.1.4.1.30221.2.10.3.149 | Continuous Garbage Collection Detected | The JVM configuration and server memory requirements have caused JVM garbage collection to run continuously |
| crypto-manager-error | ERROR | MAJOR | 1.3.6.1.4.1.30221.2.10.3.139 | CryptoManager error | CryptoManager encountered an unexpected error while synchronizing settings between the topology registry and the trust store backend |
| deadlock-detected | ERROR | MAJOR | 1.3.6.1.4.1.30221.2.10.3.49 | Deadlock Detected | Indicates that a deadlock has been detected in the JVM in which the Directory Server is running |
| debug-logging-enabled | WARNING | WARNING | 1.3.6.1.4.1.30221.2.10.3.140 | A Debug Log Publisher is enabled which could cause performance issues if it is configured to log large volumes of data | Indicates that Debug Logging is enabled |
| delegated-admin-configuration-errors | ERROR | MAJOR | 1.3.6.1.4.1.30221.2.10.3.164 | Delegated Admin Configuration Errors | Indicates that Delegated Admin is not configured properly |
| duplicate-alerts-suppressed | ERROR | 1.3.6.1.4.1.30221.2.10.3.17 | Duplicate Alert Notifications Suppressed | Indicates that duplicate alert notifications have been suppressed | |
| duplicate-error-alerts-suppressed | ERROR | 1.3.6.1.4.1.30221.2.10.3.91 | Duplicate Error Alert Notifications Suppressed | Indicates that duplicate error alert notifications have been suppressed | |
| duplicate-fatal-alerts-suppressed | FATAL | 1.3.6.1.4.1.30221.2.10.3.90 | Duplicate Fatal Alert Notifications Suppressed | Indicates that duplicate fatal alert notifications have been suppressed | |
| duplicate-info-alerts-suppressed | INFO | 1.3.6.1.4.1.30221.2.10.3.93 | Duplicate Info Alert Notifications Suppressed | Indicates that duplicate info alert notifications have been suppressed | |
| duplicate-warning-alerts-suppressed | WARNING | 1.3.6.1.4.1.30221.2.10.3.92 | Duplicate Warning Alert Notifications Suppressed | Indicates that duplicate warning alert notifications have been suppressed | |
| entering-lockdown-mode | WARNING | WARNING | 1.3.6.1.4.1.30221.2.10.3.18 | Server Entering Lockdown Mode | Indicates that the server is entering lockdown mode, in which case it will only allow operations from users with the lockdown-mode privilege |
| entry-references-removed-attribute-type | ERROR | 1.3.6.1.4.1.30221.2.10.3.163 | Entry References Removed Attribute Type | Indicates that an entry retrieved from a backend references an attribute type that has been removed from the server schema | |
| exec-task-launching-command | INFO | 1.3.6.1.4.1.30221.2.10.3.154 | Indicates that the exec task is being used to run a specified command | Exec Task Launching Command | |
| exploded-index-background-delete-cleanup-failed | ERROR | 1.3.6.1.4.1.30221.2.10.3.117 | Exploded Index Background Delete Cleanup Failed | Indicates that an error occurred while attempting to clean up after a background delete of an exploded index key | |
| exploded-index-background-delete-failed | ERROR | 1.3.6.1.4.1.30221.2.10.3.116 | Exploded Index Background Delete Failed | Indicates that an error occurred while attempting to perform a background delete of an exploded index key that is no longer needed | |
| external-config-file-edit-handled | WARNING | 1.3.6.1.4.1.30221.2.10.3.19 | Handled External Configuration File Edit Detected | Indicates that the server has detected an external edit to the configuration file with the server online, but that it was able to copy the modifications into a separate file but without applying them | |
| external-config-file-edit-lost | ERROR | 1.3.6.1.4.1.30221.2.10.3.20 | Lost External Configuration File Edit Detected | Indicates that the server has detected an external edit to the configuration file with the server online and was unable to copy the modifications into a separate file | |
| external-server-initialization-failed | ERROR | MAJOR | 1.3.6.1.4.1.30221.2.10.3.79 | External Server Initialization Failed | Indicates that the attempt to initialize an external server failed |
| failed-to-apply-mirrored-configuration | ERROR | MAJOR | 1.3.6.1.4.1.30221.2.10.3.137 | Failed to Apply Mirrored Configuration | Indicates that although mirrored configuration was synchronized successfully from the master server, there were errors when applying it to this server. A server restart is recommended in this case |
| file-retention-task-delete-failure | ERROR | 1.3.6.1.4.1.30221.2.10.3.155 | Indicates that a file retention task was unable to delete a file that matched the filename pattern and was outside of the retention criteria | File Retention Task Delete Failure | |
| force-gc-complete | INFO | 1.3.6.1.4.1.30221.2.10.3.69 | Completed Forced Garbage Collection | Indicates that the Directory Server has completed a synchronous garbage collection | |
| force-gc-starting | INFO | 1.3.6.1.4.1.30221.2.10.3.68 | Starting Forced Garbage Collection | Indicates that the Directory Server is going to invoke a synchronous garbage collection | |
| http-connection-handler-duplicate-context-path | WARNING | WARNING | 1.3.6.1.4.1.30221.2.10.3.156 | Duplicate HTTP servlet context paths | More than one HTTP servlet or web application extension is registered to handle the same context path. The extension that handles requests for this context path is indeterminate |
| http-connection-handler-duplicate-servlet-extension | ERROR | MAJOR | 1.3.6.1.4.1.30221.2.10.3.157 | Duplicate HTTP servlet extensions | An HTTP connection handler is configured with more than one HTTP servlet extension of a type that may only be configured once per HTTP connection handler. The connection handler configuration must be corrected, or undefined behavior may result |
| index-corrupt | ERROR | MAJOR | 1.3.6.1.4.1.30221.2.10.3.110 | Index Key Corrupt | Indicates that an index has been determined to have corrupt keys and needs to be rebuilt in order for those keys to yield correct results. The index will continue to function correctly for other keys |
| index-degraded | WARNING | WARNING | 1.3.6.1.4.1.30221.2.10.3.74 | Index Degraded | Indicates that a backend is operating with a degraded index that needs to be rebuilt before that index may be used |
| index-rebuild-completed | INFO | 1.3.6.1.4.1.30221.2.10.3.76 | Index Rebuild Completed | Indicates that an index rebuild process has completed | |
| index-rebuild-in-progress | INFO | 1.3.6.1.4.1.30221.2.10.3.75 | Index Rebuild in Progress | Indicates that an index is in the process of being rebuilt | |
| insecure-access-token-validator-enabled | WARNING | WARNING | 1.3.6.1.4.1.30221.2.10.3.158 | Insecure access token validator enabled | An insecure access token validator is enabled. This access token validator does not validate the authenticity of bearer tokens and should only be used in test or demonstration deployments |
| invalid-privilege | WARNING | 1.3.6.1.4.1.30221.2.10.3.21 | Invalid Privilege | Indicates that a user has been configured with an invalid privilege | |
| je-background-sync-failed | ERROR | 1.3.6.1.4.1.30221.2.10.3.89 | Berkeley DB JE Background Sync Failure | Indicates that an error occurred while attempting to perform a synchronous write in a Berkeley DB JE database environment | |
| je-cleaner-disabled | WARNING | WARNING | 1.3.6.1.4.1.30221.2.10.3.130 | Berkeley DB JE Cleaner Disabled | Indicates that the Berkeley DB JE cleaner has been disabled in a local DB backend and that the on-disk size of the database will be allowed to increase without bound until cleaning is re-enabled |
| je-daemon-thread-exception | ERROR | 1.3.6.1.4.1.30221.2.10.3.87 | Berkeley DB JE Daemon Thread Exception | Indicates that an exception was encountered during processing within a daemon thread used by a Berkeley DB JE database environment | |
| je-environment-not-closed-cleanly | WARNING | 1.3.6.1.4.1.30221.2.10.3.138 | JE Environment Not Closed Cleanly | Indicates that a Berkeley DB JE environment may not have been closed cleanly when it was last open, and that a potentially-expensive recovery process may be required when the environment is opened | |
| je-recovery-required | FATAL | CRITICAL | 1.3.6.1.4.1.30221.2.10.3.22 | Berkeley DB Java Edition Requires Recovery | Indicates that a backend using the Berkeley DB Java Edition has encountered a severe error and requires recovery |
| jvm-misconfiguration | WARNING | WARNING | 1.3.6.1.4.1.30221.2.10.3.143 | Indicates that recommended JVM options for this server are missing or misconfigured | Indicates that JVM arguments are misconfigured |
| large-attribute-update-failure | ERROR | 1.3.6.1.4.1.30221.2.10.3.63 | Error Updating Large Attribute | Indicates that an error occurred while attempting to update large attribute for an entry in a manner that may have resulted in the large attribute information being out of sync with the rest of the entry contents | |
| ldap-connection-handler-cannot-listen | FATAL | 1.3.6.1.4.1.30221.2.10.3.23 | LDAP Connection Handler Startup Error | Indicates that an error occurred when the LDAP connection handler tried to start listening for client connections and therefore the connection handler will be disabled | |
| ldap-connection-handler-consecutive-failures | FATAL | 1.3.6.1.4.1.30221.2.10.3.24 | LDAP Connection Handler Disabled After Failures | Indicates that an LDAP connection handler has experienced consecutive failures and will be disabled | |
| ldap-connection-handler-uncaught-error | FATAL | 1.3.6.1.4.1.30221.2.10.3.25 | LDAP Connection Handler Disabled After Error | Indicates that an LDAP connection handler has encountered an uncaught error and will be disabled | |
| ldif-backend-cannot-write | ERROR | 1.3.6.1.4.1.30221.2.10.3.26 | Error Writing LDIF Backend Backing File | Indicates that an error occurred while trying to write the backing file for the LDIF backend | |
| ldif-connection-handler-io-error | ERROR | 1.3.6.1.4.1.30221.2.10.3.28 | LDIF Connection Handler I/O Error | Indicates that an LDIF connection handler has encountered an I/O error that has prevented it from processing | |
| ldif-connection-handler-parse-error | ERROR | 1.3.6.1.4.1.30221.2.10.3.27 | Error Parsing LDIF Backend File | Indicates that an LDIF connection handler encountered an error while parsing an LDIF file | |
| leaving-lockdown-mode | INFO | 1.3.6.1.4.1.30221.2.10.3.29 | Server Leaving Lockdown Mode | Indicates that the server is leaving lockdown mode and resuming normal operation | |
| log-file-rotation-listener-invoke-error | ERROR | 1.3.6.1.4.1.30221.2.10.3.141 | Error Invoking a Log File Rotation Listener | Indicates that an error occurred while attempting to invoke a log file rotation listener for a recently-rotated log file | |
| log-file-rotation-listener-processing-takes-too-long | WARNING | 1.3.6.1.4.1.30221.2.10.3.142 | Log File Rotation Listener Processing Takes Too Long | Indicates that a logger is rotating files more quickly than its associated rotation listeners can process them | |
| logging-error | ERROR | 1.3.6.1.4.1.30221.2.10.3.30 | Error Logging Message | Indicates that an error occurred while attempting to log a message | |
| low-disk-space-error | ERROR | MAJOR | 1.3.6.1.4.1.30221.2.10.3.46 | Low Disk Space Error | The amount of usable disk space has dropped below the configured low space error threshold |
| low-disk-space-warning | WARNING | WARNING | 1.3.6.1.4.1.30221.2.10.3.45 | Low Disk Space Warning | The amount of usable disk space has dropped below the configured low space warning threshold |
| mirrored-subtree-manager-connection-asymmetry | ERROR | MAJOR | 1.3.6.1.4.1.30221.2.10.3.161 | Mirrored subtree connection asymmetry | Indicates that the mirrored subtree manager has had an unequal number of outbound and inbound connections for more than the configured grace period |
| mirrored-subtree-manager-failed-outbound-connection | WARNING | WARNING | 1.3.6.1.4.1.30221.2.10.3.160 | Mirrored subtree outbound connection failure | Indicates that the mirrored subtree manager failed to establish a connection to a peer server within the configured grace period |
| mirrored-subtree-manager-forced-as-master-error | ERROR | MAJOR | 1.3.6.1.4.1.30221.2.10.3.134 | Mirrored subtree manager found more than one server that were forced as masters | Indicates that the mirrored subtree manager found more than one server that were forced to act as masters |
| mirrored-subtree-manager-forced-as-master-warning | WARNING | WARNING | 1.3.6.1.4.1.30221.2.10.3.133 | Mirrored subtree manager found a server that was forced as master | Indicates that the mirrored subtree manager found a server that was forced to act as master |
| mirrored-subtree-manager-no-master-found | ERROR | MAJOR | 1.3.6.1.4.1.30221.2.10.3.132 | Mirrored subtree manager found no suitable master | Indicates that the mirrored subtree manager was unable to determine a suitable server to act as the master of the topology |
| mirrored-subtree-manager-operation-error | ERROR | 1.3.6.1.4.1.30221.2.10.3.131 | Mirrored subtree manager operation error | Indicates that the mirrored subtree manager encountered an unexpected error while processing an update operation | |
| mirrored-subtree-server-not-in-topology | ERROR | MAJOR | 1.3.6.1.4.1.30221.2.10.3.135 | Mirrored subtree server not in topology | Indicates that this server is no longer functional because it does not exist in the topology registry most likely because it was removed from the topology with the remove-defunct-server tool |
| missing-schema-elements-referenced-by-backend | ERROR | 1.3.6.1.4.1.30221.2.10.3.162 | Missing Schema Elements Referenced by Backend | Indicates that a backend references one or more schema elements that are no longer defined in the server, and that operations involving entries containing those schema elements may not be processed correctly | |
| monitoring-endpoint-unable-to-connect | ERROR | 1.3.6.1.4.1.30221.2.10.3.165 | Monitoring Endpoint Unable to Connect | Indicates that a monitoring endpoint was unable to connect or write to the configured host and port | |
| no-enabled-alert-handlers | WARNING | WARNING | 1.3.6.1.4.1.30221.2.10.3.159 | No Enabled Alert Handlers | No alert handlers have been enabled. Alerts will be written to logs/errors, but administrators will not be otherwise notified of current or impending problems, which could lead to an outage that was avoidable |
| offline-config-change-detected | WARNING | 1.3.6.1.4.1.30221.2.10.3.97 | Offline Configuration Change | Indicates that a configuration change was made with the server offline | |
| out-of-disk-space-error | FATAL | CRITICAL | 1.3.6.1.4.1.30221.2.10.3.47 | Out of Disk Space | The amount of usable disk space has dropped below the configured out of space error threshold |
| replication-backlogged | WARNING | WARNING | 1.3.6.1.4.1.30221.2.10.3.65 | Replication Backlogged | Indicates that the replication backlog has exceeded the replication backlog count alert threshold for longer than the replication backlog duration alert threshold |
| replication-generation-id-mismatch | WARNING | WARNING | 1.3.6.1.4.1.30221.2.10.3.144 | Mismatched generation ID | The generation ID stored in the backend does not match the generation ID stored in the replication changelog database. To recover initialize from the server that has authoritative data to all other servers participating in replication |
| replication-metadata-decode-failure | WARNING | 1.3.6.1.4.1.30221.2.10.3.107 | Replication Conflict Resolution Metadata Decoding Failure | Indicates that an error occurred while attempting to decode replication conflict resolution metadata (as contained in the ds-sync-hist attribute) for an entry | |
| replication-missing-changes | WARNING | WARNING | 1.3.6.1.4.1.30221.2.10.3.52 | Potential Missed Replication Changes | Indicates that some updates may have been lost |
| replication-monitor-data-unavailable | WARNING | 1.3.6.1.4.1.30221.2.10.3.66 | Replication Monitor Data Missing | Indicates that replication monitor data is unavailable from cn=monitor | |
| replication-plugin-message-serialization-failure | WARNING | 1.3.6.1.4.1.30221.2.10.3.53 | Replication Plugin Serialization/Deserialization Error | Indicates that the replication plugin failed to serialize or deserialize a replication message. Replicas should be tested for any data inconsistency using - for example - the ldap-diff tool. Manual entry modification may be necessary to remedy this situation | |
| replication-replay-failed | ERROR | 1.3.6.1.4.1.30221.2.10.3.82 | Replication Replay Operation Failed | Indicates that the server failed to replay a replication operation due to abnormal circumstances. Please refer to the Recovering a Replica with Missed Changes section in the Administration Guide on how to resolve this issue | |
| replication-server-changelog-failure | FATAL | CRITICAL | 1.3.6.1.4.1.30221.2.10.3.54 | Error Accessing Replication Changelog Database | Indicates that the replication server encountered an error while accessing the replication changelog database. Subsequent database access attempts may also fail. The replication server could lose replication updates if database problems persist |
| replication-server-listen-failure | ERROR | MAJOR | 1.3.6.1.4.1.30221.2.10.3.81 | Error Listening on the Replication Server Port | Indicates that the replication server encountered an error while trying to listen on the configured replication port. There may be another application listening on the same port or the replication server host name may not be resolvable. Check the replication server configuration |
| replication-unresolved-conflict | ERROR | 1.3.6.1.4.1.30221.2.10.3.31 | Unresolved Replication Conflict Detected | Indicates that the server detected a replication conflict that could not be automatically resolved | |
| replication-unsent-changes | WARNING | 1.3.6.1.4.1.30221.2.10.3.88 | Replica failed to send all pending updates at shutdown | Indicates that one or more replicas were unable to send all pending update messages to the replication server before completing the shutdown process. These updates will be submitted when the server starts up | |
| restart-required | WARNING | WARNING | 1.3.6.1.4.1.30221.2.10.3.146 | Server restart required | A server restart is required for configuration changes to take effect |
| restricted-subtree-accessibility | WARNING | 1.3.6.1.4.1.30221.2.10.3.102 | Restricted Subtree Accessibility | Indicates that a subtree has been read-only or hidden for longer than the configured time limit | |
| schema-checking-disabled | WARNING | 1.3.6.1.4.1.30221.2.10.3.98 | Schema Checking Disabled | Indicates that schema checking has been disabled in the server, which can lead to degraded performance and unexpected behavior in the server as well as client applications | |
| sensitive-trace-data-logged-warning | WARNING | WARNING | 1.3.6.1.4.1.30221.2.10.3.136 | Sensitive data may be logged | The Trace Logger may log sensitive data |
| server-jvm-paused | WARNING | 1.3.6.1.4.1.30221.2.10.3.85 | Server JVM Paused | Indicates that the JVM for the Directory Server has paused for some reason possibly due to misconfiguration | |
| server-shutting-down | INFO | 1.3.6.1.4.1.30221.2.10.3.32 | Shutdown Begun | Indicates that the Directory Server has begun the shutdown process | |
| server-started | INFO | 1.3.6.1.4.1.30221.2.10.3.33 | Startup Complete | Indicates that the Directory Server has completed the startup process | |
| server-starting | INFO | 1.3.6.1.4.1.30221.2.10.3.84 | Startup Begun | Indicates that the Directory Server has begun the startup process | |
| subtree-delete-interrupted | ERROR | 1.3.6.1.4.1.30221.2.10.3.112 | Subtree Delete Interrupted | Indicates that a subtree delete operation has been interrupted for some reason (e.g., by an abandon or cancel request, a server shutdown, or an internal error) and the target subtree may have only been partially deleted | |
| system-current-time-shifted | ERROR | 1.3.6.1.4.1.30221.2.10.3.99 | System Current Time Has Shifted | Indicates that the system time has shifted backwards, which might have an impact on time-related aspects of the server | |
| system-nanotime-stopped | ERROR | 1.3.6.1.4.1.30221.2.10.3.77 | System.nanoTime() Has Stopped | Indicates that Java's System.nanoTime() has stopped returning updated values | |
| task-completed | INFO | 1.3.6.1.4.1.30221.2.10.3.152 | Task Completed | Indicates that an administrative task has completed successfully | |
| task-failed | ERROR | 1.3.6.1.4.1.30221.2.10.3.153 | Task Failed | Indicates that an administrative task has failed to completed successfully | |
| task-started | INFO | 1.3.6.1.4.1.30221.2.10.3.151 | Task Started | Indicates that an administrative task has started running | |
| third-party-extension-exception | ERROR | 1.3.6.1.4.1.30221.2.10.3.111 | Third-Party Extension Exception | Indicates that a third-party extension has thrown an unexpected exception | |
| thread-exit-holding-lock | ERROR | 1.3.6.1.4.1.30221.2.10.3.51 | Thread Exited Holding Lock | Indicates that a thread has exited while still holding one or more locks | |
| uncaught-exception | ERROR | 1.3.6.1.4.1.30221.2.10.3.34 | Uncaught Exception Detected | Indicates that the server has detected an uncaught exception that may have caused a thread to terminate | |
| unindexed-internal-search | WARNING | 1.3.6.1.4.1.30221.2.10.3.129 | Unindexed Internal Search | Indicates that the server is about to process an unindexed internal search operation | |
| unique-attribute-sync-conflict | ERROR | 1.3.6.1.4.1.30221.2.10.3.35 | Unique Attribute Replication Conflict Detected | Indicates that the server has detected a unique attribute conflict that was introduced from replication | |
| unique-attribute-sync-error | ERROR | 1.3.6.1.4.1.30221.2.10.3.36 | Error Detecting Unique Attribute Replication Conflicts | Indicates that the server has encountered an error while attempting to detect unique attribute conflicts via replication | |
| unlicensed-product | WARNING | WARNING | 1.3.6.1.4.1.30221.2.10.3.150 | Invalid Product License | Indicates that the Directory Server license key is not set, is invalid, or is expired |
| unrecognized-alert-type | ERROR | 1.3.6.1.4.1.30221.2.10.3.80 | Unrecognized Alert Type | Indicates that the server encountered an administrative alert type that it did not recognize | |
| user-defined-error | ERROR | 1.3.6.1.4.1.30221.2.10.3.37 | Third-party Error Alert | Indicates that an error alert notification was generated from third-party code | |
| user-defined-fatal | FATAL | 1.3.6.1.4.1.30221.2.10.3.38 | Third-party Fatal Error Alert | Indicates that a fatal error alert notification was generated from third-party code | |
| user-defined-info | INFO | 1.3.6.1.4.1.30221.2.10.3.39 | Third-party Informational Alert | Indicates that an informational alert notification was generated from third-party code | |
| user-defined-warning | WARNING | 1.3.6.1.4.1.30221.2.10.3.40 | Third-party Warning Alert | Indicates that a warning alert notification was generated from third-party code | |
| work-queue-backlogged | ERROR | MAJOR | 1.3.6.1.4.1.30221.2.10.3.50 | Work Queue Backlogged | Indicates that the work queue has accumulated a significant backlog and that operations are being required to wait for long periods of time for worker threads to process them. (If the system clock was recently changed, then you can ignore this message if there are no other indications there is a problem) |
| work-queue-full | ERROR | MAJOR | 1.3.6.1.4.1.30221.2.10.3.42 | Work Queue Full | Indicates that the work queue is full and has rejected a client request |
| work-queue-no-threads-remaining | FATAL | CRITICAL | 1.3.6.1.4.1.30221.2.10.3.43 | All Worker Threads Terminated | Indicates that all worker threads have been terminated due to errors and the server must shut down |
| worker-thread-caught-error | ERROR | 1.3.6.1.4.1.30221.2.10.3.41 | Worker Thread Unexpected Error | Indicates that a worker thread has caught an unexpected error that has caused it to be terminated |