You can check your /VAR/LOG repository and see what happen ?
Please post results
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.
2010-04-13 14:54:49.327 'Proxysvc' 19573680 warningSSL Handshake on client connection failed: SSL Exception: error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate 2010-04-13 14:54:55.547 'Proxysvc' 19307440 warningSSL Handshake on client connection failed: SSL Exception: error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate 2010-04-13 14:54:57.669 'ha-eventmgr' 69319600 infoEvent 38 : User firstname.lastname@example.org logged in 2010-04-13 14:54:57.976 'VmMisc' 41147312 warningFailed to find conversion from winServer2008Datacenter-64 to type: vim.vm.GuestOsDescriptor.GuestOsIdentifier 2010-04-13 14:54:58.101 'ha-eventmgr' 3076440992 infoEvent 39 : User root logged out 2010-04-13 14:55:01.609 'ha-eventmgr' 19573680 infoEvent 40 : User email@example.com logged in 2010-04-13 14:55:01.942 'TaskManager' 18922416 infoTask Created : haTask-ha-folder-root-vim.host.LocalAccountManager.createUser-50 2010-04-13 14:55:01.956 'TaskManager' 18922416 infoTask Completed : haTask-ha-folder-root-vim.host.LocalAccountManager.createUser-50 2010-04-13 14:55:01.956 'Vmomi' 18922416 infoActivation N5Vmomi10ActivationE:0x8e4f880 : Invoke done on vim.host.LocalAccountManager:ha-localacctmgr 2010-04-13 14:55:01.957 'Vmomi' 18922416 infoThrow vim.fault.AlreadyExists 2010-04-13 14:55:01.957 'Vmomi' 18922416 infoResult:
dynamicType = <unset>,
name = "vpxuser",
msg = ""
2010-04-13 14:55:01.992 'TaskManager' 19839920 infoTask Created : haTask-ha-folder-root-vim.host.LocalAccountManager.updateUser-51 2010-04-13 14:55:04.972 'TaskManager' 19839920 infoTask Completed : haTask-ha-folder-root-vim.host.LocalAccountManager.updateUser-51 2010-04-13 14:55:04.976 'TaskManager' 19573680 infoTask Created : haTask--vim.AuthorizationManager.setEntityPermissions-52 2010-04-13 14:55:04.977 'TaskManager' 19573680 infoTask Completed : haTask--vim.AuthorizationManager.setEntityPermissions-52 2010-04-13 14:55:05.013 'ha-eventmgr' 69319600 infoEvent 41 : User root logged out 2010-04-13 14:55:05.059 'ha-eventmgr' 19573680 infoEvent 42 : User firstname.lastname@example.org logged in 2010-04-13 14:55:05.253 'ha-eventmgr' 19839920 infoEvent 43 : User vpxuser logged out 2010-04-13 14:55:05.371 'ha-eventmgr' 18656176 infoEvent 44 : User email@example.com logged in 2010-04-13 14:55:05.376 'ha-eventmgr' 18922416 infoEvent 45 : User vpxuser logged out 2010-04-13 14:55:05.394 'ha-eventmgr' 18922416 infoEvent 46 : User firstname.lastname@example.org logged in 2010-04-13 14:55:05.401 'ha-eventmgr' 18922416 infoEvent 47 : User vpxuser logged out 2010-04-13 14:55:05.411 'ha-eventmgr' 19573680 infoEvent 48 : User email@example.com logged in 2010-04-13 14:55:05.430 'Vmomi' 41147312 infoActivation N5Vmomi10ActivationE:0x97b5140 : Invoke done on vmodl.query.PropertyCollector:ha-property-collector 2010-04-13 14:55:05.430 'Vmomi' 41147312 infoThrow vmodl.query.InvalidProperty 2010-04-13 14:55:05.430 'Vmomi' 41147312 infoResult:
dynamicType = <unset>,
name = "licenses",
msg = ""
2010-04-13 14:55:07.578 'VmMisc' 19839920 warningFailed to find conversion from winServer2008Datacenter-64 to type: vim.vm.GuestOsDescriptor.GuestOsIdentifier 2010-04-13 14:55:08.672 'App' 19839920 errorFailed to send response to the client: Broken pipe
Please restart the vcenter server service.....
VCP 3&4, MCTS(Hyper-V), SNIA SCP.
Please award points, if helpful
geddam I'v already tried that, it did not help.
Kasper- did you get any resolution on this? I just had the same thing happen to me... running vCenter 4, and a standalone ESX host running ESX 3.5. Host is running fine, restarted mgmt-vmware and vmware-vpxa services. DNS name resolution is fine (DNS server is fine, host file as a backup is fine, checked DNS PTR records as well). About to put int a trouble ticket weith VMware... just not looking forweard to the wait, and then having to go through all the steps I just went through trroubleshooting on my own, and then never getting an answer back from tech support.
did you get a fix for this from vmware after you logged a support ticket ?
You also give a try by removing the host from VC and adding it back again, this will not trouble your VM's, You can also have a look at the following link which will help you to reinstall the vcenter agent.
NOTE: If your problem or questions has been resolved / answered, please mark this thread as answered and award points accordingly.
I ended up shutting down all of the VM's, and upgrading the server to ESX 4.0 U2. I wasn't sure if the update would work- I have two other standalone ESX servers that I cannot upgrade. Hoping that this issue doesn't hit those other servers. Pulling the server out of the VC and putting it back in did not work, or removing and reinstalling the HA agent didn't work (in fact, I couldn't reinstall the HA manually or by adding back to VC). DNS is working fine, name resolution is working fine. The only thing I didn't try was making sure I was patched to 3.5 U5. I tried the update to 4.0, and it worked, so no need to try the patch to 3.5 U5.
I had this same/similar problem on ESXi 4.1. VMware tech support fixed it with the following internal only procedure. Hope this helps someone.
1. Select the ESX in vCenter
2. Click on the "Configuration" tab and select "System Resource Allocation"
3. Under "System Resource Pools", select "host", then "vim", then "Edit Settings"
4. When the "Edit vim Resource Allocaation" window opens, set the "Memory Resources" Limit to "Unlimited"
Had the same error today on an ESX 3.5.0 build 82663 server, it disconnected from the Cluster it was in and wouldn't connect in VCentre
An internal error vmodl.fault.HostConnection. It then went through the wizard of adding a host but failed at 9%
Rebooted ESX host and same fault when trying to connect in VCentre. I could connect directly to the ESX host itself and see the hosts (all down)
I had to reboot our server hosting VCentre and then connect worked straight away on this ESX host
VCentre was the issue for my fault
I had the same issues, the solution? I Log on to the console (in my case throgh HP ilo - remote console) and them restart the management agents (in thoubleshooting options).
Any other option causes a down of the service.
4 years later, but, now you have the real answer
Bloody hell this actually works! Might be 4 years late for OP but certainly helped the others in future! Thanks alot! BTW im on Vcenter 5.5 with esxi host 5.5
i have esxi 5.5 & VC 5.5 too, all of sudden all 5 nodes had same issue.
dns is fine
also tried the mgmt network restart from console, no luck
I'm using esxi5.1.x and found the following solution to work after a couple previously mentioned solutions failed my case:
Log in directly to each host via vSphere despite them being technically managed by VC server. You'll get the popup that says it's managed (even though it's not showing up in vSphere via VC anymore...) so just click through that nonsense.
On the Summary tab, there's a section called Host Management in the bottom right. If your hosts are still thinking they're associated with the VC server, it should say "This host is currently managed by vCenter Server a.b.c.d and you'll have the Disassociate host from vCenter Server... option.
Disassociate each host one by one and when you go back in through vSphere via the main VC login, you should be able to successfully re-add each host without issue.
Hope this helps @esxi1979 and anyone else dealing with inexplicable vmware BS