VMware HealthAnalyzer Troubleshooting Guide v4.0 Page 1 of 14
Version History Date Ver. Author Description Reviewers 17 April 2015 V1.0 VMware Initial content 21 Mar 2016 V2.0 VMware Update 29 Dec 2016 V3.0 VMware Add troubleshooting steps for OVA start-up 15 Jun 2017 V4.0 VMware Increase the size of the OVA root partition 2016 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. This product is covered by one or more patents listed at http://www.vmware.com/download/patents.html. VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies. Page 2 of 14
Contents Version History... 2 1. Error during vsphere collection vcenter user account permission issue for storage profile access... 4 2. Error during vsphere collection vcenter user account permission issue for iscsi access... 5 3. Error during vsphere collection Disconnected ESX hosts issue... 6 4. Error during Horizon View Desktop collection Unresolved issue... 7 5. Error while accessing Web UI from a browser network issue... 8 6. Error when starting Java version of VHA... 9 7. vcenter Collection fails during connection vcenter certificate issue10 8. Error when connecting to vcenter 5.1 or above (using SSO server). 11 9. Observations do not show up... 12 9. HealthAnalyzer OVA does not start up in VMware Fusion... 13 10. Increase the size of the OVA root partition 14 Page 3 of 14
1. Error during vsphere collection vcenter user account permission issue for storage profile access When collecting data from vcenter, HealthAnalyzer UI shows either of the following error messages A service error during during collection A runtime error occurred during collection and following line is seen in the vha.log An unhandled invocation target exception thrown by pbmqueryprofile method on PbmProfileProfileManager vcenter user account does not have sufficient permissions to collect all data necessary 1. In addition to the Read-Only permissions to the vcenter user account, a Assign Profile-driven storage > Profile-driven storage view privileges to the user account in order to collect Storage Policy data 2. If changing the permissions for read-only user or getting an account with above privileges is not an option then you can turn off collection and analysis for storage profiles by updating <VHA_Instance>/tomcat /webapps/vha/web-inf/classes/vha.properties file and set the following property to false. collection.storagepolicies.enabled 3. In appliance mode, <VHA_instance> is located at /usr/share/vha. 4. Restart HealthAnalyzer instance. For more details on how to configure vcenter user account for HealthAnalyzer data collection, see section Setting Up Access to vcenter Server and View Connection Server in VMware HealthAnalyzer Install and User Guide Note that the following best practices will be missing Storage Profile data if storage profile policy data collection is disabled: VSAN-003, VSAN-006, VSAN-008, VSAN-013 Page 4 of 14
2. Error during vsphere collection vcenter user account permission issue for iscsi access When collecting data from vcenter, HealthAnalyzer UI shows either of the following error messages A service error during during collection A runtime error occurred during collection and the following lines (or similar) are seen in the vha.log An unhandled invocation target exception thrown by queryboundvnics method on IscsiManager An authorization error occurred while collecting data for IscsiManager vcenter user account does not have sufficient permissions to collect all data necessary 1. In addition to the Read-Only permissions to the vcenter user account, Assign Host > Configuration > Storage partition configuration privileges to the user account in order to collect iscsi Manager data 2. If changing the permissions for read-only user or getting an account with above privileges is not an option then you can turn off collection and analysis for iscsi by updating <VHA_Instance>/tomcat /webapps/vha/web-inf/classes/vha.properties file and set the following property to false. collection.iscsiport.enabled 2. In appliance mode, <VHA_instance> is located at /usr/share/vha. 3. Restart HealthAnalyzer instance. For more details on how to configure vcenter user account for HealthAnalyzer data collection, see section Setting Up Access to vcenter Server and View Connection Server in VMware HealthAnalyzer Install and User Guide Note that the following best practices will be missing iscsi data if iscsi data collection is disabled: NE-003, NE-004, NE-006, NE-009, NE-011, NE-014, NE-019, ST-014, ST-026, VSAN-005, VSAN-011, VSAN-015 Page 5 of 14
3. Error during vsphere collection Disconnected ESX hosts issue When collecting data from vcenter, HealthAnalyzer UI shows either of the following error messages A service error during during collection A runtime error occurred during collection and the following line is seen in the vha.log An unhandled invocation target exception thrown by queryboundvnics method on IscsiManager and any of the following lines are seen in the vha.log An error occurred while communicating with the remote host javax.xml.ws.soap.soapfaultexception: vim.fault.nohost During data collection, one or more ESX hosts might be in disconnected state and vcenter is unable to communicate with those ESX hosts to provide the iscsi and Storage profile data to HealthAnalyzer. This can also be momentary when the ESX host is being taken down for maintenance. 1. Try any one of the following and re-run data collection Try running collection again and see if the error was momentary. If not, try the following: Fix the disconnected ESX hosts to bring them back to normal state or Remove those ESX hosts from vcenter if that is an option or Exclude those ESX hosts or their parent cluster in HealthAnalyzer discovery phase. 2. If none of the above are viable options at customer site, then you can turn off collection and analysis for iscsi and storage profiles by updating <VHA_Instance>/tomcat /webapps/vha/web- INF/classes/vha.properties file and set the following properties to false. collection.iscsiport.enabled collection.storagepolicies.enabled 3. In appliance mode, <VHA_instance> is located at /usr/share/vha. 4. Restart HealthAnalyzer instance. Note that the following best practices will be missing iscsi data if iscsi data collection is disabled: NE-003, NE-004, NE-006, NE-009, NE-011, NE-014, NE-019, ST-014, ST-026, VSAN-003, VSAN-005, VSAN-006, VSAN-008, VSAN-013, VSAN-011, VSAN-015 Page 6 of 14
4. Error during Horizon View Desktop collection Unresolved issue When collecting data from Horizon View Connection broker, HealthAnalyzer UI shows either of the following error messages A service error during during collection A runtime error occurred during collection and a line similar to the following is seen in the vha.log Unable to create a new instance of type 'com.sun.jndi.ldap.ldapctx This error occurs with some of the View Desktop Pools with certain configurations. The exact reason for this error is not known. There is no known solution but the work around is to skip data collection for those pools and continue with the collection and analysis. For those pools with issues, one has to manually analyze them against best practices. This is not always desirable for pool with large number of desktops, but this work around will let you analyze the other desktop pools automatically and generate a report. Steps to skip certain pools and proceed with collection/analysis 1) Edit the file vha.properties For VHA Java App: <VHA folder>/tomcat/webapps/vha/web-inf/classes/vha.properties For VHA OVF: /usr/share/vha/tomcat/webapps/vha/web-inf/classes/vha.properties 2) Change the value of collection.skip.errorviewpools.enabled to 'true' 3) Restart VHA (close VHA App completely and start HealthAnalyzer.jar) 4) Run collection again 5) Once collection is over, you can open the vha.log and look for the word Skipping pool" and that should provide you with the Dekstop Pools that got skipped. Page 7 of 14
5. Error while accessing Web UI from a browser network issue When the Web UI is accessed from a browser, HealthAnalyzer UI shows the following error and refreshing the browser does not help: Unknown error occurred. See logs for more information This error occurs if HealthAnalyzer Application (Java or OVF) is not running Network latency between the browser and the server where HealthAnalyzer is running is too high Make sure the HealthAnalyzer application is running. If possible, use a browser that is on a network with high network bandwidth to access HealthAnalyzer application. Try running HealthAnalyzer locally. Page 8 of 14
6. Error when starting Java version of VHA When the Java version of VHA (launcher) is started, the App server or the Database server stays in Starting status or shows an error at with a link to the log file. 1) Java incompatibility (Launcher displays Error during startup: see log file for details and log file contains support is not available when running on Java Change Java version 1.7 is the minimum version required for VHA 5.0.4 and above. Make sure correct version is installed by opening a terminal/command window and check the version of Java: java version 2) Ports being used for Database and tomcat conflict with other application ports. Launcher displays Error during startup: see log file for details and log file contains java.net.bindexception: Address already in use. Check if ports 41984 (used for database) and 8080 (used for tomcat server) are being used by other applications. If so, stop VHA and change port numbers in application (directly via Launcher) and restart VHA via Launcher. 3) Not enough contiguous memory available. Launcher displays Error during startup: see log file for details and log file contains Error occurred during initialization of VM Could not reserve enough space If using 32 bit JRE on 64 bit OS upgrade to a 64 bit JRE. Reboot your machine and that should make more contiguous memory available. Page 9 of 14
7. vcenter Collection fails during connection vcenter certificate issue An error Connection failed appears while a user is using HealthAnalyzer on vcenters using 512 bits certificate Java 7 does not consider MD2 as secure algorithm anymore and also RSA key size should not be less than 1024 Update the certificates on vcenter as Java 7 does not consider MD2 as secure algorithm anymore and also RA key size should not be less than 1024. If updating the certificates is not an option then o Go to JRE installation folder and edit java.security file (ex. C:\Program Files\Java\jre7\lib\security\java.security) o Comment this line jdk.certpath.disabledalgorithms=md2, RSA keysize < 1024 i.e. put a '#' in front as below. # jdk.certpath.disabledalgorithms=md2, RSA keysize < 1024 o Add this line below the line that commented was above: jdk.certpath.disabledalgorithms= o After saving this file, relaunch VHA launcher/appliance. This will bypass security enhancements that came with Java 7 (http://docs.oracle.com/javase/7/docs/technotes/guides/security/enhancements- 7.html) and should collect data against the vcenter successfully. o Please advice your customer to update the certificates on vcenter as Java 7 does not consider MD2 as secure algorithm anymore and also key size should not be less than 1024. o After Healthcheck is completed, revert these security settings. Page 10 of 14
8. Error when connecting to vcenter 5.1 or above (using SSO server) An error occurs (Unable to connect to target server) while a user is connecting to vcenter 5.1 or above using SSO server SSO server and vcenter clocks not synchronized Synchronize vcenter clock with NTP server and restart VHA collection. If synchronizing the clocks is not an option then leave SSO server field as blank. o Note that if there is VSAN in vcenter then following information will be missing: Data table for best practice VSAN-014 Data table and analysis for best practices VSAN-004, VSAN-007 and VSAN-009 o and if there is vfrc in vcenter then data table will be missing for VM-028. These are simple look up operations that can be easily performed manually using Web Client. Page 11 of 14
9. Observations do not show up Observations saved within VHA do not show up in the Observations section in the Health Check report Inability to parse Observation content, when copy pasted from another editor like MS-Word Type the text or copy paste as text instead of from Word as is. Page 12 of 14
9. HealthAnalyzer OVA does not start up in VMware Fusion Inability to start vami-sfcbd results in HealthAnalyzer OVA start up failue in VMware Fusion Networking configuration results in inability to start vami-sfcbd In VMware Fusion, edit virtual network adapter settings to use Share with my Mac option. Page 13 of 14
10. Increase the size of the OVA root partition 1) First, create a backup of all Your data as extending root partition may lead to unrecoverable data loss. You can do that by exporting all Your projects to a save location. 2) Extend the disk to the desired size from VMWare Fusion, VMware Workstation or VMware vsphere client. You must delete the snapshots before you can make a change. Shut down or power off the virtual machine. You cannot change the setting while the virtual machine is powered on or suspended. After the disk is expanded Power on the appliance and login into the shell. 3) ##Go to /opt folder root@vmwarehealthanalyzer [ ~ ]# cd /opt/ 4) ##Download gdisk rpm package root@vmwarehealthanalyzer [ ~ ]# wget https://sourceforge.net/projects/gptfdisk/files/gptfdisk/1.0.1/gdisk-binaries/gdisk-1.0.1-1.x86_64.rpm 5) ##Install gdisk package root@vmwarehealthanalyzer [ ~ ]# rpm -ivh --nodeps gdisk-1.0.1-1.x86_64.rpm 6) ##Check root partition space root@vmwarehealthanalyzer [ ~ ]# df -h 7) ##Verify that block device /dev/sda3 GUID is 9BE72B25-0BDF-4B1D-9992-2364334D137A. GUID number may be different for different vha 5.2.0 build number. root@vmwarehealthanalyzer [ ~ ]# echo -e "i\n3\nq" gdisk /dev/sda grep 'Partition unique GUID' awk '{ print $4 }' 8) ##Extend root partition. If the GUID number is different from 9BE72B25-0BDF-4B1D-9992-2364334D137A You need to replace it in the next echo command. root@vmwarehealthanalyzer [ ~ ]# echo -e "d\n4\nd\n3\nn\n3\n\n\n\nx\nc\n3\n9be72b25-0bdf-4b1d-9992-2364334d137a\nw\ny" gdisk /dev/sda > /opt/extend.log 2>&1 9) ##Reboot vm root@vmwarehealthanalyzer [ ~ ]# reboot 10) ##Resize file system on the root partition: root@vmwarehealthanalyzer [ ~ ]# resize2fs /dev/sda3 11) ##Check if root partition is extended root@vmwarehealthanalyzer [ ~ ]# df -h Page 14 of 14