WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud Foundation
  • VKS
  • Homelab
    • Resources
    • Nested Virtualization
  • VMware Nostalgia
  • Apple
You are here: Home / Uncategorized / How to get rid of "Quicks stats on hostX is not up-to-date" message

How to get rid of "Quicks stats on hostX is not up-to-date" message

09.27.2013 by William Lam // 10 Comments

After upgrading my Apple Mac Mini to ESXi 5.5 I noticed the following warning message being displayed after joining my ESXi host to my vCenter Server:

"Quick stats on mini is not up-to-date" 

I have seen this warning message in the past and it usually goes away within a few minutes of connecting to a vCenter Server. However, this time it did not go away and as you can see from the screenshot, I have had my ESXi host up for 4 days now and the message is still there.

UPDATE (9/30) - This looks to be a known issue in vSphere 5.5 and there is a permanent fix which has been documented in the following VMware KB 2061008. Restarting the management service will not prevent the warning message from coming again, please refer to the KB for the solution.

I do not know about you, but I like to have a clean environment and I get annoyed when I see warning/error messages in the UI. From what I can tell, vCenter Server was able to collect the "quick stats" from the ESXi host but perhaps there was a communication problem at some point or just a glitch?

In any case, is is pretty easy to fix the problem, you just need to restart the management service on the ESXi host and this will force a refresh of the stats. You have three ways of doing this:

  1. Restart management service using DCUI connecting to your ESXi console
  2. Restart management service using DCUI via command-line
  3. Restart management service using command-line script

Option 1 is pretty straight forward and both Option 2 and 3 can be performed on the command-line via an SSH session to your ESXi host if you have enabled SSH.

Option 2 - To launch the DCUI, just type "dcui" on the command-line and you will be able to interact with the DCUI as you normally would from the console and restart the management service:

Option 3 - To restart just using the command-line, you can run the following command to restrat the management service:

/sbin/services.sh restart

More from my site

  • Customizing the ESXi DCUI to show number of VMs
  • How to restart the ESXi management network via command-line?
  • Programmatically accessing the Broadcom Compatibility Guide (BCG)
  • Supported chipsets for the USB Network Native Driver for ESXi Fling
  • Quick Tip - Auditing ESXi boot firmware type

Categories // Uncategorized Tags // dcui, ESXi, management service, quick stats

Comments

  1. *protectedAnonymous says

    09/27/2013 at 5:54 pm

    Thank you for the info, i've had similar problems on Esxi5.5 🙂 Strange, but if you'd look in HA cluster settings (if you have a cluster), you can see same message there. I was a bit confused, because of that. Thought - something wrong with HA...
    Andy.

    Reply
    • *protectedWilliam Lam says

      09/30/2013 at 2:15 pm

      I've updated the article, this looks to be a known issue in vSphere 5.5, please refer to this VMware KB http://kb.vmware.com/kb/2061008 for the full solution

      Reply
  2. *protectedAnonymous says

    09/27/2013 at 6:18 pm

    thank you! works like a charm.

    Reply
  3. *protectedAnonymous says

    09/28/2013 at 9:44 am

    Continiuing mine reply about this problem in HA/DRS clustered environment - restarting service doesn't solve the issue. You'll have to run "Reconfigure for vSphere HA".
    Andy.

    Reply
    • *protectedWilliam Lam says

      09/30/2013 at 2:16 pm

      I've updated the article, this looks to be a known issue in vSphere 5.5, please refer to this VMware KB http://kb.vmware.com/kb/2061008 for the full solution

      Reply
  4. *protectedAnonymous says

    09/28/2013 at 2:42 pm

    Not working here...on 5.5 hosts nor 5.1 🙁
    Every box I have seen upgraded has this 'issue', surprised there isn't a better fix/explanation available.

    Reply
    • *protectedWilliam Lam says

      09/30/2013 at 2:16 pm

      I've updated the article, this looks to be a known issue in vSphere 5.5, please refer to this VMware KB http://kb.vmware.com/kb/2061008 for the full solution

      Reply
  5. *protectedAnonymous says

    09/28/2013 at 6:06 pm

    Thanks Andy, that fixed it for me.
    -Mike

    Reply
  6. *protectedAnonymous says

    09/30/2013 at 12:40 pm

    the issue is solved here:

    http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2061008

    Reply
    • *protectedWilliam Lam says

      09/30/2013 at 3:34 pm

      Thanks, I've have updated my article pointing to the KB.

      Reply

Thanks for the comment!Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Search

Thank Author

Author

William is Distinguished Platform Engineering Architect in the VMware Cloud Foundation (VCF) Division at Broadcom. His primary focus is helping customers and partners build, run and operate a modern Private Cloud using the VMware Cloud Foundation (VCF) platform.

Connect

  • Bluesky
  • Email
  • GitHub
  • LinkedIn
  • Mastodon
  • Reddit
  • RSS
  • Twitter
  • Vimeo

Recent

  • Programmatically accessing the Broadcom Compatibility Guide (BCG) 05/06/2025
  • Quick Tip - Validating Broadcom Download Token  05/01/2025
  • Supported chipsets for the USB Network Native Driver for ESXi Fling 04/23/2025
  • vCenter Identity Federation with Authelia 04/16/2025
  • vCenter Server Identity Federation with Kanidm 04/10/2025

Advertisment

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Copyright WilliamLam.com © 2025