while anabling Vcenter HA following error occured:
A general system error occurred: Failed to start HACore profile on node
What is the reason?
I have the same issue... I have been reading a ton of issues with VCHA enabling. But have not figured this out yet.
Yes we have everything FQDN, DNS, all on a local STRATUM-1 NTP etc. Been there done that...
Manually destroyed the VCHA from VCSA etc, rebooted etc, keeps failing after 90% with exact error
Encountered similar issue recently. Below steps helped me in resolving the issue.
Before enabling VCHA:
sed -i '/StartTimeout/d' /etc/vmware/vmware-vmon/svcCfgfiles/statsmonitor.json
sed -i '/ApiHealthFile/a "StartTimeout": 600,' /etc/vmware/vmware-vmon/svcCfgfiles/statsmonitor.json
kill -HUP $(cat /var/run/vmon.pid)
/usr/lib/vmware-vmon/vmon-cli -k statsmonitor
/usr/lib/vmware-vmon/vmon-cli -i statsmonitor
Please do take snapshot before you make any changes.
If this does not fix the issue attach vpxd.log to the thread.
Thanks, I did get it working without all of that just prior to your post.
See if I can remember the order but:
After failure I rebooted the witness and peer.
Logged into the console of my main active vcsa
shell> destroy-vcha -f
I noticed if you try to run <service vmware-vcha start>, you get a mask error.
<systemctl unmask vmware-vcha>
then <service vmware-vcha start>
This then caused the active vcsa to reboot....
Once up I went to the web client, clicked on vcenter, configure, vCenter HA, edit and enable.
In about 5 min it ran through the "sync" and all came back green
sapreaper What have you done in detail after you ran into that error?
Have you powered off and deleted the already deployed peer and whitness before you did the steps mentioned in your post?
I was running into a similar error with one of my vCenter setups. I connected to it via SSH and immediately received a prompt to change the password as the current one had expired. Once I updated that, I was able to complete the HA setup without any issues.