Good afternoon,
I am getting the following error when attempting to launch vSphere client HTML5:
503 Service Unavailable (Failed to connect to endpoint: [class Vmacore::Http::LocalServiceSpec:0x0000001993b01430] _serverNamespace = /ui action = Allow _port = 5090)
That error is basically useless since it can either be expected while the service is starting up, or can mean just about anything. You need to look at the logs on the vcenter server its self
What should I be specifically looking for within the logs....it is definitely not because we are waiting for it to start up.....
please check which service failed to start
ssh to vcsa or use shell
service-control --status --all
share the output to us
based on the services down, we need to isolate which service is down like vapi-endpoint,vpxd-svcs, vpxd or vsphere-ui.. and check the relevant service logs in /var/log/vmware folder
thanks,
MS
Here is what I get when running that command:
C:\Program Files\VMware\vCenter Server\bin>service-control --status --all
Running:
EsxAgentManager VMWareAfdService VMWareCertificateService VMWareDirectoryService VMwareComponentManager VMwareDNSService VMwareIdentityMgmtService VMwareSTS VServiceManager rhttpp
roxy vPostgres vapiEndpoint vimPBSM vmon vmonapi vmsyslogcollector vmware-autodeploy-waiter vmware-cis-config vmware-license vmware-perfcharts vmware-psc-client vmwareServiceContro
lAgent vpxd vpxd-svcs vsan-health vspherewebclientsvc
Stopped:
VMWareCAMService content-library mbcs vmware-imagebuilder vmware-network-coredump vsphere-ui
C:\Program Files\VMware\vCenter Server\bin>
Could you try to run: service-control --stop --all and service-control --start --all to see which service fails to initialize?
Which service log should I pull?
That depends on what service is the one failing when you try to start all of them.
Not saying this is the issue, but looks the error, you need to look for something similar
com.vmware.vise.extensionfw.impl.PackagesDeployer Error deploying one of more bundles for the plugin package C:\ProgramData\VMware\vCenterServer\runtime\vsphere-ui\plugin-packages\license-client java.lang.Exception: Timed out waiting for a bundle to start.
at com.vmware.vise.extensionfw.impl.DirectApiBundleDeployer.waitForBundlesStart(DirectApiBundleDeployer.java:98)
at com.vmware.vise.extensionfw.impl.DirectApiBundleDeployer.deploy(DirectApiBundleDeployer.java:58)
[2018-10-19T11:28:47.557+08:00] [ERROR] plugin-deploy2 org.eclipse.virgo.medic.eventlog.default XF1009E Failed to deploy plugin package 'com.vmware.license.client' version '6.5.0.10000'.
[2018-10-19T11:38:48.014+08:00] [ERROR] ng DM Context Creation Timer org.eclipse.virgo.medic.eventlog.default AG0000E Application context creation failure for bundle 'com.vmware.license.client-6.5.0.10000-com.vmware.license.client.licenseservice' version '6.5.0.13000'. org.springframework.context.ApplicationContextException: Application context initialization for 'com.vmware.license.client-6.5.0.10000-com.vmware.license.client.licenseservice' has timed out waiting for (objectClass=org.springframework.beans.factory.config.Scope)
see how these "at com.vmware" these types of errors stand out compared to the rest of the errors. You should be looking at vsphere-ui which is the logs I mentioned, and that service looked stopped based on the output you've provided so far.
Looking at the vsphere_Client_virgo log and finding this:
[2020-08-26T09:41:49.630-04:00] [INFO ] -extension-manager-pool-1408 70008432 100361 200243 com.vmware.vise.extensionfw.impl.PackagesDeployer Could not resolve dependencies for plugins packages: [ com.vmware.fallback.mixed:6.5.0 requires: [ com.vmware.vsphere.client lessThan 6.0.2 ]; ];
is it windows 2016?
Windows 2012 R2 Standard
ok thanks, you can try the steps in kb article for sure..
I tried the KB article resolution at the bottom of the article and still getting the same issue. I guess at this point it is time to open a support call.
If the issue persist, perform the below steps:
pickup.deployer=true