Search the VMware Knowledge Base (KB)
View by Article ID

vRA 7.0.x Manager Service extensibility callouts to Event Broker fails (2145735)

  • 0 Ratings
Language Editions

Symptoms

  • Timeout while waiting for Event Broker response even though workflows are completing in vRealize Orchestrator.
  • In the Catalina.out log file, you see entries similar to

    WARN {} [SDKFinder] convertToResult() --> Finder 'vCAC:VCACHost' : unable to invoke read method : 'authenticationType'
    public String getAuthenticationType() {    return connection.getConnectionInfo().getAuthentication().getType();

  • In the Manager log, you see entries similar to:

    sendEBSMessage19(workflow=eb68d678-c64a-461f-ba6d-d2366eeda6f9) Error in state VMPSMasterWorkflow32.MachineProvisioned phase PRE event (queue = 421e4c3c-78b6-4fa9-93ad-737ed89a667c): Timed out while waiting for Event Broker response

  • This issue occurs only in High Availability environment.

Cause

This issue occurs when the RabbitMQ cluster internal to the vRealize Automation appliances is broken.
 
IaaS gets the events from the RabbitMQ cluster. If the RabbitMQ cluster is broken, IaaS does not get the event within expected time (30 minutes) and the machine provisioning slows or eventually fails. The event times out while waiting for the Event Broker response even when workflows are completing in vRealize Orchestrator.

Resolution

This issue is resolved in VMware vRealize Automation 7.1, available at VMware Downloads .
 
To resolve this issue in VMware vRealize Automation 7.0.x:
  1. Connect to the vRealize Automation Appliance using the SSH.
  2. Run this command:

    rabbitmqctl cluster_status

    For example:

    When you run the rabbitmqctl cluster_status command, you see output similar to:

    Cluster status of node 'rabbit@cava-test-va2' ...
    [{nodes,[{disc,['rabbit@cava-test-va1','rabbit@cava-test-va2']}]},
    {running_nodes,['rabbit@cava-test-va1','rabbit@cava-test-va2']},
    {cluster_name,<<"
    rabbit@cava-test-va1.sqa.local ">>},
    {partitions,[]}]

    Where cava-test-va1 and cava-test-va2 are the vRealize Automation nodes running.

  3. Validate that all appliances are appearing in running_nodes list.

    For example, cava-test-va1 and cava-test-va2.

  4. If an appliance is missing in the running_nodes list, you must rebuild the RabbitMQ cluster.

  5. Verify that all vRealize Automation appliances are connected through the Fully Qualified Domain Name (FQDN).

  6. Verify that host short names resolve on all vRealize Automation appliances in the cluster by running nslookup vra_host_shortname.

    For example, nsookup cava-test-va1.

    Note: If you cannot connect appliances by FQDN and short name, resolve DNS or Network issues.

  7. On the Virtual Appliance Management Interface page (VAMI Port 5480), go to vRA Settings  > Messaging > Press Reset.

    Note: RabbitMQ reset should be done on all vRealize Automation appliances of the cluster.

  8. Verify that all services are started and connect the Appliances.

    1. On the primary Appliance (Appliance with master database):

      1. Log in to the Appliance using SSH.
      2. Run the command

        service vcac-server restart

      3. Verify that all services are started.

    2. On the secondary Appliances:

      1. Log in to VAMI page (Port 5480).
      2. Navigate to  vRA Settings > Cluster.
      3. Join to the Primary appliance.

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 0 Ratings
Actions
KB: