3.5  Troubleshooting an Unresponsive Director

If one of the WEBES components is not responding or giving an error, it may be that the Director process is not responding. To correct this problem, use one of the following procedures.

3.5.1  Windows

Stop the Director either from the Start | Programs menu, or by issuing the command: net stop desta_service. Check the Windows Task Manager for the following WEBES processes:

If they end within 2 minutes, the Director can be restarted either from the Start | Programs menu, or by issuing the command: net start desta_service and then waiting approximately one minute for WEBES to set up its processes before running a WEBES tool.

If the Director does not stop in approximately two minutes the processes may be hung. Select any suspect WEBES process from the list above and press the End Process button, which should remove the entry. Do not end java.exe processes that are not associated with the WEBES Director. To identify likely WEBES java.exe processes, look for a "Low" base priority in the Task Manager's Process list. If you do not see the Base Priority column, choose View | Select Columns from the Task Manager pulldown menu and check the box for Base Priority.

If you are presented with an error message that you do not have privileges to end a process, you must restart the Windows system. Before restarting, follow the post-installation steps in the WEBES Installation Guide to assign yourself the privileges necessary to kill WEBES processes in the future. The Director will be restarted automatically during the restart phase.

3.5.2  Tru64 UNIX

Issue the command: desta stop. If the Director does not stop in approximately two minutes the process may be hung. Look for the WEBES java processes in the ps list:

ps ugxww | grep /usr/opt/hp/svctools | grep -v grep

Processes containing any of the following strings may appear, all of which are WEBES processes:

Then, issue kill commands to stop them. Finally, as the root user, issue the command: desta start and wait approximately one minute for WEBES to set up its processes before running a WEBES component.

3.5.3  HP-UX

Issue the command: desta stop. If the Director does not stop in approximately two minutes the process may be hung. Look for the WEBES java processes in the ps list:

ps -eflx | grep /opt/hp/svctools | grep -v grep

Processes containing any of the following strings may appear, all of which are WEBES processes:

Then, issue kill commands to stop them. Finally, as the root user, issue the command: desta start and wait approximately one minute for WEBES to set up its processes before running a WEBES component.

3.5.4  Linux

Issue the command: desta stop. If the Director does not stop in approximately two minutes the process may be hung. Look for the WEBES java processes in the ps list:

ps ugxww | grep /usr/opt/hp/svctools | grep -v grep

Processes containing any of the following strings may appear, all of which are WEBES processes:

Then, issue kill commands to stop them. Finally, as the root user, issue the command: desta start and wait approximately one minute for WEBES to set up its processes before running a WEBES component.

3.5.5  OpenVMS

Issue the command: desta stop. If the Director does not stop in approximately two minutes the process may be hung. Look in the SHOW SYSTEM output for any of the following WEBES processes:

Issue the STOP PROC /ID= command to kill the process ID associated with those processes. Then issue the command: desta start and wait approximately one minute for WEBES to set up its processes before running a WEBES component.