vRealize Operation Troubleshooting
I decided to share some common troubleshooting steps I’ve had to do with vRealize Operations at customers.
Troubleshooting steps Enabling SSH on the appliance:
- Log in to the vRealize Operations Manager (formerly known as VMware vCenter Operations Manager (vApp)) virtual machine console as root using ALT-F1.Note: By default there is no root password configured.
- Start the SSH service by running the command:service sshd start
- To configure SSH to start automatically run this command:chkconfig sshd on
Troubleshooting tip #1: Pairing the vRealize Operations Management for Horizon Agent fails.
- Uninstall V4H agent on connection broker
- Delete/Rename ‘C:\Programdata\vmware\vRealize Operations for Horizon’
- Delete registry key:
Follow the following KB and install the hotfix on the broker. Horizon 6.4 Hot Fix Download: https://www.dropbox.com/s/n9virk2iuc70k7a/VMware-v4vbrokeragent-x86_64-6.4.0-5099242.zip?dl=0 Additionally, check the following KB 2140844 ‘VMware vRealize Operations Manager for Horizon 6.2 Broker Agent fails to pair with the Horizon adapter’ link: https://kb.vmware.com/s/article/2140844 Troubleshooting tip #2:
- On the Connection Server on which the V4H Agent is installed, move this file to another directory:install_directory\VMware\VMware View\Server\sslgateway\conf\locked.properties
- Restart the View Connection Server service or security server service for the changes to take effect.
- Restart the V4H Broker Agent service.
Troubleshooting tip #3: There is a rare chance the appliance log partition filled up. To see if the log partition is filled execute ‘df -h’ at the command-line Before executing this next step, verify no historical data needs to be saved because this will wipe it. On the appliances in question execute: find /storage/log/ -mount -type f -iname “*log*” -exec truncate -cs 0 {} \; This will empty the log partition.
