Troubleshooting Components

Use the information in this section to troubleshoot components. The information is organized as follows:

• On Solaris

• On Linux

• On Windows

• Examining WatchList.properties

On Solaris

The command /usr/ucb/ps -auxww | grep com.sun.directory.wps will list all of the Identity Synchronization for Windows processes running. This table shows which processes should be running.

If the expected number of processes are not running, then issue the following commands to restart all Identity Synchronization for Windows processes.

# /etc/init.d/isw stop
# /etc/init.d/isw start

If the WatchDog process is running, but the expected number of java.exe processes are not running, then see the “Examining WatchList.properties” section to verify that all components were installed properly.

Like other system components, the Sun Java System Directory Server Plug-in sends log records over the bus that are managed by the central logger for end-user viewing. However, the Plug-in also logs some messages that may not show up over the bus (for instance when the subcomponent cannot contact the connector). In this case the log messages only show up in the Plug-in’s logs directory on the file system, which should look something like the following:

serverroot/isw-hostname/logs/SUBCid

Because the Plug-in runs with the Directory Server process, there could potentially be a problem for the Plug-in’s ability to write into its logs directory. This happens if the directory server runs as a different user than the owner of the logs directory. In this case, it may be necessary to give the Plug-in permission explicitly by changing the directories permission or owner using native operating system commands.

On Linux

The command /usr/ucb/ps -auxww | grep com.sun.directory.wps will list all of the Identity Synchronization for Windows processes running. This table shows which processes should be running.

If the expected number of processes are not running, then issue the following commands to restart all Identity Synchronization for Windows processes.

# /etc/init.d/isw stop
# /etc/init.d/isw start

If the WatchDog process is running, but the expected number of java.exe processes are not running, then see the “Examining WatchList.properties” section to verify that all components were installed properly.

Like other system components, the Sun Java System Directory Server Plug-in sends log records over the bus that are managed by the central logger for end-user viewing. However, the Plug-in also logs some messages that may not show up over the bus (for instance when the subcomponent cannot contact the connector). In this case the log messages only show up in the Plug-in’s logs directory on the file system, which should look something like the following:

serverroot/isw/logs/SUBC 

Because the Plug-in runs with the Directory Server process, there could potentially be a problem for the Plug-in’s ability to write into its logs directory. This happens if the directory server runs as a different user than the owner of the logs directory. In this case, it may be necessary to give the Plug-in permission explicitly by changing the directories permission or owner using native operating system commands.

On Windows

Using the Service control panel, check that the “Sun Java System Identity Synchronization for Windows service is started. If it is not started, then Identity Synchronization for Windows is not running on that machine, and should be started. If the service is started, then verify using the Task Manager that pswwatchdog.exe (the Watchdog process) is running and that the expected number of java.exe processes are running:

• One for the Message Queue broker only if the Core is installed

• One for the System Manager only if the Core is installed

• One for the Central Logger only if the Core is installed

• One for each Connector installed on that machine

There might be other active java processes, such as the Directory Server Console. If pswwatchdog.exe is not running, then restart the “Sun Java System Identity Synchronization for Windows” service. If it is running but the expected number of java.exe processes are not running, then see Examining WatchList.properties to verify that all components were installed properly.

Examining WatchList.properties

On each machine where a Identity Synchronization for Windows component is installed, the isw-machine_name/resources/WatchList.properties file enumerates the components that should run on that machine. The process.name[n] properties name the components that should be running.

On machines where Core is installed, WatchList.properties will include entries for the Central Logger and System Manager:

process.name[1]=Central Logger
process.name[2]=System Manager

On machines where connectors are installed, WatchList.properties will include a separate entry for each connector. The process.name property is the connector ID:

process.name[3]=CNN100
process.name[4]=CNN101

If there is a mismatch between the entries in WatchList.properties and the actively running processes, then restart the Identity Synchronization for Windows daemon or service.

If there are fewer than expected entries in WatchList.properties (e.g. only one connector entry even though two were installed), then examine the installation logs for possible installation failures.

• On Solaris systems: Installation logs are written to /opt/SUNWisw

• On Linux Systems: Installation logs are written to /var/opt/sun/isw/logs

• On Windows systems: Installation logs are written to the %TEMP% directory, which is a subdirectory of the Local Settings folder located under

  C:\Documents and Settings\Administrator

On some Windows systems (such as Windows 2000 Advanced Server), the Local Settings folder is a hidden folder.

To View Hidden Folders and the Temp subdirectory

1. Open your Windows Explorer and select Tools -> Folder Options from the menu bar.

2. When the Folder Options dialog box is displayed, select the View tab and enable the Show Hidden Files option.