Hi!
I had same problem. I upgraded my vcenter appliance 6.5U2 from Build 9451637 to Build 11347054.
After rebooting, I saw this error:
(https://myvcenter.local) - 503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http20NamedPipeServiceSpecE:0x000055d5a4458ea0] _serverNamespace = / action = Allow _pipeName =/var/run/vmware/vpxd-webserver-pipe)
I checked vCenter Server Appliance Health(https://myvcenter.local:5480) and finded that: "Single Sign-On - Status Not Running"
I checked vcenter appliance services (service --status-all) and finded this:
● vmware-stsd.service - LSB: VMWare Security Token Service
....
Active: failed (Result: timeout) since Fri 2019-03-01 19:47:49 +05; 2min 9s ago
....
Failed to start LSB: VMWare Security Token Service.
vmware-stsd.service: Unit entered failed state.
vmware-stsd.service: Failed with result 'timeout'.
Increasing the timeout window to 10 seconds.. Request for http://localhost:7080/afd failed after 10 seconds. Status: /usr/bin/curl status. Response: 000. Host: ;; connection timed out; no servers could be reached. Request for http://localhost:7080/afd failed after 10 seconds. Status: /usr/bin/curl status. Response: 000. Host: ;; connection timed out; no servers could be reached. Request for http://localhost:7080/afd failed after 10 seconds. Status: /usr/bin/curl status. Response: 000. Host: ;; connection timed out; no servers could be reached. Request for http://localhost:7080/afd failed after 10 seconds. Status: /usr/bin/curl status. Response: 000. Host: ;; connection timed out; no servers could be reached. Request for http://localhost:7080/afd failed after 10 seconds. Status: /usr/bin/curl status. Response: 000. Host: ;; connection timed out; no servers could be reached. Request for http://localhost:7080/afd failed after 10 seconds. Status: /usr/bin/curl status. Response: 000. Host: ;; connection timed out; no servers could be reached.
....
Starting LSB: Start and Stop vmware-sts-idmd...
vmware-sts-idmd[2953]: ensure environment variables are set
vmware-sts-idmd[2953]: Starting VMware STS IDM Server ...failed
vmware-sts-idmd.service: Control process exited, code=exited status=1
Failed to start LSB: Start and Stop vmware-sts-idmd.
vmware-sts-idmd.service: Unit entered failed state.
vmware-sts-idmd.service: Failed with result 'exit-code'.
Then i tried restarting services, but it did't help me:
service-control --stop --all
service-control --start --all
Then i tried to find problem with LDAP and SSO service.
I checked the log (vmware-sts-idmd.log) and finded it:
cat /var/log/vmware/sso/localhost.2019-03-01.log
...
Caused by: com.vmware.identity.interop.ldap.InvalidCredentialsLdapException: Invalid credentials
LDAP error [code: 49]
at com.vmware.identity.interop.ldap.LdapErrorChecker$28.RaiseLdapError(LdapErrorChecker.java:413)
at com.vmware.identity.interop.ldap.LdapErrorChecker.CheckError(LdapErrorChecker.java:1090)
at com.vmware.identity.interop.ldap.OpenLdapClientLibrary.CheckError(OpenLdapClientLibrary.java:1241)
at com.vmware.identity.interop.ldap.OpenLdapClientLibrary.ldap_sasl_srp_bind_s(OpenLdapClientLibrary.java:769)
at com.vmware.identity.interop.ldap.LdapConnection.bindSaslSrpConnection(LdapConnection.java:670)
at com.vmware.vim.lookup.impl.LdapStorage$LdapQuery.execute(LdapStorage.java:2030)
...
Then:
cat /var/log/vmware/sso/vmware-sts-idmd.log
...
com.vmware.identity.interop.ldap.InvalidCredentialsLdapException: Invalid credentials
Caused by: com.vmware.identity.interop.ldap.InvalidCredentialsLdapException: Invalid credentials
Caused by: com.vmware.identity.interop.ldap.InvalidCredentialsLdapException: Invalid credentials
...
Then:
cat /var/log/vmware/vmdird/vmdird-syslog.log
...
VmDirSendLdapResult: Request (Bind), Error (49), Message ((49)(SASL step failed.)), (0) socket (127.0.0.1)
Bind Request Failed (127.0.0.1) error 49: Protocol version: 3, Bind DN: "cn=vcenter.vsphere.local,ou=Domain Controllers,dc=vsphere,dc=local", Method: SASL
SASLSessionStep: sasl error (-13)(SASL(-13): authentication failure: client evidence does not match what we calculated. Probably a password error)
...
The problem is invalid credentials.
I finded this article and it helped me: