eduruizblas
Enthusiast
Enthusiast

error configuring HA

Jump to solution

Hi!

I am having trouble configuring HA on a vmware version 6.7 two node cluster.The message is as follows: The vSphere HA agent on this host has an error: The vSphere HA agent cannot be installed or configured. I have changed the vcenter, updated the esxi nodes and I still have the same problem. attached I send the errors of the vpxa.log file:

-05-07T20:32:39.450Z info vpxa[2695048] [Originator@6876 sub=vpxLro opID=kobd0t9l-45614-auto-z73-h5:70013443-c8-01-32] [VpxLRO] -- BEGIN lro-18769 -- vpxa -- vpxapi.VpxaService.Delete -- 525425d8-dcc1-0ffb-3066-73ed48a3c2cc
2021-05-07T20:32:39.450Z info vpxa[2648330] [Originator@6876 sub=vpxLro opID=kobd0t9l-45614-auto-z73-h5:70013443-c8-01-39] [VpxLRO] -- BEGIN lro-18770 -- vpxa -- vpxapi.VpxaService.Delete -- 525425d8-dcc1-0ffb-3066-73ed48a3c2cc
2021-05-07T20:32:39.451Z info vpxa[2647661] [Originator@6876 sub=vpxLro opID=kobd0t9l-45614-auto-z73-h5:70013443-c8-01-1b] [VpxLRO] -- BEGIN lro-18771 -- vpxa -- vpxapi.VpxaService.Delete -- 525425d8-dcc1-0ffb-3066-73ed48a3c2cc
2021-05-07T20:32:39.451Z info vpxa[2647657] [Originator@6876 sub=vpxLro opID=kobd0t9l-45614-auto-z73-h5:70013443-c8-01-b5] [VpxLRO] -- BEGIN lro-18772 -- vpxa -- vpxapi.VpxaService.Delete -- 525425d8-dcc1-0ffb-3066-73ed48a3c2cc
2021-05-07T20:32:39.451Z info vpxa[2647676] [Originator@6876 sub=vpxLro opID=kobd0t9l-45614-auto-z73-h5:70013443-c8-01-d4] [VpxLRO] -- BEGIN lro-18773 -- vpxa -- vpxapi.VpxaService.Delete -- 525425d8-dcc1-0ffb-3066-73ed48a3c2cc
2021-05-07T20:32:39.452Z info vpxa[2695051] [Originator@6876 sub=vpxLro opID=kobd0t9l-45614-auto-z73-h5:70013443-c8-01-f7] [VpxLRO] -- BEGIN lro-18774 -- vpxa -- vpxapi.VpxaService.Delete -- 525425d8-dcc1-0ffb-3066-73ed48a3c2cc
2021-05-07T20:32:39.452Z info vpxa[2648330] [Originator@6876 sub=vpxLro opID=kobd0t9l-45614-auto-z73-h5:70013443-c8-01-39] [VpxLRO] -- FINISH lro-18770
2021-05-07T20:32:39.452Z info vpxa[2648330] [Originator@6876 sub=Default opID=kobd0t9l-45614-auto-z73-h5:70013443-c8-01-39] [VpxLRO] -- ERROR lro-18770 -- vpxa -- vpxapi.VpxaService.Delete: vim.fault.FileNotFound:
--> Result:
--> (vim.fault.FileNotFound) {
--> faultCause = (vmodl.MethodFault) null,
--> faultMessage = <unset>,
--> file = "ds:///vmfs/volumes/60882468-fb2182fe-a746-9cdc71c15792//.vSphere-HA/FDM-5a078625-cdb0-47d3-b093-6b13888850d0-58-cae0814-vcenter7"
--> msg = ""
--> }
--> Args:
-->
--> Arg url:
--> "ds:///vmfs/volumes/60882468-fb2182fe-a746-9cdc71c15792//.vSphere-HA/FDM-5a078625-cdb0-47d3-b093-6b13888850d0-58-cae0814-vcenter7"
--> Arg fileType:
--> "File"
--> Arg recursive:
--> true
2021-05-07T20:32:39.453Z info vpxa[2647657] [Originator@6876 sub=vpxLro opID=kobd0t9l-45614-auto-z73-h5:70013443-c8-01-b5] [VpxLRO] -- FINISH lro-18772
2021-05-07T20:32:39.453Z info vpxa[2647657] [Originator@6876 sub=Default opID=kobd0t9l-45614-auto-z73-h5:70013443-c8-01-b5] [VpxLRO] -- ERROR lro-18772 -- vpxa -- vpxapi.VpxaService.Delete: vim.fault.FileNotFound:
--> Result:
--> (vim.fault.FileNotFound) {
--> faultCause = (vmodl.MethodFault) null,
--> faultMessage = <unset>,
--> file = "ds:///vmfs/volumes/58775a48-b30f27c8-ca0f-70106fb87a9a//.vSphere-HA/FDM-5a078625-cdb0-47d3-b093-6b13888850d0-58-cae0814-vcenter7"
--> msg = ""
--> }

thanks

0 Kudos
1 Solution

Accepted Solutions
Ank_S
Enthusiast
Enthusiast

Error "vsphere ha agent cannot be accessed from vcenter" could indicate network connectivity issues :

1) Check and confirm the FDM VIB is installed on the host based on https://kb.vmware.com/s/article/2011688

Run the following command :

esxcli software vib list | grep -i fdm

2) Check connectivity issues between the vCenter and ESXI host.  (Check Ping , telnet and firewall)

2) Share the vpxa and vpxd log

View solution in original post

0 Kudos
11 Replies
virtualhelp
Contributor
Contributor

Hello.

If you have the nodes in the cluster, first remove the nodes from the cluster.

it tries to activate HA, without the nodes being in the cluster.

If this doesn't work.

Drop the cluster, create a new one, enter the nodes, and activate HA.

0 Kudos
eduruizblas
Enthusiast
Enthusiast

Thanks for the reply;

I have already performed the actions you propose and it keeps failing me. Also I have created a new vcenter with a new cluster and the problems continue. The strangest thing is that this happened to me with a node that I have even changed for a new one and the same error follows in the new one.

0 Kudos
virtualhelp
Contributor
Contributor

Can you provide images to see them?

Additional attempts to restart the management agents on each host and turn HA on again.

0 Kudos
virtualhelp
Contributor
Contributor

You can also put a host in maintenance mode and add it to the cluster.

Or create the cluster, activate HA, and then drag the hosts into the cluster.

0 Kudos
amohammadimir
Enthusiast
Enthusiast

Can you share /var/log/fdm.log output from one your esxi hosts?

Please remember to mark the replies as answers if they helped.
0 Kudos
eduruizblas
Enthusiast
Enthusiast

Hi!

the fdm.log from the host that has failed me is empty. 

0 Kudos
eduruizblas
Enthusiast
Enthusiast

I have tried this too and I still do not go.

0 Kudos
Ank_S
Enthusiast
Enthusiast

Hello,

Refer the following KB and try installing the FDM VIB manually onto the ESXI hosts.

https://kb.vmware.com/s/article/2011688

 

PS: Mark kudos or correct answer as appropriate

 

0 Kudos
eduruizblas
Enthusiast
Enthusiast

eduruizblas_0-1620758390391.png

Hi! this is a capture of the error that comes out once I activate HA on the cluster

0 Kudos
Ank_S
Enthusiast
Enthusiast

Error "vsphere ha agent cannot be accessed from vcenter" could indicate network connectivity issues :

1) Check and confirm the FDM VIB is installed on the host based on https://kb.vmware.com/s/article/2011688

Run the following command :

esxcli software vib list | grep -i fdm

2) Check connectivity issues between the vCenter and ESXI host.  (Check Ping , telnet and firewall)

2) Share the vpxa and vpxd log

View solution in original post

0 Kudos
eduruizblas
Enthusiast
Enthusiast

Hi! finally solve the problem by reinstalling the fdm agent. I realized that I did not have enough space on the system partition.

0 Kudos