Sun Directory Server Enterprise Edition 7.0 Troubleshooting Guide

Troubleshooting Processes on Solaris or Linux

The following command lists all of the Identity Synchronization for Windows processes that are currently running:

# /usr/ucb/ps -auxww | grep

The following table describes the processes that should be running.

Table 7–2 Identity Synchronization for Windows Processes

Java Process Class Name 


When it Should be Present

Watchdog Process 


Central Logger 

Only where Core is installed

System Manager 

Only where Core is installed


One for each connector installed 

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 verify that all components were installed properly. For information about verifying the components, see Examining the File.

Like other system components, the 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, such as messages that are written when the subcomponent cannot contact the connector. These log messages only appear in the plug-in’s logs directory on the file system, which should look something like the following:


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. If the Directory Server process runs as a different user, give the plug-in explicit permissions using native operating system commands.