Sun Java System Identity Synchronization for Windows 1 2004Q3 Installation and Configuration Guide |
Chapter 10
Understanding Audit and Error FilesIdentity Synchronization for Windows provides information about the installation and configuration status, the day-to-day system operations, and any error conditions that are related to your deployment.
This chapter explains how to access and understand this information in the following sections:
Understanding the LogsYou can view various types of information from the Status tab of the Identity Synchronization for Windows Console.
If you select one of the following nodes in the navigation tree pane (on the left), the content presented on the Status tab changes to provide specific information about that item.
- Directory Source: Select a directory source node (such as dc=example,dc=com) to view status information about that directory source.
- To Do: Select this node for a list of the steps you must complete to successfully install and configure Identity Synchronization for Windows (the program greys-out all completed steps).
- Audit File: Select this node for information about day-to-day system operations (including error conditions).
- Error File: Select this node for information about error conditions on your system. (The Error log essentially acts as a filter in which only the error entries are displayed.)
Figure 10-1 The Status Tab
Log Types
This section describes the different kinds of logs that are available for Identity Synchronization for Windows:
Central Logs
As long as Identity Synchronization for Windows components can access Message Queue, all audit and error messages will be logged in the Identity Synchronization for Windows central logger. Consequently, these central logs (which include messages from all components) are the primary logs to monitor.
The centralized logs are located on the machine where Core is installed, in the following directories:
The specific logs are described in Table 10-1.
Each central log also includes information about each component ID. For example,
In addition to the central logger, each component has it’s own local logs. You can use these local logs to diagnose problems with the connector if it cannot log to the central logger.
Local Component Logs
Each connector, the system manager, and the central logger have the following local logs:
Table 10-2 Local Logs
Log Name
Description
audit.log
A superset of error.log that includes messages about each synchronization event. These messages are also written to the central audit.log.
error.log
Warning and Severe messages are reported here. These messages are also written to the central error.log.
These local logs are located in the following subdirectories:
The sysmgr and clogger100 (central logger) directories are on the machine where Core is installed.
Identity Synchronization for Windows rotates these local component logs daily by moving the current log to a log file that includes the date, as follows:
audit_2004_08_06.log
Note
By default, Identity Synchronization for Windows deletes connector logs after ten days. You can extend this period by editing the com.sun.directory.wps.logging.maxmiumDaysToKeepOldLogs value in the Log.properties file and restarting the service daemon.
Local Windows NT Subcomponent Logs
The following Windows NT subcomponents also have local logs:
These subcomponent logs are located in the SUBC1XX (for example, SUBC100) subdirectories of the following directory:
<installation_root>/isw-<machine_name>/logs/
Identity Synchronization for Windows limits these files to 1 MB in size, and keeps only the last 10 logs.
Directory Server Plugin Logs
The Directory Server Plugin logs information through the Directory Server connector to the central log and through the Directory Server logging facility. Consequently, local Directory Server Plugin log messages will also be saved in the Directory Server error log.
Directory Server saves information into the error log from other Directory Server Plugins and components. To identify messages from the Identity Synchronization for Windows Directory Server Plugin, you can filter out lines containing the isw string.
By default, only minimal Plugin log messages are displayed in the error log.
For example:[14/Jun/2004:17:08:36 -0500] - ERROR<38747> - isw - conn=-1 op=-1 msgId=-1 - Plugins unable to establish connection to DS Connector at attila:1388, will retry later
You can change the default verbosity level of the Directory Server error log from the Directory Server Management Console as follows:
For more information about Directory Server logging, refer to the Sun Java System Directory 5 2004Q2 Server Administrator's Guide (http://docs.sun.com/db/coll/DirectoryServer_04q2).
Reading the Logs
Every log message includes the following information:
- Time: Indicates when (time and date) the log entry was generated. For example:
[13/Aug/2004:06:14:36:753 -0500]
- Level: Indicates the severity and verbosity of the log message.
Identity Synchronization for Windows uses the following log levels:
Table 10-3 Log Levels
Log Level
Description
INFO
These messages provide a minimum amount of information about each action so you can see that the system is running correctly. For example, you can see when a change is detected and when synchronization occurs. These messages are always logged to the audit log.
FINE
These messages contain more information about an action as it travels through the system.
FINER
These messages contain even more information about an action as it travels through the system. Turning the logging level to FINER for all components may impact performance.
FINEST
These messages contain the most information about an action as it travels through the system. Turning the logging level to FINEST for all components may significantly impact performance.
- Thread ID: Displays the Java thread ID of the function causing the event.
- ID: Identifies the component (console, system manager, and so forth.) causing the event.
- Host: Displays the name of the host causing the event.
- Message: Displays audit or error information associated with the event.
Some examples include:“Resetting Central Logger configuration ...”
“System manager is shutting down.”
“Processing request (ID=<ID_number> from the console to stop synchronization.”
Configuring Your Log FilesYou can use the Identity Synchronization for Windows Console to configure logging for your deployment, as follows:
- Open the Console and select the Configuration tab.
- In the navigation tree pane, and expand nodes until you see the Logs node.
- Select the Logs node and the Log Files panel is displayed on the Configuration tab (see Figure 10-2).
Figure 10-2 Configuring Log Files
- Use the Log Files pane to configure your log files, as follows:
- Write logs to file. Enable this option to write logs to a file on the Core host.
After selecting this option you can:
- Enable the default log directory and file (for example, /var/opt/SUNWisw/logs/central).
- Enable the Write log files to directory option, and then specify a path and file name for the log file.
Note
The Console does not verify whether a specified log file location actually exists. The central logger will try to create the log directory if it does not exist. Consequently, there is no indication that you specified and saved a nonexistent log location until you try to view the logs. After several attempts to view the logs, a message displays to report the Console’s inability to find logs at the specified location.
- On Solaris Only — Write logs to syslog daemon: Enable this option if Identity Synchronization for Windows resides on a Solaris platform.
Use the drop-down list to select a category for writing the log. (Default is DAEMON.)
Note
When you select this option, Identity Synchronization for Windows logs everything to the syslog; however, the syslog is configured by default to log WARNING and SEVERE messages only.
To configure syslog to log INFO messages, edit /etc/syslog.conf and change the following line:
*.err;kern.debug;daemon.notice;mail.crit /var/adm/messages
to
*.err;kern.debug;daemon.notice;daemon.info;mail.crit /var/adm/messages
After making this change, you must restart the syslog daemon as follows:
/etc/init.d/syslog stop ; /etc/init.d/syslog start
To enable FINE, FINER, and FINEST logging, include daemon.debug in the semi-colon separated list.
- Remove Old Logs: The number of log files will continue to grow (one per day) indefinitely. To avoid running out of disk space, enable this option and specify when the program can delete old logs from the central log file.
- Log Level. Use the drop-down list to select the level of detail you want to see in your system logs. (Review Log Levels.)
- Click the Save Log Configuration button to create log files based on the selected options.
Viewing Directory Source StatusTo view the status of your directory sources:
- From the Identity Synchronization for Windows Console, select the Status tab.
- In the navigation tree pane, expand the Directory Source node, and then select the directory source node (such as dc=example,dc=com).
The Status tab content changes to provide information related to the selected directory source (for example, see Figure 10-3).
Figure 10-3 Directory Source Status
Note
When viewing the Directory Source status you are essentially viewing the status of the connector associated with that Directory Source.
The following information is provided on the Status tab:
- Update: Click Update to refresh the information on this tab.
- State: Reflects the current state of the directory source. Valid states include:
- Uninstalled: The connector has not been installed.
- Installed: The connector is installed, but is not ready for synchronization because it has not received its runtime configuration yet. If the connector remains in this state for more than a minute, something is probably wrong.
- Ready: The connector is ready for synchronization, but it is currently not synchronizing any objects. A connector remains in the Ready state if synchronization has not been started or if synchronization has been started but not all subcomponents have established connections with the connectors.
- Syncing: The connector is synchronizing objects. There might still be errors, so consult the error log if you notice that changes are not synchronized.
- Active: Indicates whether the directory source is active or down.
- Last Communication: Indicates the time of the last response from this directory source’s connector.
Viewing Installation and Configuration StatusTo see which steps you must still complete in the Identity Synchronization for Windows installation and configuration process, use the following procedure:
- From the Identity Synchronization for Windows Console, select the Status tab.
- In the navigation tree pane, expand the To Do node.
The Status tab content changes to provide a checklist of the installation and configuration steps (for example, see Figure 10-3).
Figure 10-4 Viewing Your To Do List
- Click the Update button (upper right) to refresh the list.
Completed steps will be check-marked and greyed-out. You must complete the remaining steps to successfully complete the installation and configuration process.
Viewing Your Audit and Error LogsTo view your error logs:
- From the Identity Synchronization for Windows Console, select the Status tab.
- In the navigation tree pane, expand the Audit File or the Error File node.
The Status tab content changes to display the current logs (Figure 10-5).
Figure 10-5 Viewing Your Logs
The following information is provided on the Status tab:
- Refresh: Loads the latest audit or error information.
- Continuous: Updates and displays the latest audit or error information constantly.
- Log File: Displays the full path name of the audit or error log being read; for example:
C:\Program Files\Sun\MPS\isw-<hostname>\logs\central\audit.log
- Lines to show: Specifies how many audit or error entries to display. (Default is 25.)
Enabling Auditing on a Windows NT MachineIf you have a Windows NT machine in your deployment, verify that auditing is enabled or Identity Synchronization for Windows cannot log messages from that machine.
You can use the following procedure to enable audit logging on your Windows NT machine:
- From the Windows NT Start menu, select Programs > Administrative Tools > User Manager for Domains.
- When the User Manager dialog box is displayed, select Policies > Audit from the menu bar.
The Audit Policy dialog box is displayed.
- Enable the Audit These Events button and then enable the Success and Failure boxes.
- Click OK to close the dialog box.
These settings will remain in effect until you change them again.