MontanaBoy
Contributor
Contributor

ESX 4 Host disconnected from VC and Can't connect to ESX Host via vSphere client

I Also can't connect to the default Webpage of the ESX Host

I have tried to restart the VC agent and the SC with the following commands

service vmware-vpxa restart

service mgmt-vmware restart

I checked the vpxa.log file and there are many errors See Below:

Failed to discover version: vim.fault.HttpFault

Could not resolve version for authenticating to host agent

Creating temporary connect spec: localhost:443

SSLStreamImpl::BIORead (0xcf7c560) timed out

SSLStreamImpl::DoClientHandshake (0xcf7c560) SSL_connect failed with BIO Error

Error in sending request - SSL Exception: The SSL handshake timed out local: 127.0.0.1:40139 peer: 127.0.0.1:443.

Failed to discover version: vim.fault.HttpFault

Could not resolve version for authenticating to host agent

Creating temporary connect spec: localhost:443

SSLStreamImpl::BIORead (0xcf7c560) timed out

SSLStreamImpl::DoClientHandshake (0xcf7c560) SSL_connect failed with BIO Error

Any Ideas?

0 Kudos
7 Replies
MontanaBoy
Contributor
Contributor

I forgot to mention I tried connecting via the IP address as to avoid any DNS type issues and it still won't connect

0 Kudos
bulletprooffool
Champion
Champion

MontanaBoy - by default, web access is not enabled in vSphere -to enabkle i, have a look at:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=101192...

One day I will virtualise myself . . .
0 Kudos
MontanaBoy
Contributor
Contributor

I actually wasn't trying to login to ESX with Web Access I was only trying to connect to the webpage that every ESX Host has by default. I am not sure what the page it is called but there is a link on the page to download the vSphere client. See the attached Screen shot it has the web page I am trying to reach.

Also, I am actually not very concern about this page I just noticed I can't open it up.

0 Kudos
MontanaBoy
Contributor
Contributor

Well I broke down and opened a Service Call. The issue appears to be with a Defunked Process called Hostd. We tried to kill the process but it wouldn't kill. I have been asked to reboot the Host server. I will have to schedule this reboot as I have many Guests running on the Host and it isn't in a DRS cluster. I will post with an update after the reboot.

0 Kudos
MontanaBoy
Contributor
Contributor

The reboot fixed the issue. Normally I wouldn't have a problem with rebooting an ESX Host if it is part of a DRS cluster, but this server was not part of a DRS Cluster so I had to bring down all my Guests for the reboot.

0 Kudos
PanVlad
Contributor
Contributor

Hi,

I got the same problem, but resolved it with two commands from management console:

esxcfg-rescan vmhba34

Then restart management service:

/etc/init.d/mgmt-vmware restart

It helped me do not reboot ESX server, and renewed connectivity to the virtual center.

0 Kudos
JGP
Contributor
Contributor

Also had similar problem after the upgrade vCenter Server to v4.1

3 Hosts (VMware ESX 4.0.0 build-261974) managed by the VC, 1 host with a (soft)iSCSI adapter (hba32).

The two hosts without iSCSI storage connected to the new VC without any problem.

The host with iSCSIconfigured failed toconnect to VC.

Error in /var/log/vmwaer/vpx/vpxa.log:

Error in sending request - Operation timed out

Failed to discover version: vim.fault.HttpFault

Could not resolve version for authenticating to host agent

Creating temporary connect spec: localhost:443

running:

esxcfg-rescan vmhba32

solved the problemand and no reboot needed

0 Kudos