1.7  Starting the Director

The Director is automatically started during system startup. Under normal operation, you should not need to manually start the Director. However, if circumstances require it, you can manually start the Director by following 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 start

On TruClusters, you can run the /usr/sbin/webes_install_update program and choose the Start WEBES Director option to start 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 start

Linux

At a shell prompt, enter:

/usr/sbin/desta start

OpenVMS

At the OpenVMS command line prompt, enter:

desta start

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

Windows

To start the WEBES Director, start the DESTA_Service using one of the following methods:

net start DESTA_Service

Using the desta start command on a Windows system is unsupported and not recommended. While the command may start the Director, it will also generate error messages. Starting 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.