• Call Toll Free: 1-855-909-3300

How to Troubleshoot VMware vCloud Automation Center Issues?

Troubleshooting a VMware Automation Center, now known as vRealize Automation, might not go smoothly. There are several key areas to look over when troubleshooting.

VMware vCloud Automation Center now known as vRealize Automation, is designed to help businesses manage their cloud and various data center resources. But getting through the troubleshoot vmware cloud automation process unscathed can be challenging when all the disparate components aren’t together.

Check on the components:

With vCAC, it is very important that you are using the correct versions of all the components. Using the wrong version of SSO, database server or other modules can lead to broken features or to erratic behavior. Check the vCAC Support Matrix document in the documentation section at VMware’s site.

Before diving into the troubleshooting steps of vmware cloud automation, have a look at the components that are involved. A minimal deployment contains these machines and services:

  • Identity Applianceor existing vSphere SSO
  • vCAC appliance
  • Windows IAAS Server
  • SQL Database Server
  • Active Directory or OpenLDAP

Another important thing to know about these components is which one is taking care of running what.

Login problems:

These areas should be open to troubleshoot vmware cloud automation to work correctly and not only the authentication process.

  • DNS:Make sure all components have a fully qualified domain name server and are registered in your DNS-environment.
  • Time synchronization:Verify that all servers in vmware cloud automation use the same time source and that they are actively synchronizing with that time source.
  • Certificates:All servers should have valid SSL certificates.

The Web portal layout:

When the left side loads and the right side gives an HTTP Error 404, look at your Windows IAAS server and verify that IIS is running.

Verify the services:

The services tab will show the registered services. One exception is the sts-service, which is never listed as registered. When any of the services is not registered or reports a status of FAILED, you can dive into the problem or take a shortcut and restart the services. There is no need to restart the entire Linux appliance. Unfortunately, there isn’t any feature to restart individual services, so you will have to restart the entire server. Access the appliance with Secure Socket Shell or login to the local console through the vSphere Web Client, and on the command line execute the following command:

service vcac-server restart

This will stop and restart the server.

It may take up to 15 minutes before the services appear in the Web management interface. If you want to trace what’s happening, check the messages log file with this command:

tail -f /var/log/messages

This shows the end of the messages log file and will print any new line that is added to the file on the screen. After a while, all services should be registered. If not, it’s time to investigate what’s wrong with that service.

When one of the services is not registered or has failed, access your vmware cloud automation appliance to look at the status of that service.

Check other locations for the troubleshooting of vmware cloud automation:

When all the components appear to be online or when you can’t find any errors or warnings, then the next step is to look into the log files.

If a DEM Worker is offline — and it’s the only DEM worker — none of the workflows will process. If you have multiple DEM Workers, your workflows might still process, but it might take longer for them to finish. If you have a large number of pending workflows, end users might start complaining about delays with requests.

Leave a Reply

Techarex NetWorks Products