Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
The vmware-vpxd to start on the vCenter Server Appliance.The vSphere Web Client displays this error: 503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http20NamedPipeServiceSpecE:0x7fec10092390] _serverNamespace = / _isRedirect = false _pipeName =/var/run/vmware/vpxd-webserver-pipe) The time on the vCenter Server Appliance and/or the ESXi host on which it resides is incorrect.In the /var/log/vmware/vpxd.log file, you see entries similar to: 2015-07-15T11:52:22.578Z error vpxd[7F95B3F907A0] [Originator@6876 sub=componentManagerUtil] AcquireToken for solution (vpxd-7688deef-a858-4ff9-ba2d-41184d324096@vsphere.local): SsoException: Authentication failed: Invalid credentials 2015-07-15T11:52:22.579Z error vpxd[7F95B3F907A0] [Originator@6876 sub=licenseServiceDiscovery] Failed to discover license service endpoint: N9SsoClient27InvalidCredentialsExceptionE(Authentication failed: Invalid credentials) 2015-07-15T11:52:22.584Z warning vpxd[7F95B3F907A0] [Originator@6876 sub=VpxProfiler] ServerApp::Init [TotalTime] took 4023 ms 2015-07-15T11:52:22.584Z error vpxd[7F95B3F907A0] [Originator@6876 sub=Main] [VpxdMain] Failed to initialize N9SsoClient27InvalidCredentialsExceptionE(Authentication failed: Invalid credentials) 2015-07-15T11:52:22.584Z error vpxd[7F95B3F907A0] [Originator@6876 sub=Default] Failed to intialize VMware VirtualCenter. Shutting down... 2015-07-15T11:52:22.584Z info vpxd[7F95B3F907A0] [Originator@6876 sub=SupportMgr] Wrote uptime information 2015-07-15T11:54:22.586Z info vpxd[7F95B3F907A0] [Originator@6876 sub=Default] Forcing shutdown of VMware VirtualCenter now In the vmware-identity-sts.log file, you see entries similar to: [2015-07-15T12:44:05.888Z tomcat-http--33 vsphere.local 1afb7188-03a2-4c47-bf58-d67852643137 TRACE com.vmware.identity.perf] 'idm.findSolutionUserByCertDn' took 8 ms. [2015-07-15T12:44:05.888Z tomcat-http--33 vsphere.local 1afb7188-03a2-4c47-bf58-d67852643137 DEBUG com.vmware.identity.sts.InvalidCredentialsException] About to censor authentication failurecom.vmware.identity.sts.InvalidCredentialsException: Solution user cert is not valid. at com.vmware.identity.sts.auth.impl.BSTAuthenticator.checkValidCertificate(BSTAuthenticator.java:139) at com.vmware.identity.sts.auth.impl.BSTAuthenticator.doAuthenticate(BSTAuthenticator.java:103) at com.vmware.identity.sts.auth.impl.BSTAuthenticator.authenticate(BSTAuthenticator.java:71) at com.vmware.identity.sts.auth.impl.CompositeAuthenticator.authenticate(CompositeAuthenticator.java:44) Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
This is occurs if there is a time skew between the vCenter Server Appliance and the ESXi host in which the appliance currently resides.
To resolve this issue, correct the time on the vCenter Server Appliance and/or the ESXi host. For more information on configuring NTP on the vCenter Server Appliance, see Configuring NTP on the vCenter Server Appliance 6.0 (2113610) and Synchronizing ESXi/ESX time with a Microsoft Domain Controller (1035833). To manually set the time in the vCenter Server Appliance: Log in as root through an SSH or console session on the vCenter Server Appliance.Run this command to enable the shell: shell.set --enabled true Run this command to launch the shell: shell Run this command to set the time: date --set="DD MONTH YYYY HH:MM:SS" For example: date --set="25 January 2015 22:11:01"
Synchronizing ESXi/ESX time with a Microsoft Domain ControllerConfiguring NTP on the vCenter Server Appliance 6.0VMware VirtualCenter Server 服务未能在 VMware vCenter Server Appliance 6.0 上启动，并报告以下错误： 未能发现许可证服务端点VMware vCenter Server Appliance 6.0 で VMware VirtualCenter Server サービスの開始に失敗し、次のエラーが報告される： ライセンス サービス エンドポイントを検索できませんでした