Orchestrator provides a watchdog utility that checks whether the Orchestrator server service is running. The utility pings the Orchestrator server service periodically, and restarts it if a certain timeout period is exceeded.
By default, the watchdog utility is deactivated.
You can activate the service watchdog utility by setting the timeout period for the service's response to the ping from the utility. You can set the timeout period for the response from the Orchestrator server service in the wrapper.conf configuration file. The wrapper.conf file defines the wrapping of the Orchestrator server in the host system.
Prerequisites
The Orchestrator server must be running as a Windows service.
Procedure
1 | Log in as an administrator to the machine on which the Orchestrator server is installed. |
2 | Navigate to the wrapper.conf configuration file and open the file in a text editor.
The wrapper configuration file is in the following location:
install_directory/app-server/bin/wrapper.conf
|
3 | Locate the -wrapper.ping.timeout parameter in the wrapper.conf file, or add it to the file if it does not exist. |
4 | Set the number of seconds to allow between a ping from the watchdog utility and the response from the service.
The default timeout is 0 seconds, which means that the utility is deactivated.
For example, you can increase the timeout period to 30 seconds by setting the parameter as follows:
-wrapper.ping.timeout=30
|
5 | Save and close the wrapper.conf file. |
6 | Log in to the Orchestrator configuration interface as vmware. |
7 | On the Startup Options
tab, click Restart Service
to restart the Orchestrator server. |
You activated the Orchestrator watchdog utility by setting the timeout.