Overview Performance Charts fails with error: perfcharts service experienced an internal error

Products

• VMware vCenter Server
• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• Attempting to view Overview performance charts for vCenter inventory objects, such as clusters or hosts fails.
• On the vSphere Web Client you see error:
  perfcharts service experienced an internal error
• In the /var/log/vmware/perfcharts/stats.log file, you message similar to:

 

[Thread-2 ERROR com.vmware.vim.common.lifecycle.InitializerExecutor] Initialization error; attempt 2 will begin in 60 seconds...

java.util.concurrent.ExecutionException: java.lang.IllegalStateException: com.vmware.vim.vmomi.client.exception.ConnectionException: org.apache.http.conn.HttpHostConnectException: Connect to localhost:18091 [localhost/127.0.0.1] failed: Connection refused

at java.util.concurrent.FutureTask.report(FutureTask.java:122)

at java.util.concurrent.FutureTask.get(FutureTask.java:192)

at com.vmware.vim.common.lifecycle.InitializerExecutor$MonitorCallback.run(Unknown Source)

at java.lang.Thread.run(Thread.java:745)

Caused by: java.lang.IllegalStateException: com.vmware.vim.vmomi.client.exception.ConnectionException: org.apache.http.conn.HttpHostConnectException: Connect to localhost:18091 [localhost/127.0.0.1] failed: Connection refused

at com.vmware.vim.common.lifecycle.InitializerExecutor$MonitorCallback$1.run(Unknown Source)

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

at java.util.concurrent.FutureTask.run(FutureTask.java:266)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

... 1 more

 

 

 

Environment

VMware vSphere 6.7.x
VMware vCenter Server 6.5.x

Cause

This issue occurs when the vmware-sca service (Service Control Agent) is not running on the vCenter Server node.

Resolution

To resolve this issue, connect to the vCenter Server Appliance command line and restart the vmware-sca and vmware-perfcharts services.

 

1. Open an SSH connection to vCenter Server Appliance node.

2. Run the command service-control --status from the appliance shell and verify that the vmware-sca service is in a stopped state.

3. Run the command service-control --start vmware-sca to start the service

4. Run the command service-control --stop vmware-perfcharts && service-control --start vmware-perfcharts to restart the Performance Charts service.