The vRealize Automation appliance management interface can help you resolve registration problems with vRealize Automation component services.

Problem

Under normal operation, all vRealize Automation component services must be unique and in a REGISTERED state. Any other set of conditions might cause vRealize Automation to behave unpredictably.

Cause

The following are examples of problems that might occur with vRealize Automation component services.

  • A service has become inactive.

  • Server settings caused a service to be in a state other than REGISTERED.

  • A dependency on another service caused a service to be in a state other than REGISTERED.

  • There are duplicate services.

Results

Unregister and, where needed, re-register component services that appear to have problems.

  1. Log in to the vRealize Automation appliance management interface as root.

    https://vrealize-automation-appliance-FQDN:5480

  2. Click Services.

  3. In the list of services, select a service that is a duplicate, is not in the correct state, or has other problems.

  4. At the upper right, click Unregister.

  5. To have vRealize Automation re-register the service, log in to a console session on the vRealize Automation appliance as root, and restart vRealize Automation by entering the following command.

    service vcac-server restart

    If there are services associated with the embedded vRealize Orchestrator instance, enter the following additional command.

    service vco-restart restart

  6. To re-register any services associated with an external system, such as an external vRealize Orchestrator instance, log in to the external system and restart the services there.