This monitor tracks the vCenter Server Health Alarm.
By default, the alarm is triggered by the following event:
- vim.event.HealthStatusChangedEvent: Health status of the vCenter Server changed.
Check that vCenter Server database has enough space. For more information on managing vCenter Server database requirements, see this VMware KB article.
Check whether the vCenter Server vpxd service is running. If the service is stopped, try starting it again. For more information on stopping, starting, or restarting VMware vCenter Server 6.0 services, see this VMware KB article.
If the vCenter Server vpxd service fails to start, see these VMware KB articles:
- Troubleshooting the VMware VirtualCenter Server service when it does not start or fails on vCenter Server (KB1003926)
- vCenter Server Appliance vmware-vpxd service fails to start (KB2018902)
- VMware VirtualCenter Server service fails to start with the vpxd.log error: ODBC error: (28000) (KB1017688)
- The vpxd service fails to start after upgrading from vCenter Server Appliance 5.1 Update1 to 5.1 Update2 (KB2075309)
- VMware VirtualCenter Server Service fails to start with the vpxd log error: W32Util_RegisterEventLog: Could not open registry key (KB2005164)
- VMware VirtualCenter Server service fails to start with the error: vpxd logs show ODBC error: (08001) - [Microsoft][SQL Native Client]TCP Provider: Timeout error . (KB1025664)
- vCenter Server process (vpxd) consumes all memory and fails (KB2062989)
See the Help Center for more information including reference lists of all Rules and Monitors and full set of User Guides for the Veeam MP for VMware.
See the VMware Online Documentation for more information on VMware vSphere, in particular: