3.8  Stopping the Director

Under normal operation, you should not need to stop the Director. However, if circumstances require you to stop the Director, follow the instructions for your operating system.

Wait Before Restarting


After a "desta stop" or "net stop desta_service" command completes, the operating system sometimes requires a few more seconds to stop all WEBES-related processes and release resources (such as sockets). On rare occasions, restarting the Director too soon after stopping it can result in errors in the Director log file, and the Director also may fail to restart.

To avoid this issue, wait 10 more seconds before restarting the Director, once the "desta stop" or "net stop desta_service" command completes.


HP-UX

At a shell prompt, enter:

# /usr/sbin/desta stop

Linux

At a shell prompt, enter:

# /usr/sbin/desta stop

OpenVMS

At the OpenVMS command line prompt, enter:

$ desta stop

On OpenVMS clusters, you can uses the SYSMAN utility to issue the do desta stop command on either all the nodes in the cluster or a specific group of nodes that you choose.

Windows

To stop the Director, stop the DESTA_Service using one of the following methods:

A Stop Director icon appears in the Task Bar, then disappears when the Director shutdown has completed.
C:\>net stop desta_service

Caution


The desta stop command on Windows is unsupported. The command may eventually stop the Director, but it also may cause errors.

The Director may not stop completely, leaving running processes behind.

Error messages may appear in either the logs for the Director process or in the desta stop output.

The Director may take longer to stop than it normally would using one of the recommended methods, and it may continue to run for a time even after the desta stop process has finished.

On Windows, the desta start/stop commands are used only for troubleshooting, and if the Director is started with desta start, it must be stopped with desta stop.