During previous vSphere JumpStart training I wasn’t able to show VMware HA feature to my students since we were having some issue to enable it though message shown “HA agent has an error” in vCenter is well known to me. Due to time constraint during the session,troubleshooting is not an option so I left it as is and planning to troubleshoot it when I come back to my office.
First I need to identify the root cause of this problem by login to ESX host using putty. Knowing all log files should be sitting in the same folder like previous ESX, I’m starting to locate the “aam” folder with this two commands :
- #cd /var/log
- #find -name aam
You should get the same output as mine which is “vmware/aam”. Then, I locate my ESX host file from this folder and read it with command “tail -n 100 vmware/aam/vmware_esx01.log”.
Fortunately, from this log, I found out that it had something to do with “procMon”. So, I go to procmon folder and read another log (esx01_fatal.out) and found something that I already suspected before:
- Error Type - 1
- Message - Unable To Get Fully Qualified Domain Name
Now the rest should be easy from here. Since I resolving my domain name using /etc/hosts instead of DNS server, I verify my /etc/hosts entry. What the “F”, all entries are there. But, when I run this two commands, I noticed that I forgot something in my /etc/hosts ;
- #hostname –fqdn
- #hostname -a
After this, I managed to reconfigure VMware HA for problematic ESX host successfully without issue.
athlon_crazy 14/10/2009 7:34am
1 Comment so far
Leave a comment