Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Cannot enable vCenter Hardware Status and vCenter Service Status plugin in vSphere Client several hours after restarting vCenter Server service on vCenter server appliance.After restarting the vCenter Server service, these plugins can be enabled. However, they cannot be enabled after a period of time.In the VCSA log localhost_access_log file located at /var/log/vmware/vsphere-client/, these script plugin xml files no longer appear as available: XXX.XXX.XXX.XXX - - [04/Feb/2014:20:26:25 +0900] "GET /cim-ui/scriptConfig.xml HTTP/1.1" 200 641 XXX.XXX.XXX.XXX - - [04/Feb/2014:20:26:25 +0900] "GET /health-ui/scriptConfig.xml HTTP/1.1" 200 864 XXX.XXX.XXX.XXX - - [04/Feb/2014:20:44:15 +0900] "GET /cim-ui/scriptConfig.xml HTTP/1.1" 200 641 XXX.XXX.XXX.XXX - - [04/Feb/2014:20:44:15 +0900] "GET /health-ui/scriptConfig.xml HTTP/1.1" 200 864 In the vpxd.log file located at /var/log/vmware/vpx/ , you see entries similar to: [7FC5BB7DC700 warning 'vpxdvpxdMoHost'] [HostMo::GetLinkedVmInt] Getting linked vm for vmid 13 on host esxi.corp.local - COULD NOT FIND IT [7FC5BB7DC700 info 'vmcheckclusterChecker'] [CheckChangePropertiesInt] Property added/deleted [7FC5BB7DC700 error 'utilvpxdDbUpdate'] [VpxdDbUpdate] Update for 'modified' property config.tools.lastInstallInfo not currently managed. [7FC5BB7DC700 error 'utilvpxdDbUpdate'] Update for property tools.lastInstallInfo failed [7FC5BB7DC700 error 'utilvpxdDbUpdate'] [VpxdDbUpdate] ProcessDataObject: XmlPath = hardware.device.slotInfo property is missing in XML mapping file [7FC5BB7DC700 error 'utilvpxdDbUpdate'] [VpxdDbUpdate] ProcessDataObject: XmlPath = hardware.device.slotInfo property is missing in XML mapping file [7FC5BB7DC700 error 'utilvpxdDbUpdate'] [VpxdDbUpdate] ProcessDataObject: XmlPath = hardware.device.slotInfo property is missing in XML mapping file [7FC5BB7DC700 error 'utilvpxdDbUpdate'] [VpxdDbUpdate] ProcessDataObject: XmlPath = hardware.device.slotInfo property is missing in XML mapping file [7FC5E045E700 info 'commonvpxLro' opID=BC75AD6C-00000022-44] [VpxLRO] -- BEGIN task-internal-55519 -- -- vmodl.query.PropertyCollector.createFilter -- a5fbae2a-d09a-2ac4-65d6-424e46c76b80(52b19ee7-0174-0009-89aa-51d097e33efe) [7FC5E045E700 info 'commonvpxLro' opID=BC75AD6C-00000022-44] [VpxLRO] -- FINISH task-internal-55519 -- -- vmodl.query.PropertyCollector.createFilter -- [7FC5BB7DC700 error 'utilvpxdDbUpdate'] [VpxdDbUpdate] ProcessDataObject: XmlPath = initialOverhead property is missing in XML mapping file [7FC5AF617700 info 'commonvpxLro' opID=D6F60229-0000036B-f5-1b-30-77] [VpxLRO] -- BEGIN task-internal-55537 -- -- VmTestDriver -- [7FC5BB07F700 error 'httphttpUtil'] [HttpUtil::ExecuteRequest] Error in sending request - Operation timed out [7FC5BB07F700 error 'ServerAccess'] Remote login failed: N3Vim5Fault9HttpFault9ExceptionE(vim.fault.HttpFault) [7FC5BB07F700 error 'vpxdvpxdHealth'] [VpxdHealthServiceMonitor::LoginToHealthService] Unable to login into HealthService. Error is vmodl.fault.HostCommunication [7FC5BB07F700 warning 'VpxProfiler'] VpxUtil_InvokeWithOpId [TotalTime] took 120003 ms [7FC5AFFBE700 error 'Default'] SSLStreamImpl::BIORead from SSL(TCPClientSocket(this=00007fc564a07170, state=CONNECTED, _connectSocket=TCP(null), error=(null)) TCP(local= XXX.XXX.XXX.XXX :56015, peer= XXX.XXX.XXX.XXX :8443)) timed out [7FC5AFFBE700 error 'Default'] SSLStreamImpl::DoClientHandshake for SSL(no stream): SSL_connect failed with BIO Error [7FC5AFFBE700 error 'HttpConnectionPool-000189'] [ConnectComplete] Connect failed to <cs p:00007fc564dd19a0, TCP:/esxi.corp.local:8443>; cnx: (null), error: N7Vmacore3Ssl28SSLHandshakeTimeoutExceptionE(SSL Exception: The SSL handshake timed out local: XXX.XXX.XXX.XXX :56015 peer: XXX.XXX.XXX.XXX:8443.) [7FC5AF617700 info 'commonvpxLro' opID=D6F60229-0000036B-f5-1b-30-77] [VpxLRO] -- FINISH task-internal-55537 -- -- VmTestDriver -- Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
To resolve this issue, reconfigure the JVM heap size in the Virtual Appliance Management Interface (VAMI).For more information on reconfiguring the JVM heap size manually, see vCenter Server Appliance fails to reconfigure JVM settings when the memory size of the virtual machine on which it resides is modified (2066099).
VMware vCenter Server Appliance fails to reconfigure JVM settings when the memory size of the virtual machine on which it resides is modified