Hello,
Failed to deploy vCenter HA Cluster (vcenter 6.5.0 Build 5318154) with the following error:
"A general system error occured: Failed to start HACore profile on node 192.168.18.22" (192.168.18.22 is the IP address for the witness server filled up during the configuration wizard)
We tried the below with no luck:
The following is the status of services from our vcenter:
Also there is a ping from our vcenter appliance to the above IP address:
Please advise,
Seeing the below errors in vpxd.log -->
2018-09-14T17:32:22.276+03:00 error vpxd[7F73A580C700] [Originator@6876 sub=vpxUtil opID=FlowBasedWizard-apply-911-ngc-80] /usr/bin/python failed with error [1] and output [2018-09-14T14:32:22.095Z Failed to start statsmonitor services. Error: Operation timed out
2018-09-14T17:32:22.276+03:00 info vpxd[7F73A580C700] [Originator@6876 sub=Default opID=FlowBasedWizard-apply-911-ngc-80] [VpxLRO] -- ERROR task-65223 -- FailoverClusterConfigurator -- vim.vcha.FailoverClusterConfigurator.deploy: vmodl.fault.SystemError:
--> Result:
--> (vmodl.fault.SystemError) {
--> faultCause = (vmodl.MethodFault) null,
--> faultMessage = <unset>,
--> reason = "Failed to start HACore profile on node 192.168.18.22"
--> msg = ""
--> }
Before initiating vCHA, perform the below steps on the vCSA active node -
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
Cheers,
Supreet
Did you check the comments on the thread A general system error occurred: Failed to start HACore profile on node? If it does not help, share the time stamp of the failure along with the vpxd.log from the master node and vmon-syslog.log from the witness node.
Cheers,
Supreet
Regarding the time stamp, the following screenshot mention it:
SupreetK , can you advise how can i share the log file please.
You can attach the log files to your reply or put them on a Dropbox link. What is the time zone for the above time stamp? Also, did you check the suggested resolution from the thread A general system error occurred: Failed to start HACore profile on node?
Cheers,
Supreet
Hello dear,
our time zone is "GMT +3". and please find the vpxd.log on the following URL: https://iccleb-my.sharepoint.com/:u:/g/personal/hassan_alkak_cci-me_com_lb/EZL9vYoM5LpKjFVRMQ46IcQBP...
Seeing the below errors in vpxd.log -->
2018-09-14T17:32:22.276+03:00 error vpxd[7F73A580C700] [Originator@6876 sub=vpxUtil opID=FlowBasedWizard-apply-911-ngc-80] /usr/bin/python failed with error [1] and output [2018-09-14T14:32:22.095Z Failed to start statsmonitor services. Error: Operation timed out
2018-09-14T17:32:22.276+03:00 info vpxd[7F73A580C700] [Originator@6876 sub=Default opID=FlowBasedWizard-apply-911-ngc-80] [VpxLRO] -- ERROR task-65223 -- FailoverClusterConfigurator -- vim.vcha.FailoverClusterConfigurator.deploy: vmodl.fault.SystemError:
--> Result:
--> (vmodl.fault.SystemError) {
--> faultCause = (vmodl.MethodFault) null,
--> faultMessage = <unset>,
--> reason = "Failed to start HACore profile on node 192.168.18.22"
--> msg = ""
--> }
Before initiating vCHA, perform the below steps on the vCSA active node -
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
Cheers,
Supreet
Thx Dear,
Solved after applying your steps, we found them on the thread, but we were waiting the approve from responsible.
Thanks again,
Hey guys!
I'm kind of a newbie in VMWare administration and a got this errors while enabling vCHA. My peer and witness was created just fine, but at the end of vCHA deploy it show this error "Failed to start HACore profile on node". Also in the vCenter HA session the buttons "edit" and "initiate failover" was visible but not enable.
I was not feeling very brave to do this kind of alterations so I try to reboot my active vCenter node (i had a backup in case it didn't comeback) and work just fine!
A was able to activate the vCHA with no errors.
Hope my experience help someone.
Why should I follow your steps or report errors? VCenter version is 6.7.0 13007421