OpenDJ can send alerts to provide notifications of significant server events. Yet alert notifications are not enabled by default. You can use the dsconfig command to enable alert notifications.
$ dsconfig set-alert-handler-prop --port 4444 --hostname opendj.example.com --bindDN "cn=Directory Manager" --bindPassword password --handler-name "JMX Alert Handler" --set enabled:true --trustAll --no-prompt
OpenDJ can also send mail over SMTP instead of JMX notifications. Before you set up the SMTP-based alert handler, you must identify an SMTP server to which OpenDJ sends messages.
$ dsconfig set-global-configuration-prop --port 4444 --hostname opendj.example.com --bindDN "cn=Directory Manager" --bindPassword password --set smtp-server:smtp.example.com --trustAll --no-prompt $ dsconfig create-alert-handler --port 4444 --hostname opendj.example.com --bindDN "cn=Directory Manager" --bindPassword password --handler-name "SMTP Alert Handler" --type smtp --set enabled:true --set message-subject:"OpenDJ Alert, Type: %%alert-type%%, ID: %%alert-id%%" --set message-body:"%%alert-message%%" --set recipient-address:kvaughan@example.com --set sender-address:opendj@example.com --trustAll --no-prompt
Alert Types
OpenDJ directory server uses the following types when sending
alerts. For alert types that indicate server problems, check
OpenDJ/logs/errors for details.
org.opends.server.AccessControlDisabled-
The access control handler has been disabled.
org.opends.server.AccessControlEnabled-
The access control handler has been enabled.
org.opends.server.authentiation.dseecompat.ACIParseFailed-
The dseecompat access control subsystem failed to correctly parse one or more ACI rules when the server first started.
org.opends.server.BackendRunRecovery-
The JE backend has thrown a
RunRecoveryException. The directory server needs to be restarted. org.opends.server.CannotCopySchemaFiles-
A problem has occurred while attempting to create copies of the existing schema configuration files before making a schema update, and the schema configuration has been left in a potentially inconsistent state.
org.opends.server.CannotRenameCurrentTaskFile-
The directory server is unable to rename the current tasks backing file in the process of trying to write an updated version.
org.opends.server.CannotRenameNewTaskFile-
The directory server is unable to rename the new tasks backing file into place.
org.opends.server.CannotScheduleRecurringIteration-
The directory server is unable to schedule an iteration of a recurring task.
org.opends.server.CannotWriteConfig-
The directory server is unable to write its updated configuration for some reason and therefore the server may not exhibit the new configuration if it is restarted.
org.opends.server.CannotWriteNewSchemaFiles-
A problem has occurred while attempting to write new versions of the server schema configuration files, and the schema configuration has been left in a potentially inconsistent state.
org.opends.server.CannotWriteTaskFile-
The directory server is unable to write an updated tasks backing file for some reason.
org.opends.server.DirectoryServerShutdown-
The directory server has begun the process of shutting down.
org.opends.server.DirectoryServerStarted-
The directory server has completed its startup process.
org.opends.server.DiskFull-
Free disk space has reached the full threshold.
Default is 20 MB.
org.opends.server.DiskSpaceLow-
Free disk space has reached the low threshold.
Default is 100 MB.
org.opends.server.EnteringLockdownMode-
The directory server is entering lockdown mode, in which only root users are allowed to perform operations and only over the loopback address.
org.opends.server.LDAPHandlerDisabledByConsecutiveFailures-
Consecutive failures have occurred in the LDAP connection handler and have caused it to become disabled.
org.opends.server.LDAPHandlerUncaughtError-
Uncaught errors in the LDAP connection handler that have caused it to become disabled.
org.opends.server.LDIFBackendCannotWriteUpdate-
An LDIF backend was unable to store an updated copy of the LDIF file after processing a write operation.
org.opends.server.LDIFConnectionHandlerIOError-
The LDIF connection handler encountered an I/O error that prevented it from completing its processing.
org.opends.server.LDIFConnectionHandlerParseError-
The LDIF connection handler encountered an unrecoverable error while attempting to parse an LDIF file.
org.opends.server.LeavingLockdownMode-
The directory server is leaving lockdown mode.
org.opends.server.ManualConfigEditHandled-
The directory server detects that its configuration has been manually edited with the server online and those changes were overwritten by another change made through the server. The manually-edited configuration will be copied to another location.
org.opends.server.ManualConfigEditLost-
The directory server detects that its configuration has been manually edited with the server online and those changes were overwritten by another change made through the server. The manually-edited configuration could not be preserved due to an unexpected error.
org.opends.server.replication.UnresolvedConflict-
Multimaster replication cannot resolve a conflict automatically.
org.opends.server.UncaughtException-
A directory server thread has encountered an uncaught exception that caused that thread to terminate abnormally. The impact that this problem has on the server depends on which thread was impacted and the nature of the exception.
org.opends.server.UniqueAttributeSynchronizationConflict-
A unique attribute conflict has been detected during synchronization processing.
org.opends.server.UniqueAttributeSynchronizationError-
An error occurred while attempting to perform unique attribute conflict detection during synchronization processing.
