| Exit Print View | |
Sun OpenDS Standard Edition 2.0 Administration Guide |
|
|
|
Configuring the Directory Server
Configuring Security in the Directory Server
Monitoring the Directory Server
Working With Monitor Providers
Viewing Monitoring Information Using the cn=monitor Entry
To View the Available Monitoring Information
To Monitor General-Purpose Server Information
To Monitor Version Information
To Monitor the User Root Back End
To Monitor the Backup 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 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 userRoot Database Environment
To Monitor JVM Stack Trace Information
To Monitor the JVM Memory Usage
Monitoring Using Managed Tasks
Configuring Alert Notifications and Account Status Notification Handlers
General Purpose Enterprise Monitoring Solutions
Monitoring the Directory Server With JConsole
To Configure JMX on a Directory Server Instance
Accessing a Directory Server Instance From JConsole
Viewing Directory Monitoring Information With JConsole
Monitoring the Directory Server With SNMP
Configuring SNMP in the Directory Server
To Configure SNMP in the Directory Server
To View the SNMP Connection Handler Properties
To Access SNMP on a Directory Server Instance
Monitoring the Directory Server With the Control Panel
To View Monitoring Information With the Control Panel
Configuring Logs With dsconfig
Overview of Directory Server Logs
To Configure Log Retention Policies
To Configure Log Rotation Policies
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
To View All Configured Alert Handlers
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 a Replicated Topology
Monitoring Replication Status With dsreplication
The directory server provides logging mechanisms to record access, error, or debugging information for the directory server instance. Multiple loggers of a given type can be active at any time, which makes it possible to create logs for specific subtrees or different repositories. The directory server does not currently provide logging filters to restrict the type of information in the logs.
The following logs are provided:
Access logs. Access logs record information about the types of operations processed by the directory server.
Audit logs. Audit logs are a type of access log and record all activity on the directory server.
Debug logs. Debug logs record information that can be used for troubleshooting directory server problems or for providing detailed information about the directory server's processing.
Error logs. Error logs record all warnings, errors, or significant events that occur during directory server processing.
Replication repair logs. Replication repair logs record inconsistencies on a single directory server in a topology, based on events relating to the replication of global index catalogs.
The replication repair log is read-only and its use is restricted to enabling replication conflict resolution.
$ cd install-dir/logs
$ cat access | more [24/Oct/2008:16:02:52 -0500] CONNECT conn=0 from=127.0.0.1 to=127.0.0.1 protocol=LDAP [24/Oct/2008:16:02:52 -0500] BIND conn=0 op=0 msgID=1 type=SIMPLE dn="cn=Directory Manager" [24/Oct/2008:16:02:53 -0500] BIND conn=0 op=0 msgID=1 result="Success" authDN="cn=Directory Manager,cn=Root DNs,cn=config" etime=57 ...(more output)...
$ cd install-dir/logs
$ cat audit | more # 05/Nov/2008:13:32:58 -0600; conn=21; op=51 dn: cn=File-Based Audit Logger,cn=Loggers,cn=config changetype: modify replace: ds-cfg-enabled ds-cfg-enabled: true - replace: modifiersName modifiersName: cn=Directory Manager,cn=Root DNs,cn=config - replace: modifyTimestamp modifyTimestamp: 20081105193257Z # 05/Nov/2008:13:33:17 -0600; conn=21; op=57 dn: cn=File-Based Debug Logger,cn=Loggers,cn=config changetype: modify replace: ds-cfg-enabled ds-cfg-enabled: true - replace: modifiersName modifiersName: cn=Directory Manager,cn=Root DNs,cn=config - replace: modifyTimestamp modifyTimestamp: 20081105193316Z ...(more output)...
$ cd install-dir/logs
$ cat debug | more [24/Oct/2008:16:02:52 -0500] CONNECT conn=0 from=127.0.0.1 to=127.0.0.1 protocol=LDAP [24/Oct/2008:16:02:52 -0500] BIND conn=0 op=0 msgID=1 type=SIMPLE dn="cn=Directory Manager" [24/Oct/2008:16:02:53 -0500] BIND conn=0 op=0 msgID=1 result="Success" authDN="cn=Directory Manager,cn=Root DNs,cn=config" etime=57 ...(more output)...
$ cd install-dir/logs
$ cat error | more [24/Oct/2007:16:02:10 -0500] category=CONFIG severity=NOTICE msgID=3605006 msg=Access control has been enabled and will use the org.opends.server.authorization.dseecompat.AciHandler implementation [24/Oct/2007:16:02:17 -0500] category=JEB severity=NOTICE msgID=8847402 msg=The database backend userRoot containing 160 entries has started [24/Oct/2007:16:02:21 -0500] category=CORE severity=NOTICE msgID=458887 msg=The Directory Server has started successfully ...(more output)...
$ cd install-dir/logs
$ cat replication | more [09/Oct/2007:11:02:22 -0500] category=SYNC severity=NOTICE msgID=15138878 msg=Replication Server sr1-uaus-08/129.123.131.98:8989 now used for Replication Domain cn=admin data [09/Oct/2007:11:02:23 -0500] category=SYNC severity=NOTICE msgID=15138878 msg=Replication Server sr1-uaus-08/129.123.131.98:8989 now used for Replication Domain cn=schema [09/Oct/2007:11:02:23 -0500] category=SYNC severity=NOTICE msgID=15138878 msg=Replication Server sr1-uaus-08/129.123.131.98:8989 now used for Replication Domain dc=example,dc=com ...(more output)...
$ cd install-dir/logs
$ cat replication | more [24/Jun/2009:18:32:18 +0200] category=CORE severity=INFORMATION msgID=132 msg=The Directory Server is beginning the configuration bootstrapping process [24/Jun/2009:18:32:21 +0200] category=EXTENSIONS severity=INFORMATION msgID=1049147 msg=Loaded extension from file '$SERVER_ROOT/lib/extensions/distribution.jar' (build 1.0.0, revision 1057(20090618075417)) [24/Jun/2009:18:32:21 +0200] category=EXTENSIONS severity=INFORMATION msgID=1049147 msg=Loaded extension from file '$SERVER_ROOT/lib/extensions/globalindex.jar' (build 1.00, revision 1057(20090618075417)) [24/Jun/2009:18:32:21 +0200] category=EXTENSIONS severity=INFORMATION msgID=1049147 msg=Loaded extension from file '$SERVER_ROOT/lib/extensions/loadbalancing.jar' (build 1.0.0, revision 1057(20090618075417)) [24/Jun/2009:18:32:22 +0200] category=EXTENSIONS severity=INFORMATION msgID=1049147 msg=Loaded extension from file '$SERVER_ROOT/lib/extensions/proxyldap.jar' (build 1.0.0, revision 1057(20090618075417)) [24/Jun/2009:18:32:22 +0200] category=EXTENSIONS severity=INFORMATION msgID=1049147 msg=Loaded extension from file '$SERVER_ROOT/lib/extensions/snmp-mib2605.jar' (build 2.0.0, revision 5452) [24/Jun/2009:18:32:25 +0200] category=CORE severity=NOTICE msgID=458886 msg=Sun Virtual Directory Proxy 1.0.0 (OpenDS version = 2.0.0) (build 20090615154012Z, R5452) starting up ...(more output)...
|
|