Datacenter outages and application restoration can lead to corrupted files.
Manually changing application settings with vcac-vami and or vcac-config commands or manual manipulating configuration files can lead to unexpected product behavior.
Hostname changes or certificate changes can lead to scenarios where these instructions maybe required.
Resolution
This is a known issue affected vRealize Orchestrator 7.x. Currently there is no resolution.
See the workaround below for further details.
Workaround:
Open an SSH session to the affected vRO node
Run the following commands
cd /var/lib/vco/app-server/conf
touch update
chown vco:vco update
service vco-configurator restart
Attempt to access vRO control center on the the node by navigating to https://vRO-vRAFQDN:8283/vco-controlcenter