Follow the steps given below to capture OVFTool logs:
- Open vCD UI in browser by adding ?debug=true at the end. For example see URL: https://xx.xxx.xxx.xx/cloud/?debug=true
- Now reproduce the issue
- Collect the client logs from the client machine. If client machine is windows, then the logs will be at following location:
There are a couple items that can be easily missed in the Documentation for upgrading the VCSA in version 6. The documentation is located HERE.
Here is a quick step by step to help summarize:
There are a ton of blogs out there with complex queries and actions you can perform when your transaction logs are full and the vCD Web Interface fails with an error like:
.CellNotActiveException: Cell is not active
Well, I decided to make it simple for those who just want to get your environment back up and running ASAP.
Just wanted to give you a heads up that if you or friends/family are looking to buy a new computer you may want to steer clear of Lenovo. They are installing a trusted certificate so they can see (MiTM) all your traffic so they can target you with ads better. But they are doing this for every site you visit, including your bank so who knows what information they can see.
I found it quite risky to connect to a vCloud instance as a SysAdmin and perform calls to a specific Org and ensure not to touch other orgs by a simple typo in my commands.
Use the following command to connect via PowerCLi direct to an org in vCD.
Connect-CIServer -Org WWW -Server XXX -Username YYY -password ‘ZZZ’