VirtualCenter is not homed.  But the vpxd logs on virtualcenter do seem to indicate that it's a cert issue with the host.

Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client -- BEGIN task-internal-60678 -- host-9655 -- VpxdInvtHostSyncHostLRO.Synchronize

Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client Synchronizing host: hqgtnesx23 (10.23.1.83)

Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client Failed to send request. Retrying. Error: class Vmacore::Ssl::SSLException(SSL Exception: error:00000001:lib(0):func(0):reason(1))

Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:

• A certificate in the host's chain is based on an untrusted root.

Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the error

Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client Retrieved host update to 8233

When we say 'cert on host' we mean the ESX host? (in this case 23).  How do you delete the cert? I don't know where it's located.  I could try deleting it, then restarting the mgmt-vmware service like you suggested.

A few updates for those interested. 

I've removed/readded hosts from virtualcenter, and it hasn't fixed anything.  I've rebuilt one of the esx hosts and it hasn't fixed anything.  I did however notice that the issue I'm having currently isn't 'when selected' as I put in the title.  It just seemed that way.  It does it pretty much whenever it wants, on as many hosts as it wants, but only ever for a few seconds.   Looking at the times that it happens against the hostd.log doesn't show much, but virutalcenter does.

Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client Queuing 10.23.1.91:790 (host-13521)

Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client 502c3559-cecb-ec0d-81ef-24445bacea25:790 (host-13521)

Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client Need inventory sync for: host-13521

Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client Queuing sync LRO for: /vpx/host/#13521/

Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client -- BEGIN task-internal-172795 -- host-13521 -- VpxdInvtHostSyncHostLRO.Synchronize

Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client Synchronizing host: hqgtnesx31 (10.23.1.91)

Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client Failed to send request. Retrying. Error: class Vmacore::Ssl::SSLException(SSL Exception: error:00000001:lib(0):func(0):reason(1))

Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:

• A certificate in the host's chain is based on an untrusted root.

Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the error

Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client Got vmacore exception: SSL Exception: error:00000001:lib(0):func(0):reason(1)

Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client Backtrace:

backtrace[00] eip 0x0122b526 ?GenerateCoreDump@System@Vmacore@@YAXXZ

backtrace[01] eip 0x01176caa ?CreateBacktrace@SystemFactoryImpl@System@Vmacore@@UAEXAAV?$Ref@VBacktrace@System@Vmacore@@@3@@Z

backtrace[02] eip 0x0115192e ??0Throwable@Vmacore@@QAE@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z

backtrace[03] eip 0x01141b38 ??4Throwable@Vmacore@@QAEAAV01@ABV01@@Z

backtrace[04] eip 0x0117e254 ?InitServer@Authd@Vmacore@@YAXABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@0@Z

backtrace[05] eip 0x011d7e1f ?CreateSSLContext@Ssl@Vmacore@@YAXPAVKeyStore@Crypto@2@W4SupportedVersion@12@AAV?$Ref@VSSLContext@Ssl@Vmacore@@@2@@Z

backtrace[06] eip 0x011d7f3b ?CreateSSLContext@Ssl@Vmacore@@YAXPAVKeyStore@Crypto@2@W4SupportedVersion@12@AAV?$Ref@VSSLContext@Ssl@Vmacore@@@2@@Z

backtrace[07] eip 0x011d8364 ?CreateSSLContext@Ssl@Vmacore@@YAXPAVKeyStore@Crypto@2@W4SupportedVersion@12@AAV?$Ref@VSSLContext@Ssl@Vmacore@@@2@@Z

backtrace[08] eip 0x011d55c6 ?CreateSSLContext@Ssl@Vmacore@@YAXPAVKeyStore@Crypto@2@W4SupportedVersion@12@AAV?$Ref@VSSLContext@Ssl@Vmacore@@@2@@Z

backtrace[09] eip 0x0118ce06 ?CreateHttpConnectionPool@Http@Vmacore@@YAXHAAV?$Ref@VHttpConnectionPool@Http@Vmacore@@@2@@Z

backtrace[10] eip 0x0115bbff ?CreateElementNode@Xml@Vmacore@@YAXABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@0AAV?$Ref@VElementNode@Xml@Vmacore@@@2@@Z

backtrace[11] eip 0x013a618a ?CreateSoapSerializationVisitor@Vmomi@@YAXPAVVersion@1@PAVWriter@Vmacore@@AAV?$Ref@VSerializationVisitor@Vmomi@@@4@PBD_N@Z

backtrace[12] eip 0x013a6332 ?CreateSoapSerializationVisitor@Vmomi@@YAXPAVVersion@1@PAVWriter@Vmacore@@AAV?$Ref@VSerializationVisitor@Vmomi@@@4@PBD_N@Z

backtrace[13] eip 0x013a81ff ?CreateSoapStubAdapter@Vmomi@@YAXABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@HPAVSSLContext@Ssl@Vmacore@@00PAVLogger@Service@6@AAV?$Ref@VStubAdapter@Vmomi@@@6@@Z

backtrace[14] eip 0x013a9051 ?CreateSoapStubAdapter@Vmomi@@YAXABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@HPAVSSLContext@Ssl@Vmacore@@00PAVLogger@Service@6@AAV?$Ref@VStubAdapter@Vmomi@@@6@@Z

backtrace[15] eip 0x00510d11 (no symbol)

backtrace[16] eip 0x0051169f (no symbol)

backtrace[17] eip 0x00511af1 (no symbol)

backtrace[18] eip 0x013779ce ?_Invoke_Task@StubImpl@Vmomi@@UAEXPAVManagedMethod@2@AAV?$RefVector@VAny@Vmomi@@@Vmacore@@AAV?$Ref@VAny@Vmomi@@@5@@Z

backtrace[19] eip 0x008630a2 (no symbol)

backtrace[20] eip 0x0053b0e5 (no symbol)

backtrace[21] eip 0x0053bad8 (no symbol)

backtrace[22] eip 0x006d5df6 (no symbol)

backtrace[23] eip 0x006dad6e (no symbol)

backtrace[24] eip 0x006e0e04 (no symbol)

backtrace[25] eip 0x00a1c06a (no symbol)

backtrace[26] eip 0x77e64829 GetModuleHandleA

Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client Host sync on hqgtnesx31 in progress, waiting..

Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client pool:0, 9 out of 10 connections are available

Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client Recording (285c1c8:0) UPDATE VPX_HOST SET BOOT_TIME = ? , MAINTENANCE_MODE = ? , POWER_STATE = ? WHERE ID = ?

Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client host connection state changed to Re: Issues with ESX hosts not responding WHEN SELECTED in VI Client

I haven't tried the cert rebuilding as was suggested before because I've nuilt new esx hosts, and they are having the same issue..  The certs aren't really important to me, that's why they're disabled.  Is it possible that it's an issue with the cert on the virtualcenter server? Should I try recreating that? Would it affect anything?

I added the certs from each host to the trusted stores on virtualcenter.  Even though they were the generic mock certs and there shouldn't have been a problem, it fixed it.

Both errors disappeared when I added the 'mock' certs from the ESX hosts to the Trusted Root Authorities cert store on the VirtualCenter server.

That fixed the issue for me.  The other thing I looked into was the 'ProxySVC' errors that  I was getting on the ESX hosts, and as it turns out, if you turn the VirtualCenter logging level to 'trivial' you capture ProxySVC events in the VirtualCenter logs.That may help.

I added the certs from /etc/vmware/ssl

I took the rui.crt from each vmware server and put them on the virtualcenter server

Then opened up the mmc, added certificates as a snap-in, and selected 'this computer' when it asked me which cert store I wanted to use.  I then selected 'personal certificates, right clicked on it, and 'imported' each of the certificates.

At that point, when I double clicked on the rui.crt on the hard drive of the virtual center server, I didn't have a trusted cert chain error.  Instead it was trusted

Then the logs with the SSL exception stopped appearing.