A General System Error Occurred Internal Error Vmodl.fault
NSXVirtual SAN vCenterFusionWorkstationvExpertVMware {code} CloudCredSubmit a Link Home > VMTN > VMware Infrastructureâ„¢ > VI: VMware ESXâ„¢ 3.5 > Discussions Please enter a title. You can not post a blank message. Please type your message and try again. 14 Replies Latest reply: Sep 3, 2015 9:59 AM by rcmessner A general system error occurred: internal error: vmodl.fault.HostCommunication kasperottesen Apr 13, 2010 3:37 AM Hi,Yesterday one of my hosts in a HA Cluster suddenly went into disconnected status. I tried to connect it again but got the above message in a popup. I tried to restart mgmt-vmware and vmware-vpxa agents and then tried to connect it again, same error.I have tried to manual uninstall and install vpx agent but still no help.I have checked DNS and network settings, everything looks fine. I cant reboot the host since I have production VMs running on it.Anyone seen this before and came up with a solution?Detais about my setup:vCenter 4.0ESX 3.5 U2- Kasper 34454Views Tags: none (add) This content has been marked as final. Show 14 replies 1. Re: A general system error occurred: internal error: vmodl.fault.HostCommunication Shakayumi Apr 13, 2010 5:15 AM (in response to kasperottesen) Hello, You can check your /VAR/LOG repository and see what happen ?Please post resultsThanks Like Show 0 Likes (0) Actions 2. Re: A general system error occurred: internal error: vmodl.fault.HostCommunication kasperottesen Apr 13, 2010 6:06 AM (in response to Shakayumi) Yeah sure, here are som copy from hostd.log. I know there are SSL Exception, this one started after I tried to rebuild the certifcates.Let me know if you want to see more logs or a specific log file. I forgot to say that i tried to copy these to lines into vpxa.cfg, but everytime I reconnect it removes the two lines again.
Cisco Cloud CrossFit ESX ESXi feature goals Homelab Linux Load balancer logging Log Insight Mac NAS Network Review Script Security SSL Storage Synology syslog Travel UCS vCenter Server vCS VMworld vR Ops vSphere Windows This is the personal website of Steve Flanders. The opinions expressed here are mine and may or may http://sflanders.net/2011/04/03/a-general-system-error-occurred-internal-error-vmodl-fault-hostcommunication/ not be the same as my employer. Search for: A general system error occurred internal error vmodl.fault.HostCommunication April 3, 2011Steve Flanders I am in the process of building my home lab. I recently purchased two servers and installed ESXi 4.1 on them. In addition, I deployed a test vCenter Server instance so I could run VUM. With vCenter Server up, I attempted to add the two ESXi servers. The first one added without issue, but the a general second one failed with the error messages:Cannot complete the configuration of the HA agent on the host. See the task details for additional information.Misconfiguration in the host network setupI verified that the hosts were in fact configured identically and then tried to add the host again, but the same error messages were displayed. Based on the error messages, I found the following KB article: http://kb.vmware.com/kb/1019200. Unfortunately, the link did not help.Next, I removed the ESXi host a general system from vCenter Server and tried to re-add it. This time I got a different error message:A general system error occurred internal error vmodl.fault.HostCommunicationFrom this error message I found KB article: http://kb.vmware.com/kb/1012154. This article pointed to name resolution (i.e. DNS) being my issue. I know of the importance of DNS with VMware products and was sure I had verified its configuration, but decided to double check. As suspected, DNS was configured and working as expected.At this point, I decided to restart the management services as that fixes a majority of ESX(i) issues. Upon doing so and trying to add the ESXi server to vCenter Server, I received another new error message:Unable to access the specified host, either it doesn't exist, the server software is not responding, or there is a network problemThis error message pointed me to KB article: http://kb.vmware.com/kb/1003409.Again I tried everything suggested and was still receiving the same error message. At this point, I was frustrated. I decided to reboot the server just in case that fixed the issue. Upon restarting, the error message want back to the vmodl.fault.HostCommuncation one.What was going on and how could this be fixed?At this point I was out of ideas and needed to log into the ESXi host to figure out what was going on. VMware typically recommends that if you need to log into the ESXi host then you s