VMware Cloud Community
Adam231
Contributor
Contributor

[500] SSO error: Cannot connect to the VMware Component Manager

Hi,

Hopefully someone might be able to point me in the right direction here, I'm a bit out of my depth....

I have a LAB setup of 3x ESXi hosts, on one of which vcenter is installed.

All the ESXi hosts were added and everything was working very well. I needed to change the IP addressing of the network the three ESXi/vcenter hosts were on. Initially there was no problem, moved form 192.168.1.x/24 to 192.168.100.x/24. Again, initially everything seemed ok.

I think the problem I am now getting, which is when trying to access vsphere web client I get '[500] SSO error: Cannot connect to the VMware Component Manager', started after the VM hosting vcenter rebooted, though I can't be certain of this.

I've seen posts suggesting a requirement for entries in the hosts file of the vcenter server if forward/reverse DNS isnt working, but it is. I came across another post suggesting to reset the certificates using the certificate-manager.bat command, which I've tried but with no luck error stays the same after services/server reboot.

I pulled the vsphere-client-virgo.log but the only thing I could see in it was an entry of: failed: Connection refused: connect

In case it helps I've pasted the section below;

[2017-02-15T14:16:25.874Z] [INFO ] Timer-0                      com.vmware.vise.util.debug.SystemUsageMonitor                    Summary: heap = 269.95 MB, threads = 87

Heap    : init = 134217728(131072K) used = 283060008(276425K) committed = 376438784(367616K) max = 557842432(544768K)

non-Heap : init = 2555904(2496K) used = 189541640(185099K) committed = 210223104(205296K) max = -1(-1K)

No of loaded classes: 22227

Live Thread Count(w/o the live daemon threads): 6

Peak Thread Count: 90

Daemon Thread Count: 81

Tomcat Request-Processing Threads Count: 20

Blocked threads: 0

Waiting threads: 80

Threads blocked in Data Service: 0

Threads waiting in Data Service: 0

Threads blocked in Logback: 0

Threads waiting in Logback: 0

[2017-02-15T14:21:25.911Z] [INFO ] Timer-0                      com.vmware.vise.util.debug.SystemUsageMonitor                    Summary: heap = 289.84 MB, threads = 87

Heap    : init = 134217728(131072K) used = 303914664(296791K) committed = 376438784(367616K) max = 557842432(544768K)

non-Heap : init = 2555904(2496K) used = 189541640(185099K) committed = 210223104(205296K) max = -1(-1K)

No of loaded classes: 22227

Live Thread Count(w/o the live daemon threads): 6

Peak Thread Count: 90

Daemon Thread Count: 81

Tomcat Request-Processing Threads Count: 20

Blocked threads: 0

Waiting threads: 80

Threads blocked in Data Service: 0

Threads waiting in Data Service: 0

Threads blocked in Logback: 0

Threads waiting in Logback: 0

[2017-02-15T14:23:34.228Z] [INFO ] http-bio-9443-exec-2        70000007 100002 ###### com.vmware.vise.util.i18n.I18nFilter                              The preferred locale for session 100002 is set to: en_US

[2017-02-15T14:23:34.250Z] [INFO ] http-bio-9443-exec-2        70000007 100002 ###### com.vmware.vise.vim.security.sso.impl.SsoCmLocatorImpl            Fetching SSO endpoints from CM

[2017-02-15T14:23:34.266Z] [INFO ] http-bio-9443-exec-2        70000007 100002 ###### com.vmware.vise.vim.cm.impl.ComponentManagerServiceImpl          Creating a CMServiceHolder for URI https://myserver.mydomain.local/cm/sdk?hostid=5d6bdf00-db61-11e6-9a06-000c299e8cce

[2017-02-15T14:23:36.295Z] [INFO ] http-bio-9443-exec-2        70000007 100002 ###### com.vmware.vise.vim.cm.impl.ComponentManagerServiceImpl          Retry won't be attempted for CM https://myserver.mydomain.local/cm/sdk?hostid=5d6bdf00-db61-11e6-9a06-000c299e8cce for error: com.vmware.vim.vmomi.client.exception.ConnectionException - org.apache.http.conn.HttpHostConnectException: Connect to myserver.mydomain.local:443 [myserver.mydomain.local/192.168.x.x, myserver.mydomain.local/fe80:0:0:0:4858:3366:c0:39df%8] failed: Connection refused: connect

[2017-02-15T14:23:36.300Z] [ERROR] http-bio-9443-exec-2        70000007 100002 ###### com.vmware.vise.vim.cm.impl.ComponentManagerServiceImpl          Error when creating component manager service: https://myserver.mydomain.local/cm/sdk?hostid=5d6bdf00-db61-11e6-9a06-000c299e8cce com.vmware.vim.vmomi.client.exception.ConnectionException: org.apache.http.conn.HttpHostConnectException: Connect to myserver.mydomain.local:443 [myserver.mydomain.local/192.168.x.x, myserver.mydomain.local/fe80:0:0:0:4858:3366:c0:39df%8] failed: Connection refused: connect

Any help would be greatly appreciated!

4 Replies
RajeevVCP4
Expert
Expert

I resolved same issue for my customer , but before giving solution want to know these things

No need reset certificate ,

Are you using vcenter server appliances or window based vcenter server

Which version/build of are you using

are all components installed on single virtual machine or are you using external sso

Rajeev Chauhan
VCIX-DCV6.5/VSAN/VXRAIL
Please mark help full or correct if my answer is use full for you
0 Kudos
kuenzir
Contributor
Contributor

Same issue here, please provide the solution.

vCenter Appliance 6.0.0.20000

All components on one VM.

0 Kudos
RajeevVCP4
Expert
Expert

Check nslookup result from vcsa (putty) it can be because reverse lookup zone not configured properly . Check this log.

vsphere-client-virgo.log for web-client under /var/log/vmware/vsphere-client


if you will get there.


java.net.NoRouteToHostException: No route to host


Then you need to check you DNS setting try this command


command “service-control –stop -all ” and  “service-control –start -all ”

Rajeev Chauhan
VCIX-DCV6.5/VSAN/VXRAIL
Please mark help full or correct if my answer is use full for you
ECarvan
Contributor
Contributor

All,

     We have this same issue where several of the services would not start. 

2018-11-13T17:56:33.218-06:00 [main INFO  com.vmware.sca.registration.Services] Found 21 services: [perfcharts, netdumper, vmcam, vmonapi, vmsyslogcollector, vsphere-ui, vapi-endpoint, rhttpproxy, eam, vpxd, vsm, cis-license, imagebuilder, rbd, vpxd-svcs, mbcs, sps, vsphere-client, vsan-health, fallback, content-library]

vsphere-ui, vapi-endpoint, eam, imagebuilder, vsphere-client, and content-library were the services that wouldn't start.

We added the below users to the local “Logon as a batch” group.

Cm; content-library; eam; imagebuilder; mbcs; netdumper; perfcharts; rbd; vapiEndpoint; vsan-health; vsm; vsphere-client; vsphere-ui

This fixed the services not starting issue.

0 Kudos