Exit Print View

Sun OpenDS Standard Edition 2.2 Administration Guide

Get PDF Book Print View
 

Document Information

Before You Start

Starting and Stopping Your Server Instance

Configuring the Server Instance

Configuring the Proxy Components

Configuring Security Between Clients and Servers

Configuring Security Between the Proxy and the Data Source

Configuring Servers With the Control Panel

Managing Directory Data

Replicating Directory Data

Controlling Access To Data

Managing Users and Groups

Monitoring Sun OpenDS Standard Edition

Configuring Monitor Providers

To View Monitor Providers

To Disable a Monitor Provider

To Create a Monitor Provider

Configuring Logs With dsconfig

Log Configuration Overview

Configuring Log Publishers

To Create a Log Publisher

Logging Internal Operations

Configuring Log Retention Policies

To Create a Log Retention Policy

To Modify a Log Retention Policy

Configuring Log Rotation Policies

To Create a Log Rotation Policy

Configuring Debug Targets

To Create a Debug Target

To Modify a Debug Target

Logging Access Control Information

Differences Between Logging in Sun OpenDS Standard Edition and Sun Java System Directory Server

Configuring Alerts and Account Status Notification Handlers

Managing Alert Handlers

To View All Configured Alert Handlers

To Enable an Alert Handler

To Create a New Alert Handler

To Delete an Alert Handler

To Disable an Alert Type

Managing Account Status Notification Handlers

To View the Configured Account Status Notification Handlers

To Enable Account Status Notification Handlers

To Create a New Account Status Notification Handler

To Delete an Account Status Notification Handler

Monitoring the Server With LDAP

Viewing Monitoring Information Using the cn=monitor Entry

To View the Available Monitoring Information

To Monitor General-Purpose Server Information

To Monitor System Information

To Monitor Version Information

To Monitor the User Root Back End

To Monitor the Backup Back End

To Monitor the Tasks Back End

To Monitor the monitor Back End

To Monitor the Schema Back End

To Monitor the adminRoot Back End

To Monitor the ads-truststore Back End

To Monitor Client Connections

To Monitor the LDAP Connection Handler

To Monitor LDAP Connection Handler Statistics

To Monitor Connections on the LDAP Connection Handler

To Monitor the Administration Connector

To Monitor Administration Connector Statistics

To Monitor Connections on the Administration Connector

To Monitor the LDIF Connection Handler

To Monitor the Work Queue

To Monitor JVM Stack Trace Information

To Monitor the JVM Memory Usage

To Monitor the userRoot Database Environment

To Monitor the Entry Cache

To Monitor Network Groups

To Monitor Distributions

To Monitor Load Balancing

To Monitor Remote LDAP Servers

To Monitor a Global Index

To Monitor a Global Index Catalog

Monitoring Using manage-tasks Command

Accessing Logs

To View the Access Logs

To View the Audit Logs

To View the Debug Logs

To View the Error Logs

To View the Replication Repair Logs

To View the server.out Logs

To View the vdp-setup Logs

General Purpose Enterprise Monitoring Solutions

Monitoring the Server With JConsole

To Configure JMX on a Server Instance

Starting JConsole

Accessing a Server Instance From JConsole

Viewing Monitoring Information With JConsole

Monitoring the Server With SNMP

Configuring SNMP in the Server

To Configure SNMP in the Server

To View the SNMP Connection Handler Properties

To Access SNMP on a Server Instance

SNMP Security Configuration

Monitoring a Replicated Topology

Monitoring Replication Status With dsreplication

Advanced Replication Monitoring

Monitoring the Directory Server With the Control Panel

To View Monitoring Information With the Control Panel

Monitoring the Proxy Server With the Control Panel

To View Proxy Configuration Information

To View Proxy Monitoring Information

Setting LDAP Data Source Monitoring Properties in the Proxy

Modifying Monitoring of Remote LDAP Servers

To Modify the Values of Monitoring of Remote LDAP Server

Improving Performance

Advanced Administration

Managing Alert Handlers

Sun OpenDS Standard Edition supports the following alert handlers:

To View All Configured Alert Handlers

Sun OpenDS Standard Edition stores alert handlers information in the configuration file under the cn=Alert Handlers,cn=config subtree. You can access the information using the dsconfig command.

To Enable an Alert Handler

The JMX alert handler is disabled by default. Before you begin, you must configure JMX on the server. For more information, see Monitoring the Server With JConsole.

  1. To list the alert handler's properties, use the dsconfig command as follows.
    $ dsconfig -h localhost -p 4444 -D "cn=directory manager" -w password -n \
      get-alert-handler-prop \
      --handler-name "JMX Alert Handler"
    
    Property            : Value(s)
    --------------------:---------------------------------------------
    disabled-alert-type : -
    enabled             : false
    enabled-alert-type  : -
  2. To enable the alert handler, use dsconfig as follows.
    $ dsconfig -h localhost -p 4444 -D "cn=directory manager" -w password -n \
      set-alert-handler-prop \
      --handler-name "JMX Alert Handler" --set enabled:true
  3. (Optional) Verify the change by using dsconfig.
    $ dsconfig -h localhost -p 4444 -D "cn=directory manager" -w password -n \
      get-alert-handler-prop \
      --handler-name "JMX Alert Handler"
    
    Property            : Value(s)
    --------------------:---------------------------------------------
    disabled-alert-type : -
    enabled             : true
    enabled-alert-type  : -

To Create a New Alert Handler

You can create a new alert handler by using dsconfig. This example configures a new SMTP handler. Before starting this procedure, ensure that you have configured an SMTP server for your server.

  1. Use dsconfig with the create-alert-handler subcommand to create the handler.
    $ dsconfig -h localhost -p 4444 -D "cn=directory manager" -w password -n \
      create-alert-handler \
      --handler-name "my SMTP Handler" --type smtp --set enabled:true \
      --set message-body:"Alert Type: %%alert-type%%\n\nAlert ID: \
      %%alert-id%%\n\nAlert Message: %%alert-message%%" \
      --set message-subject:"Alert Message" \
      --set recipient-address:directorymanager@example.com \
      --set sender-address:OpenDS-Alerts@directory.example.com
  2. (Optional) View the list of alert handlers by using dsconfig.
    $ dsconfig -h localhost -p 4444 -D "cn=directory manager" -w password -n \
     list-alert-handlers
Supported Alert Types

The server sends out message alerts when an alert type event occurs in the system. The supported alert types are defined in the following table.

Alert Type
Description
Access Control Disabled

Java Class: org.opends.server.AccessControlDisabled

Notify administrator that the access control handler has been disabled.
Access Control Enabled

Java Class: org.opends.server.Enabled

Notify administrator that the access control handler has been enabled.
Access Control Parse Failed

Java Class: org.opends.server.authentication.dseecompat.ACIParseFailed

Notify administrator if the DSEE compatible access control subsystem failed to correctly parse one or more ACI rules when the server is first started.
Backend Environment Unusable

Java Class: org.opends.server.BackendRunRecovery

Notify administrator that the JE back end throws a RunRecoveryException and the directory server needs to be restarted.
Cannot Copy Schema Files

Java Class: org.opends.server.CannotCopySchemaFiles

Notify administrator if a problem occurs while attempting to create copies of the existing schema configuration before making a schema update, and the schema configuration is left in a potentially inconsistent state.
Cannot Find Recurring Task

Java Class: org.opends.server.CannotFindRecurringTask

Notify administrator if the directory server is unable to locate a recurring task definition in order to schedule the next iteration once the previous iteration has completed.
Cannot Rename Current Task File

Java Class: org.opends.server.CannotRenameCurrentTaskFile

Notify administrator if the directory server is unable to rename the current tasks backing file in the process of trying to write an updated version.
Cannot Rename New Task File

Java Class: org.opends.server.CannotRenameNewTaskFile

Notify administrator if the directory server is unable to rename the new tasks backing file into place.
Cannot Schedule Recurring Iteration

Java Class: org.opends.server.CannotScheduleRecurringIteration

Notify administrator if the directory server is unable to schedule an iteration of a recurring task.
Cannot Write Configuration

Java Class: org.opends.server.CannotWriteConfig

Notify administrator if the directory server is unable to write its updated configuration for some reason and so the server cannot exhibit the new configuration if it is restarted.
Cannot Write New Schema Files

Java Class: org.opends.server.CannotWriteNewSchemaFiles

Notify administrator if a problem occurs while attempting to write new versions of the server schema configuration files, and the schema configuration is left in a potentially inconsistent state.
Cannot Write Task File

Java Class: org.opends.server.CannotWriteTaskFile

Notify administrator if the directory server is unable to write an updated tasks backing file for some reason.
Distribution Backend Does Not Support PreRead Control

Java Class: com.sun.dps.server.distribution.globalindex.UnsupportedDirectoryBackend

Notify administrators if the distribution is unable to maintain the content of the global index catalog. This will happen \ if one or more servers do not support the Pre-Read Entry Control (RFC 4527)
Entering Lockdown Mode

Java Class: org.opends.server.EnteringLockdownMode

Notify administrator that the directory server is entering lockdown mode, in which only root users will be allowed to perform operations and only over the loopback address.
LDAP Connection Handler Consecutive Failures

Java Class: org.opends.server.LDAPHandlerDisabledByConsecutiveFailures

Notify administrator of consecutive failures that have occurred in the LDAP connection handler that have caused it to become disabled.
LDAP Connection Handler Uncaught Error

Java Class: org.opends.server.LDAPHandlerUncaughtError

Notify administrator of uncaught errors in the LDAP connection handler that have caused it to become disabled.
LDAP Server Extension Failed

Java Class: com.sun.dps.server.workflowelement.proxyldap.LDAPServerExtension.LDAPServerExtensionDown

Notify administrator that the LDAP Server Extension has been detected as Down.
LDAP Server Extension is Up

Java Class: com.sun.dps.server.workflowelement.proxyldap.LDAPServerExtension.LDAPServerExtensionUp

Notify administrator that the LDAP Server Extension has been detected as UP.
LDIF Backend Cannot Write Update

Java Class: org.opends.server.LDIFBackendCannotWriteUpdate

Notify administrator that an LDIF back end was unable to store an updated copy of the LDIF file after processing a write operation.
LDIF ConnHandler Parse Error

Java Class: org.opends.server.LDIFConnectionHandlerParseError

Notify administrator that the LDIF connection handler encountered an unrecoverable error while attempting to parse an LDIF file.
LDIF ConnHandler IO Error

Java Class: org.opends.server.LDIFConnectionHandlerIOError

Notify administrator that the LDIF connection handler encountered an I/O error that prevented it from completing its processing.
Leaving Lockdown Mode

Java Class: org.opends.server.LeavingLockdownMode

Notify administrator that the directory server is leaving lockdown mode.
Manual Config Edit Handled

Java Class: org.opends.server.ManualConfigEditHandled

Notify administrator if 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 off to another location.
Manual Config Edit Lost

Java Class: org.opends.server.ManualConfigEditLost

Notify administrator if 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.
New route elected by the SaturationLoadBalancingAlgorithm

Java Class: com.sun.dps.server.SaturationLoadBalancer

Notify administrator that a new route has been elected as active route by the saturation load balancing algorithm.
New route elected by the FailoverLoadBalancingAlgorithm

Java Class: com.sun.dps.server.FailoverLoadBalancer

Notify administrator that a new route has been elected as the active route by the failover load balancing algorithm.
Replication Unresolved Conflict

Java Class: org.opends.server.replication.UnresolvedConflict

Notify administrator if the multimaster replication cannot automatically resolve a conflict.
Server Started

Java Class: org.opends.server.DirectoryServerStarted

Notify administrator that the directory server has completed its startup process.
Server Shutdown

Java Class: org.opends.server.DirectoryServerShutdown

Notify administrator that the directory server has begun the process of shutting down.
State change for a Saturation Load Balancing Route

Java Class: com.sun.dps.server.SaturationLoadBalancer

Notify administrator that the saturation load balancing route state has changed (either from saturated to not saturated or from not saturated to saturated).
Uncaught Exception

Java Class: org.opends.server.UncaughtException

Notify administrator if a directory server thread has encountered an uncaught exception that caused the thread to terminate abnormally. The impact that this problem has on the directory server depends on which thread was impacted and the nature of the exception.
Unique Attr Sync Conflict

Java Class: org.opends.server.UniqueAttributeSynchronizationConflict

Notify administrator that a unique attribute conflict has been detected during synchronization processing.
Unique Attr Sync Error

Java Class: org.opends.server.UniqueAttributeSynchronizationError

Notify administrator that an error occurred while attempting to perform unique attribute conflict detection during synchronization processing.
Unsupported Directory Backend

Java Class: com.sun.dps.server.distribution.globalindex.UnsupportedDirectoryBackend

Notify administrator that the distribution is unable to maintain the content of the global index catalog. This will happen if one or more servers do not support the Pre-Read Entry Control (RFC 4527).

To Delete an Alert Handler

The following example removes an alert handler from the directory server.


Note - You can simply disable an alert handler instead of deleting it. In this case, the alert handler is available if you need to enable it again in the future. For more information, see To Disable an Alert Type.


To Disable an Alert Type

By default, all alert types are allowed. If you specify a value for the enabled-alert-type property, only alerts with one of those types are allowed. If you specify a value for the disabled-alert-type property, all alert types except for the values in that property are allowed. Alert types are specified by their Java class, as shown in this example.