Unable to deploy machines using vRA due to vRA and vRO connectivity issue
search cancel

Unable to deploy machines using vRA due to vRA and vRO connectivity issue

book

Article ID: 343200

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Symptoms:
  • vRealize Automation and vRealize Orchestrator communication broken.
  • Unable to provision virtual machines from vRealize Automation.
  • When you test connectivity in vRealize Orchestrator server configuration, you see the error:

    Unable to connect on port
     
  • In catalina.out log, you see the error

    Unable to establish a connection to vCenter Orchestrator server.


Environment

VMware vRealize Orchestrator 7.0.x
VMware vRealize Orchestrator 7.5.x
VMware vRealize Automation 7.0.x

Cause

This issue occurs when the port 1514 is blocked by excessive remote logging between vRealize Orchestrator and Syslog server (For Ex: LogInsight, RHEL 7.2 rsyslog server) that causes vRealize Orchestrator to fail. This happens when remote logging and debug logging level are enabled on vRealize Orchestrator.

Resolution

To resolve the issue, ensure the port 1514 be open by disabling remote logging and move logging level to warning. For more information, see the Ports and External Interfaces that the Log Insight Virtual Appliance Uses section in the VMware vRealize Log Insight Security Guide.