DS servers can send alerts for significant server events.
The following example enables JMX alert notifications:
dsconfig \ set-alert-handler-prop \ --hostname localhost \ --port 4444 \ --bindDN uid=admin \ --bindPassword password \ --handler-name "JMX Alert Handler" \ --set enabled:true \ --usePkcs12TrustStore /path/to/opendj/config/keystore \ --trustStorePasswordFile /path/to/opendj/config/keystore.pin \ --no-prompt
The following example sets up an SMTP server, and configures email alerts:
dsconfig \ create-mail-server \ --hostname localhost \ --port 4444 \ --bindDN uid=admin \ --bindPassword password \ --server-name "SMTP server" \ --set enabled:true \ --set auth-username:mail.user \ --set auth-password:password \ --set smtp-server:smtp.example.com:587 \ --set trust-manager-provider:"JVM Trust Manager" \ --set use-start-tls:true \ --usePkcs12TrustStore /path/to/opendj/config/keystore \ --trustStorePasswordFile /path/to/opendj/config/keystore.pin \ --no-prompt$
dsconfig \ create-alert-handler \ --hostname localhost \ --port 4444 \ --bindDN uid=admin \ --bindPassword password \ --handler-name "SMTP Alert Handler" \ --type smtp \ --set enabled:true \ --set message-subject:"DS Alert, Type: %%alert-type%%, ID: %%alert-id%%" \ --set message-body:"%%alert-message%%" \ --set recipient-address:email@example.com \ --set sender-address:firstname.lastname@example.org \ --usePkcs12TrustStore /path/to/opendj/config/keystore \ --trustStorePasswordFile /path/to/opendj/config/keystore.pin \ --no-prompt
DS servers use the following alert types. For alert types that indicate server problems, check
logs/errors for details:
The access control handler has been disabled.
The access control handler has been enabled.
The dseecompat access control subsystem failed to correctly parse one or more ACI rules when the server first started.
The pluggable backend has thrown a
RunRecoveryException. The server needs to be restarted.
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.
The server is unable to rename the current tasks backing file in the process of trying to write an updated version.
The server is unable to rename the new tasks backing file into place.
The server is unable to schedule an iteration of a recurring task.
The 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.
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.
The server is unable to write an updated tasks backing file for some reason.
The server has begun the process of shutting down.
The server has completed its startup process.
Free disk space has reached the full threshold.
Default is 6% of the size of the file system.
Free disk space has reached the low threshold.
Default is 10% of the size of the file system.
The server is entering lockdown mode, wherein only root users are allowed to perform operations and only over the loopback address.
Consecutive failures have occurred in the LDAP connection handler and have caused it to become disabled.
Uncaught errors in the LDAP connection handler have caused it to become disabled.
An LDIF backend was unable to store an updated copy of the LDIF file after processing a write operation.
The LDIF connection handler encountered an I/O error that prevented it from completing its processing.
The LDIF connection handler encountered an unrecoverable error while attempting to parse an LDIF file.
The server is leaving lockdown mode.
The 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.
The 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.
Multimaster replication cannot resolve a conflict automatically.
A 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.
A unique attribute conflict has been detected during synchronization processing.
An error occurred while attempting to perform unique attribute conflict detection during synchronization processing.