Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

vCenter High Availablity enablement fails due to HACore profile startup failure and vmware-statsmonitor service startup timeout (55791)

Last Updated: 2/27/2024Categories: TroubleshootingTotal Views: 7243Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

Enabling VCHA on vCSA fails.

In the /var/log/vmware/vpxd/vpxd.log, you see a message similar to:

2017-11-07T12:24:54.750+01:00 info vpxd[7FDFFF9F3700] [Originator@6876 sub=Default opID=FlowBasedWizard-apply-426753-ngc:70014009-f6] [VpxLxRO] -- ERROR task-31949 -- FailoverClusterConfigurator -- vim.vcha.FailoverClusterConfigurator.configure: vmodl.fault.SystemError:
--> Result:
--> (vmodl.fault.SystemError) {
--> faultCause = (vmodl.MethodFault) null,
--> faultMessage = <unset>,
--> reason = "Failed to start HACore profile on node 10.107.233.10"
--> msg = ""
--> }
--> Args:
-->
--> Arg configSpec:
--> (vim.vcha.FailoverClusterConfigurator.VchaClusterConfigSpec) {
--> passiveIp = "10.107.233.9",
--> witnessIp = "10.107.233.10"
--> }

In vmon log entries from the failed peer or witness node /var/log/vmware/vmon/vmon-syslog.log​, you see a message similar to:

 17-11-07T12:24:35.212293+01:00 notice vmon Service statsmonitor start operation timed out.
17-11-07T12:24:35.214212+01:00 notice vmon Constructed command: /usr/bin/python /usr/lib/vmware-vmon/vmonEventPublisher.py --eventdata statsmonitor,UNHEALTHY,UNKNOWN,0
17-11-07T12:24:55.222870+01:00 warning vmon Service statsmonitor exited. Exit code 1
17-11-07T12:24:55.237217+01:00 err vmon Service batch op START failed. Failed services: 'statsmonitor'​

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

In statsmonitor service initialization during service startup, the database /var/vmware/applmgmt/appliance_stats.sqlite file is checked for integrity. If the IO subsystem hosting the appliance root file system vmdk is busy or facing latency issues, database integrity check might take longer time than the default service startup timeout, causing vMon service watchdog to declare statsmonitor unhealthy and stopping it. This can cause the vMon watchdog's whole HACore profile startup fail, in turn causing VCHA enablement to be declared as failed.

Default statsmonitor service configuration assumes fast storage IO but it's still possible for IO storms to cause IO delays.

Resolution

This issue has been fixed as of the following releases:

vCenter Server 6.7 Update 3, released 2019-08-20

vCenter Server 6.5 Update 3f, released 2019-12-19

You can download newer versions from here if needed: Download VMware vSphere
You can download product patches from here if needed: VMware Product Patches

Workaround

To work around this issue:

Before enabling VCHA, on the vCSA node(VCHA active node)

Login to vCSA with root credentials via SSH.

Modify statsmonitor service config for vMon

sed -i '/StartTimeout/d' /etc/vmware/vmware-vmon/svcCfgfiles/statsmonitor.json
sed -i '/ApiHealthFile/a "StartTimeout": 600,' /etc/vmware/vmware-vmon/svcCfgfiles/statsmonitor.json

Reload vMon service config through SIGHUP

kill -HUP $(cat /var/run/vmon.pid)​

Stop and start statmonitor service.

 /usr/lib/vmware-vmon/vmon-cli -k statsmonitor
/usr/lib/vmware-vmon/vmon-cli -i statsmonitor​

Enable VCHA.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
从 vCenter Server Appliance 6.0\6.0a\6.0b 升级到 6.0 U3g 在 rpm 更新期间挂起 (56625)

KB
•
HTML5 vSphere Client でサポートされている vSphere 6.5 および vSphere 6.7 の機能 (2150338)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Appliance

Related Versions:

VMware vCenter Server Appliance 6.7.x

VMware vCenter Server Appliance 6.5.x

Take Our Survey

Support Assistant