Troubleshooting the Watchdog Process and Core Components

Use the information in this section to troubleshoot the Identity Synchronization for Windows Watchdog
process and core components. The Watchdog process launches and monitors the
central logger, system manager, and connectors. The core components include
the configuration directory, command-line utilities, system manager, and the
central logger. The information is provided for each operating system as follows:

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 com.sun.directory.wps

The following table describes the processes that should be running.

Table 7–2 Identity Synchronization for Windows Processes

Java Process Class Name

Component

When it Should be Present

com.sun.directory.wps.watchdog.server.WatchDog

Watchdog Process

Always

com.sun.directory.wps.centrallogger.CentralLoggerManager

Central Logger

Only where Core is installed

com.sun.directory.wps.manager.SystemManager

System Manager

Only where Core is installed

com.sun.directory.wps.controller.AgentHarness

Connector

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 WatchList.properties 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:

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

Troubleshooting Processes 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 must be started.

If the service is started, then use the Task Manager to verify that
the Watchdog process, pswwatchdog.exe, is running and that
the expected number of java.exe processes are running.
You should have one java.exe process for each connector
installed on the machine. If the core component is installed, you should also
have a java.exe process for each of the following:

One for the message queue broker

One for the system manager

One for the central logger

Note –

Other active Java processes, such as the Directory Service Control
Center, may be running.

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

Examining the WatchList.properties File

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 the core component is installed, the WatchList.properties file includes entries for the Central Logger and the System Manager
as follows:

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

On machines where the connectors are installed, the WatchList.properties file includes a separate entry for each connector as follows. The process.name property is the connector ID.

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

If the entries in the WatchList.properties file and
the actively running processes are not the same, then restart the Identity Synchronization for Windows daemon
or service.

If the WatchList.properties file contains too few
a number of entries, for example only one connector entry even though two
were installed, then examine the installation logs for possible installation
failures. The location of the installation logs vary depending on your operating
system as follows:

On Solaris, installation logs are written to /opt/SUNWisw

On Linux, installation logs are written to /var/opt/sun/isw/logs

On Windows, 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. The following procedures
describes how to view hidden folders.