Hardware Status tab error: No new host data available. Data will be updated in 5 minutes (2015838)

VMware 호스트상에서 아래와 같이 하드웨어의 상태가 보이지 않는 경우

아래의 2가지 방법중 선택적으로 진행하면 될듯 하다.

Hardware Status tab error: No new host data available. Data will be updated in 5 minutes (2015838)

Symptoms

• When you click on the hardware status for a host, you receive the error:
  
  No new host data available. Data will be updated in 5 minutes
  
  
• When you click Update selection at the upper left of the screen, you may see the error:
  
  Host sensor data is not updated. The query service is not available or was restarted, try to unselect and select this host again.
  
  
• In the sms.log file, you see messages similar to:
  
  2012-03-06 14:44:38,402 [Thread-18] ERROR com.vmware.vim.sms.StorageManagerImpl  - Exception while loading providers from xDB!
  com.vmware.vim.sms.fault.QsConnectionException: java.util.concurrent.ExecutionException: com.vmware.vim.binding.vmodl.fault.HostCommunication:
  inherited from com.vmware.vim.binding.vmodl.fault.HostCommunication: <83><8A><83><82><81>[<83>g <83>z<83>X<83>g<82>ÆÌÊM<92><86><82>ÉG<83><89><81>[<82><94><90><82><82>Ü<82><81>B
      at com.vmware.vim.sms.qs.QsProxyStrategy.createClient(QsProxyStrategy.java:92)
      at com.vmware.vim.sms.qs.QsProxyStrategy.(QsProxyStrategy.java:50)
      at com.vmware.vim.sms.qs.QsProxyStrategy.getInstance(QsProxyStrategy.java:57)
      at com.vmware.vim.sms.qs.client.impl.QsClientImpl.(QsClientImpl.java:33)
      at com.vmware.vim.sms.qs.data.QueryMapper.(QueryMapper.java:84)
      at com.vmware.vim.sms.qs.data.QueryMapper.getInstance(QueryMapper.java:92)
      at com.vmware.vim.sms.StorageManagerImpl.loadProviders(StorageManagerImpl.java:173)
      at com.vmware.vim.sms.StorageManagerImpl.access$200(StorageManagerImpl.java:47)
      at com.vmware.vim.sms.StorageManagerImpl$ProviderLoader.run(StorageManagerImpl.java:128)
  Caused by: java.util.concurrent.ExecutionException: com.vmware.vim.binding.vmodl.fault.HostCommunication:
  
  
• In the vws.log file, you see messages similar to:
  
  2012-03-06 14:41:14,229 Thread-39  ERROR com.vmware.vim.health.impl.ComponentSpec] Error while trying to login to https://name.domain.com:10443java.net.UnknownHostException: name.domain.com
      at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:195)
      at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
      at java.net.Socket.connect(Socket.java:529)
      at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:559)
      at com.sun.net.ssl.internal.ssl.SSLSocketImpl.(SSLSocketImpl.java:401)
      at com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl.createSocket
  (SSLSocketFactoryImpl.java:123)
      at com.vmware.vim.common.ssl.AuthSSLProtocolSocketFactory.createSocket
  (AuthSSLProtocolSocketFactory.java:198)
      at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)
      at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$
  HttpConnectionAdapter.open
  (MultiThreadedHttpConnectionManager.java:1361)
      at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry
  (HttpMethodDirector.java:387)
      at org.apache.commons.httpclient.HttpMethodDirector.executeMethod
  (HttpMethodDirector.java:171)
      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:117)
      at com.vmware.vim.health.impl.ComponentSpec.setupClient(ComponentSpec.java:462)
      at com.vmware.vim.health.impl.ComponentSpec.retrieveHealthFromUrl(ComponentSpec.java:309)
      at com.vmware.vim.health.impl.ComponentSpec.retrieveHealth(ComponentSpec.java:266)
      at com.vmware.vim.health.impl.HealthPollerImpl.retrieveHealthFromUrl
  (HealthPollerImpl.java:116)
      at com.vmware.vim.health.impl.HealthPollerImpl.retrieveHealth(HealthPollerImpl.java:103)
      at com.vmware.vim.health.impl.HealthPollerImpl.computeHealth(HealthPollerImpl.java:185)
      at com.vmware.vim.health.impl.HealthPollerImpl.retrieveHealth(HealthPollerImpl.java:101)
      at com.vmware.vim.health.impl.HealthPollerImpl.pollHealth(HealthPollerImpl.java:84)
      at com.vmware.vim.health.impl.HealthPollerImpl.access$100(HealthPollerImpl.java:28)
      at com.vmware.vim.health.impl.HealthPollerImpl$PollerThread.run(HealthPollerImpl.java:54)
      at java.lang.Thread.run(Thread.java:662)
  
  
• In the ls.log file, you see messages similar to:
  
  [2012-03-06 10:29:42,729 Timer-4  ERROR com.vmware.vim.license.dao.assignments.impl.
  LicenseAssignmentsDaoImpl] Can't obtain QS connection:
  com.vmware.vim.license.qs.QsUnableToConnectException: java.util.concurrent.
  ExecutionException: com.vmware.vim.binding.vmodl.fault.HostCommunication:
  inherited from com.vmware.vim.binding.vmodl.fault.HostCommunication: ãªã¢ã¼ã ã¹ãã¨ã®é信中ã«ã¨ã©ã¼ãçºçãã¾ããã
      at com.vmware.vim.license.qs.impl.QsClientStubFactoryImpl.getVcInventoryQsConnectionData
  (QsClientStubFactoryImpl.java:159)
      at com.vmware.vim.license.qs.impl.QsClientStubFactoryImpl.connectVcInventoryQs
  (QsClientStubFactoryImpl.java:59)
      at com.vmware.vim.license.qs.util.QsUtil.connectVcInventoryQs(QsUtil.java:72)
      at com.vmware.vim.license.qs.impl.QsClientStubProviderImpl.borrowQsClientStub
  (QsClientStubProviderImpl.java:29)
      at com.vmware.vim.license.dao.assignments.impl.LicenseAssignmentsDaoImpl.
  getLicenseAssignments(LicenseAssignmentsDaoImpl.java:140)
      at com.vmware.vim.license.dao.assignments.impl.LicenseAssignmentsDaoImpl.
  getLicenseAssignmentsFederated(LicenseAssignmentsDaoImpl.java:95)
      at com.vmware.vim.license.dao.usage.impl.CurrentLicenseUsageDaoImpl.
  getAdditionalAssignmentsLicenseUsage(CurrentLicenseUsageDaoImpl.java:307)
      at com.vmware.vim.license.dao.usage.impl.CurrentLicenseUsageDaoImpl.
  getAdditionalAssignmentsLicenseUsageFederated(CurrentLicenseUsageDaoImpl.java:85)
      at com.vmware.vim.license.service.check.impl.LicenseCheckerImpl.
  getAdditionalLicenseUsageFederated(LicenseCheckerImpl.java:113)
      at com.vmware.vim.license.service.check.impl.LicenseCheckerImpl.
  tryDoLicenseChecking(LicenseCheckerImpl.java:74)
      at com.vmware.vim.license.service.impl.LicenseCheckingTimerTaskImpl.execute
  (LicenseCheckingTimerTaskImpl.java:27)
      at com.vmware.vim.license.service.impl.TimerTaskImpl.run(TimerTaskImpl.java:37)
      at java.util.TimerThread.mainLoop(Timer.java:512)
      at java.util.TimerThread.run(Timer.java:462)
  Caused by: java.util.concurrent.ExecutionException: com.vmware.vim.binding.vmodl.
  fault.HostCommunication:
  inherited from com.vmware.vim.binding.vmodl.fault.HostCommunication:
      at com.vmware.vim.vmomi.core.impl.BlockingFuture.get(BlockingFuture.java:70)
      at com.vmware.vim.license.qs.impl.QsClientStubFactoryImpl.getVcInventoryQsConnectionData
  (QsClientStubFactoryImpl.java:156)
      ... 13 more
  Caused by: com.vmware.vim.binding.vmodl.fault.HostCommunication:

Cause

This issue may occur due to any one of the following reasons:

• The hosts file (located in %systemroot%/system32/drivers/etc) does not contain the correct entries for the vCenter Server and host.
• The user credential does not have sufficient permissions at the root/vCenter server level.
• The user ID used to log has a custom or cloned role.

Resolution

To resolve this issue, follow either of these steps depending on the cause:

If hosts file (located in %systemroot%/system32/drivers/etc) does not contain the correct entries for the vCenter Server and host:

1. Stop the VMware VirtualCenter Server service.
2. Open the hosts file in a text editor. The hosts file is located in:
   
   %systemroot%/system32/drivers/etc
   
   
   
3. Add lines with the correct information for the vCenter Server and host using this format:
   
   IP_Address FQDN short_name
   
   Note: Each field must be separated by at least one space.
   
   
4. Save and close the file.
5. Start the VMware VirtualCenter Server service.

If the user credential does not have sufficient permissions at the root/vCenter level, the user cannot view the health status of an ESX/ESXi host. To assign permissions at the vCenter/root level:

1. Go to Home > Inventory > Hosts and Clusters and select the vCenter Server.
2. Click the Permission tab.
3. Right-click in the right pane and click Add permission.
4. Select Read only and then select the user.
5. Deselect the Propagate to child objects if you do not wish the user to see all object in vCenter option.
6. Click OK.
7. Log in to vCenter Server with the user credentials and verify if you can see the Hardware Status information.

If the user ID used to log in has a custom or cloned role, ensure that the user ID properties are correct:

1. From the main horizontal menu bar in vCenter Server, click View > Administration > Roles.
2. Right-click the role and choose Edit Role.
3. Scroll down in the resulting window and expand the VRMPolicy selections. If the box Query VRMPolicy is not selected, select it and click OK.
4. Switch to the main vCenter Hosts and Clusters view.
5. Remove any permissions involving this user ID from any of the Cluster and Datacenter levels, if they are applied there, and ensure that the permission is applied at the very top (root) level.
6. Restart VMware VirtualCenter Server Service (which in turn restarts VMware Management Webservices). For more information, seeStopping, starting, or restarting vCenter services (1003895).
7. Wait at least 5 minutes and then log in to vCenter Server with the user ID.
8. Select a host and click the Hardware Status tab to confirm that you see expected results, such as the sensor data in the results window. 
   
   

If the issue persists after attempting to complete one of the preceding resolutions:

• Collect the logs for vCenter Server and at least one of the hosts for which you attempted to see data. For more information, seeCollecting diagnostic information for VMware products (1008524). 
• File a support request with VMware Support and quote this Knowledge Base article ID (1030536) in the problem description. For more information see How to File a Support Request.
  
  
  

See Also

• Stopping, starting, or restarting vCenter services
• Collecting diagnostic information for VMware products
• [Archived] Hardware Status tab error: No new host data available. Data will be updated in 5 minutes
• [Archived] Clicking the Hardware Status tab for an ESX host reports the warning: No new host data available. Data will be updated in 5 minutes

This Article Replaces

[Archived] Clicking the Hardware Status tab for an ESX host reports the warning: No new host data available. Data will be updated in 5 minutes (1035457)

[Archived] Hardware Status tab error: No new host data available. Data will be updated in 5 minutes (1030536)

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.