vCenter server error: CPU Exhaustion on vCenter_name - with Splunk monitoring tool enabled
search cancel

vCenter server error: CPU Exhaustion on vCenter_name - with Splunk monitoring tool enabled

book

Article ID: 397850

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • vCenter server keeps giving errors:
    CPU Exhaustion on vCenter_Name    AcknowledgeReset To Green

  • vpxd-profiler-xxx.log:
     vpxd-profiler-xxx.log:--> ThreadState/ThreadId/10042/State/Task::lro-16137837::PerfMgr::vim.PerformanceManager.queryAvailableMetric::52aa1f95-470a-18f5-a49d-xxxxxxxx(523d2016-6c14-26ca-3e3f-1xxxxxxx)/State/Vdb/State/ SELECT sc.stat_id, d.device_name FROM vpx_stat_counter sc, vpx_sample_time1 sm, vpx_device d, vpx_hist_stat1 st WHERE sc.entity_id = ?   and coalesce(sc.device_id,1) = coalesce(d.device_id,1)   and sc.counter_id = st.counter_id   and st.time_id = sm.time
    vpxd-profiler-xxx.log:--> ThreadState/ThreadId/10161/State/Task::lro-16058078::PerfMgr::vim.PerformanceManager.queryAvailableMetric::52aa1f95-470a-18f5-a49d-xxxxxxxx(523d2016-6c14-26ca-3e3f-1xxxxxxx)/State/Vdb/State/ SELECT sc.stat_id, d.device_name FROM vpx_stat_counter sc, vpx_sample_time1 sm, vpx_device d, vpx_hist_stat1 st WHERE sc.entity_id = ?   and coalesce(sc.device_id,1) = coalesce(d.device_id,1)   and sc.counter_id = st.counter_id   and st.time_id = sm.time
    ======
    vpxd-profiler-xxx.log:--> /SessionStats/SessionPool/Session/Id='52axxx-xxx-18f5-a49d-xxxxxxx'/Username='xxxxxx\xxx-splunk'/ClientIP='xx.xxx.xx.xxx'/HttpSessionObject/Hidden/total 0
    vpxd-profiler-xxx.log:--> /SessionStats/SessionPool/Session/Id='52axxx-xxx-18f5-a49d-xxxxxxx'/Username='xxxxxx\xxx-splunk'/ClientIP='xx.xxx.xx.xx'/PropertyCollector/TotalObjectCount/total 38910

  • postgres:
    2025-xx-xx 11:30:26.223 UTC 68134989.5b93 0 VCDB vc [local] 23443 11 LOG:  duration: 4552652.665 ms  statement: select regexp_replace(regexp_replace (regexp_replace (vd.device_name, '(.*)(/Username='')(.*)(''/)(ClientIP='')(.*)(''.*)', '\3|-ClientIP-\6'), '(.*\\)(.*)', '\1_SLASH_\2'),'(.*)(@)(.*)', '\1_AT_\3')  as username, vhs.stat_val from vpx_hist_stat1 vhs, vpx_device vd, vpx_stat_counter vsc where vsc.device_id = vd.device_id  and vd.device_name LIKE '%Username%' and vhs.counter_id = vsc.counter_id and vsc.stat_id in (select id from VPX_STAT_DEF where name='sessionstats') order by time_id desc limit 1;
    2025-xx-xx 12:39:33.384 UTC 681332cc.83cb 0 VCDB vc [local] 33739 14 LOG:  duration: 7504734.112 ms  statement: BEGIN;declare "SQL_CUR0x7xxxxx" cursor with hold for  SELECT sc.stat_id, d.device_name FROM vpx_stat_counter sc, vpx_sample_time1 sm, vpx_device d, vpx_hist_stat1 st WHERE sc.entity_id = 1   and coalesce(sc.device_id,1) = coalesce(d.device_id,1)   and sc.counter_id = st.counter_id   and st.time_id = sm.time_id   AND sm.sample_time > '1970-01-01 00:00:00'::timestamp   AND sm.sample_time <= '2025-05-xx 10:34:28.649'::timestamp GROUP BY sc.stat_id, d.device_name ORDER BY sc.stat_id, d.device_name ;fetch 1024 in "SQL_CURxxxxxx"
    2025-xx-xx 12:39:33.398 UTC 681332cc.83cb 0 VCDB vc [local] 33739 15 LOG:  duration: 4147177.247 ms  plan:
      2025-xx-xx 12:39:57.435 UTC 68132d89.746d 0 VCDB vc [local] 29805 26 LOG:  duration: 5728347.510 ms  statement: BEGIN;declare "SQL_CUR0x7xxxx" cursor with hold for  SELECT sc.stat_id, d.device_name FROM vpx_stat_counter sc, vpx_sample_time1 sm, vpx_device d, vpx_hist_stat1 st WHERE sc.entity_id = 1   and coalesce(sc.device_id,1) = coalesce(d.device_id,1)   and sc.counter_id = st.counter_id   and st.time_id = sm.time_id   AND sm.sample_time > '1970-01-01 00:00:00'::timestamp   AND sm.sample_time <= '2025-05-xx 11:04:29.088'::timestamp GROUP BY sc.stat_id, d.device_name ORDER BY sc.stat_id, d.device_name ;fetch 1024 in "SQL_CUR0xxxxxx"




       
     

Environment

VMware vCenter Server 7.0.x

Cause

The issue is caused by a deployment of Splunk monitoring tool incompatible with VMware vCenter Server 7.0.x.

Resolution

Increase the CPU and speak to the vendor if that doesn't resolve it