Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Retrieving health data fails with the error: Unable to retrieve health data from https://<servername:port>/... (1013507)

Symptoms

  • Retrieving health data in vSphere fails.
  • When attempting to retrieve health data in vSphere, you see the error:

    Unable to retrieve health data from https://<servername:port>/....

  • The vws.log contains the entry:

    ERROR 'org.apache.commons.httpclient.HttpMethodDirector'] Narrowly avoided an infinite loop in execute
    ERROR 'com.vmware.vim.health.impl.ComponentSpec'] Error while trying to login to https://Virtual_Center:8443/vws/Login
    org.apache.commons.httpclient.RedirectException: Maximum redirects (100) exceeded
                        at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:184)
                        at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
                        at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
                        at com.vmware.vim.security.authenticate.impl.ServiceConnectImpl.loginByCertificate(ServiceConnectImpl.java:213)
                        at com.vmware.vim.health.impl.ComponentSpec.setupClient(ComponentSpec.java:394)
                        at com.vmware.vim.health.impl.ComponentSpec.retrieveHealth(ComponentSpec.java:250)
                        at com.vmware.vim.health.impl.HealthPollerImpl.retrieveHealthFromUrl(HealthPollerImpl.java:129)
                        at com.vmware.vim.health.impl.HealthPollerImpl.retrieveHealth(HealthPollerImpl.java:107)
                        at com.vmware.vim.health.impl.HealthPollerImpl.computeHealth(HealthPollerImpl.java:200)
                        at com.vmware.vim.health.impl.HealthPollerImpl.retrieveHealth(HealthPollerImpl.java:105)
                        at com.vmware.vim.health.impl.HealthPollerImpl.pollHealth(HealthPollerImpl.java:87)
                        at com.vmware.vim.health.impl.HealthPollerImpl.access$100(HealthPollerImpl.java:32)
                        at com.vmware.vim.health.impl.HealthPollerImpl$PollerThread.run(HealthPollerImpl.java:57)
                        at java.lang.Thread.run(Thread.java:595)
    ERROR 'com.vmware.vim.health.impl.ComponentSpec'] Unable to retrieve health document because of null http client for component FF9E9903-A78E-4714-9C57-D94B15BC05F9.visvc
    ERROR com.vmware.vim.cimmonitor.service.impl.CimMonitorImpl] Error connecting to CIMOM on vmware_vms1.vmhost.host.local/host-9
    WARN com.vmware.vim.cimmonitor.service.impl.CimMonitorImpl] vmware_vms1.vmhost.host.local/host-9: Increasing refresh interval to 2700000 millis.
    INFO com.vmware.vim.cimmonitor.service.impl.CimMonitorImpl] randomly scheduled host-9 for health poll in 2662944 millis
    ERROR com.vmware.vim.cimmonitor.service.impl.CimMonitorImpl] Error connecting to CIMOM on vmware_vms2.vmhost.host.local/host-141
    WARN com.vmware.vim.cimmonitor.service.impl.CimMonitorImpl] vmware_vms2.vmhost.host.local/host-141: Increasing refresh interval to 2700000 millis.

  • The Hardware status tab may show the error:

    Hardware monitoring service on this host is not responding or not available
    Additional details: Malformed URI

Resolution

This issue occurs if the hostname of the vCenter Server contains a character that Tomcat does not support (such as the underscore character "_"). Tomcat requires the hostname to be RFC 952 compliant. To resolve this issue, ensure that that vSphere server's hostname is RFC 952 compliant.
 
The underscore character in the domain name or host name may also cause the Malformed URI error on the Hardware Status tab. An underscore is not permitted in either the hostname and domain name. To workaround the issue, remove the host from vCenter Server, and re-add it using its IP address instead of the DNS name.
 
You may also experience this issue if:
  • Update Manager is installed on the vCenter Server, but it is out of date or if it is installed but references an old vCenter Server address. To resolve this issue, reinstall  Update Manager.
  • You are using a proxy server. Check your browser proxy settings to verify that https://<servername:port>/ is accessible. If it is not, check your firewall (or corporate security policy) to determine why. 

See Also

Update History

02/09/2011 - Added information about checking proxy settings. 05/22/2012 - Added additional symptoms to reflect an _ in the hostname

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 9 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 9 Ratings
Actions
KB: