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.
About this task
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 for the Windows installation and setenv.sh file for the Orchestrator Appliance. The files define the wrapping of the Orchestrator server in the host system.
Verify that the Orchestrator server is running as a Windows service.
- Log in as an administrator to the machine on which the Orchestrator server is installed.
- Navigate to the configuration file and open the file in a text editor.
If you installed Orchestrator with the vCenter Server installer
Go to install_directory\VMware\Infrastructure\Orchestrator\app-server\bin.
If you installed the standalone version of Orchestrator
Go to install_directory\VMware\Orchestrator\app-server\bin.
If you deployed the Orchestrator Appliance
Go to usr/lib/vco/app-server/bin.
- Locate the -wrapper.ping.timeout parameter in the wrapper.conf file, or add it to the file if it does not exist.
- 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:
- Save and close the wrapper.conf file.
- Log in to the Orchestrator configuration interface as vmware.
- On the Startup Options tab, click Restart Service to restart the Orchestrator server.
You activated the Orchestrator watchdog utility by setting the timeout.