You can obtain a log bundle from the cloud proxy.
- The cloudassembly-sddc-agent is not present, fails to start, or is not the latest version.
- The connection is lost, as evidenced by messaging stating that the cloud proxy connection has been lost.
- The endpoint connection can't be validated, as evidenced by any of the following messages:
- Agent not found
- Cannot get proxy with id .....
- Session doesn't exist .....
- The enumeration fails, as evidenced by the following or similar message:
The connection with vAPI endpoint cannot be established. Please make sure the vAPI endpoint is running in the vCenter. Unexpected character ('<' (code 60)): expected a valid value (number, String, array, object, 'true', 'false' or 'null').
- The enumeration never finishes.
- A VM provisioning action fails.
- A VM Day 2 post-provisioning action fails.
- Verify that you have cloud administrator credentials. See Credentials required for working with cloud accounts in VMware Aria Automation.
- Verify that you have the cloud administrator user role. See What are the VMware Aria Automation user roles.
- Verify that you have an Amazon Web Services account, and administrator credentials to access that account.
- Generate the log bundle by using either of the following two procedures:
- User interface method
Use this method to view the logs. However, if you want to send the log bundle to VMware for help, use the command line method instead.
- In Automation Assembler, select .
- Select the proxy VA that is associated with the cloud account in question and click Upload Support Bundle.
The logs are uploaded to a secure Amazon AWS S3 site and tagged with the cloud proxy ID. Be sure to record the cloud proxy ID so that you can use it to find the logs in AWS S3.
The log bundle may take a few minutes to generate.
- Command line method
Use this method when sending logs to VMware for help with troubleshooting your issues.
- Open a command prompt window and SSH into the cloud proxy VA.
- Run the following command:
The zipped log file bundle is created in the /root/log-bundle-directory folder.
- Unzip the log_bundle.tar.gz file to display the following file structure:
. ├── data1 │ ├── blueprint-agent-logs │ ├── cmx-agent-logs │ ├── codestream-agent-logs │ ├── dclogs │ ├── log-forwarder │ ├── lost+found │ ├── proxylogs │ ├── sddc-agent-logs │ └── vro-agent-logs ├── files-list.txt ├── log │ ├── cimple │ ├── firstboot │ ├── lighttpd │ ├── network-proxy │ ├── sfcb │ ├── subsequentboot │ └── vami ├── provider-runtime.xml ├── proxy.properties └── shared └── ssl.keystore
The vCenter, NSX, and VMware Cloud on AWS logs are in the sddc-agent-logs folder.
- User interface method