We are running a vCenter appliance version 5.5 2d. We recently updated to this version in an attempt to resolve our problems with vCenter crashing. Occasionally usually every 1 - 2 days vCenter will crash. When it crashes a dump file is created (core.vpxd-worker) in the /storage/core folder.
I have a support case open with VMWare and so far I don't have any resolution to why my vCenter is crashing so frequently.
I did notice while picking through the vpxd.log after the latest crash that there are out of memory errors with postgresql that happened right before the crash. I believe this may be the culprit. Anyone have any ideas on how to resolve these errors?
Our vCenter appliance has 24GB of memory and hardly ever goes beyond 25% usage, same with the CPU. I'm going to try running a manual vacuum command outlined here but other than that I'm all out of ideas on what to try.
2015-02-07T02:00:05.656Z [7F717AEDD700 warning 'Default' opID=SWI-3f804862] [VdbStatement] SQL execution failed: vacuum (analyze) vpx_hist_stat1_227
2015-02-07T02:00:05.656Z [7F717AEDD700 warning 'Default' opID=SWI-3f804862] [VdbStatement] Execution elapsed time: 617 ms
2015-02-07T02:00:05.656Z [7F717AEDD700 warning 'Default' opID=SWI-3f804862] [VdbStatement] Diagnostic data from driver is 53200:1:7:ERROR: out of memory
--> Failed on request of size 71.;
--> Error while executing the query
2015-02-07T02:00:05.656Z [7F7136244700 info 'commonvpxLro' opID=1852ed36] [VpxLRO] -- BEGIN task-internal-54802710 -- -- vmodl.query.PropertyCollector.retrieveContents -- 40675e8b-09b0-7864-8924-58652fc267da(525eca50-84c7-4d37-746a-92b7f9e93dae)
2015-02-07T02:00:05.657Z [7F719F5B8700 info 'commonvpxLro' opID=55c1e2d6] [VpxLRO] -- BEGIN task-internal-54802713 -- -- vim.SessionManager.sessionIsActive -- 81106db1-3765-372b-d642-b669c3f2f54e(52fdfe72-ff88-eb87-d25c-3319b0c665f0)
2015-02-07T02:00:05.657Z [7F7136244700 info 'commonvpxLro' opID=1852ed36] [VpxLRO] -- FINISH task-internal-54802710 -- -- vmodl.query.PropertyCollector.retrieveContents --
2015-02-07T02:00:05.656Z [7F717AEDD700 warning 'Default' opID=SWI-3f804862] [VdbStatement] Bind parameters:
2015-02-07T02:00:05.657Z [7F719F5B8700 info 'commonvpxLro' opID=55c1e2d6] [VpxLRO] -- FINISH task-internal-54802713 -- -- vim.SessionManager.sessionIsActive --
2015-02-07T02:00:05.658Z [7F719C5D9700 info 'commonvpxLro' opID=2d146636] [VpxLRO] -- BEGIN task-internal-54802714 -- -- vmodl.query.PropertyCollector.retrieveContents -- 9008cfb1-d611-14ad-8b3e-202cb5d30d42(52caec42-b1ee-461f-a49d-f6d3f0f243dd)
2015-02-07T02:00:05.658Z [7F719C5D9700 info 'commonvpxLro' opID=2d146636] [VpxLRO] -- FINISH task-internal-54802714 -- -- vmodl.query.PropertyCollector.retrieveContents --
2015-02-07T02:00:05.658Z [7F717AEDD700 error 'Default' opID=SWI-3f804862] [Vdb::IsRecoverableErrorCode] Unable to recover from 53200:7
2015-02-07T02:00:05.658Z [7F717AEDD700 error 'Default' opID=SWI-3f804862] [VdbStatement] SQLError was thrown: "ODBC error: (53200) - ERROR: out of memory
--> Failed on request of size 71.;
--> Error while executing the query" is returned when executing SQL statement "vacuum (analyze) vpx_hist_stat1_227"