VMware vRealize Automation 7.x Troubleshooting Infra issues

Troubleshooting Infra Issues in vRA 7.x

 

 

To manually troubleshoot vRA issues, we must know what all things we need to check.

 

1). In the vRA portal one should check the status of all the services whether the status is registered, fail or blank.

 

https://vRAserver_name:5480

 

If the status is registered than all good but if it is showing failed then it seems something is wrong with that service.

If the status of service is blank it means that the service is responding but not correctly.



XML link to check why services are not running are as follows:

 

https://vRA/component-registry/services/status/current?page=1&limit=50

 

2) If in the vra page one is giving Error 503 then please check below things to isolate that:

-->IIS Pools

-->SQL DB Connectivity

-->Certificate Issues

-->Service Account Issues

-->Service Dependency

 

3). Service which need to checked to monitor load balancing is "shell-ui-app" and it can be checked from below path:

 

https://FQDN-VRA-VA/vcac/services/API/status

 

4). To validate if the VMware identity manager is working go to the below link and check at end it should state

 "All ok","true"

 

5). To verify if the vRO (blueprint creator)  is working fine), go to link

 

https://FQDN-VRA-VA/vco/api/healthstatus

 

6). To validate IAAS server is successful, below services should be running:

-->Web server

-->Model Manager web

-->Model Manager Data

-->Manager Server

-->Distributed execution manager - orchestrator

-->Distributed execution manager - worker

 

7). Also check the webpools status in IAAS webserver

-->Repository

-->vCAC

-->WAPI

 

8). Now one can do some portal checks from vrA Settings like:



-->Host settings should show proper name and if cluster then the cluster virtual ip

-->Check SSO is connected

-->Check valid license is there

-->Check Rabbit MQ is running and port 5671 used

-->Check cluster connection status is connected

 

After checking all the above infra components, now one should know where the logs are for detailed analysis. Location of the log files are as follows:

 

Server

Log location

Log Purpose

vRealize Automation Appliance

/storage/log/vmware/vcac/vcac-config.log

vRealize Automation Appliance configuration logs

vRealize Automation Appliance

/storage/log/vmware/vcac/telemetry.log

vRealize Automation telemetry log

vRealize Automation Appliance

/storage/log/vmware/vco/configuration/catalina.out

vRealize Orchestrator Configuration log

vRealize Automation Appliance

/storage/log/vmware/vco/configuration/controlcenter.log

vRealize Orchestrator Control Center log

vRealize Automation Appliance

/storage/log/vmware/vco/app-server/server.log

vRealize Orchestrator Server log

vRealize Automation Appliance

/storage/log/vmware/horizon/connector.log

vIDM connector request log

vRealize Automation Appliance

/storage/log/vmware/horizon/catalina.log

vIDM Server log

vRealize Automation Appliance

/storage/log/vmware/horizon/horizon.log

vIDM Server log

vRealize Automation Appliance

/storage/log/vmware/vcac/catalina.out

vRealize Automation Server log

vRealize Automation Appliance

/var/log/vmware/horizon/horizon.log

vRA 7.2 horizon log

vRealize Automation Appliance

/var/log/vmware/horizon/connector.log

vRA 7.2 connector request log

vRealize Automation Appliance

/storage/db/pgdata/pg_log/postgresql.csv

vPostgres Log

vRealize Automation Appliance

/opt/vmware/var/log/vami/vami.log

Appliance Management and upgrade logs

IaaS Windows Server

C:\Program Files (x86)\VMware\vCAC\Agents\agent_name\logs\file

Plug-in logs example: CPI61, nsx, VC50, VC51Agent, VC51TPM, vc51withTPM, VC55Agent, vc55u, VDIAgent

IaaS Windows Server

C:\Program Files (x86)\VMware\vCAC\Distributed Execution Manager\DEMOR\Logs\DEMOR_All

Distributed Execution Manager logs

IaaS Windows Server

C:\Program Files (x86)\VMware\vCAC\Distributed Execution Manager\DEMWR\Logs\DEMWR_All

Distributed Execution Worker logs

IaaS Windows Server

C:\Program Files (x86)\VMware\vCAC\Server\Logs

Manager Service logs

IaaS Windows Server

C:\Program Files (x86)\VMware\vCAC\Server\ConfigTool\Log\vCACConfiguration-date

Repository Configuration logs

IaaS Windows Server

C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Logs\nothing_today

IIS Access logs (usually empty, but can be expected)

IaaS Windows Server

C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Web\Logs\Repository

Repository logs

IaaS Windows Server

C:\Program Files (x86)\VMware\vCAC\Server\Website\Logs\Web_Admin_All

Web Admin logs

IaaS Windows Server

C:\inetpub\logs

IIS logs

IaaS Windows Server

C:\Program Files (x86)\VMware\vCAC\Web API\Logs\Elmah

WAPI website logs (6.2.x)

IaaS Windows Server

C:\Program Files (x86)\VMware\vCAC\Management Agent\Logs

Management Agent logs

Windows Guest Agent Connection Log

C:\VRMGuestAgent\axis2\logs\gugent-axis.log

Connection logs showing status of connection to vRA Management Service server

Windows Guest Agent Log

C:\VRMGuestAgent\GuestAgent.log

All Guest Agent actions (post successful connection)

Linux Guest Agent Connection Log

/usr/share/gugent/axis2/logs/gugent-axis.log

Connection logs showing status of connection to vRA Management Service server

Linux Guest Agent Log

/usr/share/gugent/GuestAgent.log

All Guest Agent actions (post successful connection)

Windows Application Services Agent logs

c:\opt\vmware-appdirector\agent\logs\agent_bootstrap.log

Windows logs for the Software Provisioning agent.

Linux Application Services Agent logs

/opt/vmware-appdirector/agent/logs/agent_bootstrap.log

Linux logs for the Software Provisioning agent.

Linux Software Agent Logs

/opt/vmware-appdirector/agent/logs/darwin-agent<date>.log

Linux logs for the Software agent.

Windows Software Agent Logs

c:\opt\vmware-appdirector\agent\logs\darwin-agent<date>.log

Windows logs for Software agent

 

 

References:

https://kb.vmware.com/s/article/2141175

 

https://docs.vmware.com/en/VMware-Validated-Design/4.2/com.vmware.vvd.sddc-design.doc/GUID-BFD7CD88-7B39-4938-A41A-46227B280A1A.html

Comments

Post a Comment

Popular posts from this blog

Troubleshooting NonVMwareDevice Filtering in VMware SRM using Dell EMC SRDF SRA.

    Troubleshooting NonVMwareDevice Filtering in VMware SRM using Dell EMC SRDF SRA. Problem description:  While running device discovery in VMware SRM while using DELL EMC SRDF SRA, it shows all the replicated devices not just the VMware devices.     In this post, I will like to highlight about my experience which I had faced while configuring VMware SRM with DELL EMC SRDF SRA.   For those who are not aware what these products are, I will like to take some time in giving a brief indroduction about the same.   VMware SRM: VMware provides the VMware Site Recovery Manager (SRM) as part of its vSphere suite, which lets you automate backups and orchestrate the recovery of entire data centers from a disaster recovery site. SRM can be used both on-premises and as a Disaster Recovery as a Service (DRaaS).   Dell EMC SRDF SRA:   SRDF: The Symmetrix Remote Data Facility (SRDF) is a family of software ...
Read more

Replacing NSX-T Certificate with Custom Certificate

Image
                                Replacing NSX-T Certificate with Custom Certificate.   As part of best practice, it is always recommended to replace VMware self-signed Platform certificates with your organization's CA signed certificate. To do the same we need to create a Certificate Signing Request for the NSX Manager. NSX-T Data Center deployment install VMware self-signed certificated by default. The same can be checked by navigating to System > Certificates to view the platform certificates created by the system. By default, these are self-signed X.509 RSA 2048/SHA256 certificates for internal communication within NSX-T Data Center and for external authentication when NSX Manager is accessed using APIs or the UI.   To replace the VMware self-signed certificate with the custom cert there are four main steps:   1). Generate CSR. ...
Read more