Skip to main content

"Performance data is currently not available for this entity" viewing the performance tab

  Symptoms

  • While accessing the performance tab and navigating to Overview, you see:
No data available
 
  • The data for Real time, but fails to retrieve it for past 1 day, week, month or year. 
  • While selecting the advance parameter in performance tab, you see:
Performance data is currently not available for this entity
Cause
This issue is caused by the vCenter Server database (Postgress) containing a stale/future time stamp reference for the ESXi host when the data was collected.

For vCenter Servers using SQL, see 
"Performance data is currently not available for this entity" error after updating rollup in vSphere

Resolution
  1. Backup the vCenter database. For more inforamtion, see Back up and restore vCenter Server Appliance/vCenter Server 6.x vPostgres database
  2. Create a snapshot of the vCenter Server Appliance.
  3. Log in to the vSphere Web Client and navigate to Advanced Settings.
  4. Add this setting config.vpxd.stats.maxQueryMetrics with the value 256.
  5. Connect to vCenter Server Appliance through the console or using an SSH session along with root credentials.
  6. Enable the shell by running this command:
shell.set --enabled true
  1. Type shell and press Enter.
  2. Run this command to log in to the vCenter Server Appliance database:  
/opt/vmware/vpostgres/current/bin/psql -d VCDB -U postgres
  1. Run the following query:
select id,dns_name,last_perf_time from vpx_host;

Example output:
 
id |      dns_name      |   last_perf_time
----+--------------------+---------------------
15 | esxi1.labs.org | 2020-06-10 17:45:00
18 | esxi2.labs.org | 2020-06-10 17:25:00
52 | esxi3.labs.org | 2020-06-10 17:40:00
 
  1. Look for last_perf_time entries that are not close in time to the other entries:
id |      dns_name      |   last_perf_time
----+--------------------+---------------------
15 | esxi1.labs.org | 2020-06-10 17:45:00
18 | esxi2.labs.org | 2020-04-15 13:05:00    <-------- Problem host
52 | esxi3.labs.org | 2020-06-10 17:40:00
  1.  Run the following query to update the time stamp:
update vpx_host set last_perf_time =now() where id=’HOST-ID’;
         
  1. In vCenter database confirm that host time has been updated ( After update)
     id |      dns_name      |   last_perf_time
    ----+--------------------+---------------------
     15 | esxi1.labs.org | 2020-06-10 17:45:00
     18 | esxi2.labs.org | 2020-06-10 17:55:00 
     52 | esxi3.labs.org | 2020-06-10 17:28:00
  1. In 30-40 mins the vCenter Server performance chart will start populating. Data collection of month, week will take more time.

Comments

Popular posts from this blog

Troubleshooting vpxd service on Windows vCenter Server

  Symptoms You cannot connect to VMware vCenter Server with the vSphere Client. You cannot see the VMware vCenter Server in the inventory in the vSphere Web Client. You see a Microsoft Windows Event error associated with IIS similar to: Event properties - Event 7024, Service Control Manager The VMware VirtualCenter Server service terminated with service-specific error The system cannot find the file specified.. Log Name: System Source: Service Control Event ID: 7024 Level: Error Note : A windows Event ID 1000 may also be reported in relation to this issue.   Connecting to vCenter Server fails with the error: Cannot connect to host server_name : No connection could be made because the target machine actively refused it.   Attempting to start the VMware VirtualCenter Server service fails. You see this error: Windows could not start the VMware VirtualCenter Server service on...

Investigating virtual machine file locks on ESXi

      Details Adding an existing virtual machine disk (VMDK) to a virtual machine that is already powered on fails.                 Failed to add disk scsi0:1. Failed to power on scsi0:1   Powering on the virtual machine results in the power on task remaining at 95% indefinitely. Cannot power on the virtual machine after deploying it from a template. Powering on a virtual machine fails with an error: Unable to open Swap File Unable to access a file since it is locked Unable to access a file <filename> since it is locked Unable to access Virtual machine configuration In the /var/log/vmkernel log file, you see entries similar to: WARNING: World: VM xxxx: xxx: Failed to open swap file <path>: Lock was not free WARNING: World: VM xxxx: xxx: Failed to initialize swap file <path>   When opening a console to the virtual machine, you may receive ...

"Failed to configure vAPI Endpoint Service at the firstboot time" while installing Windows VC 6.5

  Symptoms While configuring the vAPI EndPoint Service, you experience these symptoms: Windows vCenter Server 6.5 installation fails while configuring the vAPI EndPoint Service vCenter Server 6.5 installation on a Windows Server fails during the vAPI EndPoint Service during the firstboot time. You see the error: Error: An error occurred while starting service 'vapi-endpoint'. Failed to start the vAPI Endpoint Service. Failed to configure vAPI Endpoint Service at the firstboot time. Please file a bug against VAPI   In vapi_firstboot.py_2948_stderr.log file, you see entries similar to: No valid files with pathname: C:\ProgramData\VMware\vCenterServer\logs\vapi\endpoint* found. ERROR starting vapi-endpoint rc: 2, stdout: , stderr: Start service request failed. Error: Service crashed while starting^M vapi firstboot failed Traceback (most recent call last): File "C:\Program Files\VMware\vCenter Server\firstbo...