1.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.

Note


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 their resources (such as sockets). On rare occasions, restarting the Director too soon after stopping it can 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.


Tru64 UNIX

At a shell prompt, enter:

/usr/sbin/desta stop

On TruClusters, you can run the /usr/sbin/webes_install_update program and choose the Stop WEBES Director option to stop the Director on either all the nodes in the cluster or a selected group of nodes that you choose.

HP-UX

At a shell prompt, enter:

/usr/sbin/desta stop

Linux

At a shell prompt, enter:

/usr/sbin/desta stop

OpenVMS

At a prompt, enter:

desta stop

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

Windows

Stop the Director by stopping the DESTA_Service Windows service. You can use any of the following methods:

A Stop Director icon appears in the Task Bar, then disappears when the Director's shutdown has completed.
net stop DESTA_Service

Using the desta stop command on Windows systems is unsupported. Stopping the director this way is not recommended because:

On Windows, the desta start/stop functionality is only intended to be used as a tool for investigating WEBES operational problems. If the Director is started with desta start, it must be stopped with desta stop.