Topic Name : Active Directory LDAP Server Identity Source Settings

Product/Version : VMware vSphere/6.7 Appliance

Question :

Want to add new identity source with LDAPS to our Active Directory Server. But all i tried failed.

At the moment we use windows integrated active directory setting to the same windows domain.

A check with curl to the needed ips and ports from appliance ssh root user was ok.

I get this error: Check the network settings and make sure you have network access to the identity source.

Also ports are open and firewall settings on windows were ok. ldp.exe is running on windows with port 636 and i can access and

bind with a user account.

Can someone help?

Greets Marko

Appears the new vCenter 7 appliance when deployed is not able to communicate to the default update repo url https://vapp-updates.vmware.com/vai-catalog/valm/vmw/8d167796-34d5-4899-be0a-6daade4005a3/7.0.0.10100.latest/

https://vapp-updates.vmware.com/vai-catalog/valm/vmw/8d167796-34d5-4899-be0a-6daade4005a3/7.0.0.10100.latest/

Getting an error message - Check the URL and try again

With new updates to apply to vCenter 7.0U1 showing in my console (7.0.1.00000 to 7.0.1.00100), I thought I'd update my lab. Unfortunately, I'm now stuck in a loop of failing update checks [see attached screenshots: 1) prechecks succeed, 2) SSO Admin password requested, 3) exception in precheck], and can't escape.

Even after restarting the VCSA, it stays stuck on the exception page; I can't figure out how to end this insanity!

The log I found (attached) seems to indicate that, although the prechecks pass correctly, the update engine can't find some files that should have been staged.

Help! I don't have any support options on this (it's a lab after all), and if I can avoid having to rebuild from backup (yes, I have both the pre-upgrade backup as well as the automated backups that have been running every day since deployment), it would be appreciated.

Hello

I'm trying to resolve this issue, has anyone seen this before?  Both the update screen and the main summary screen shows blank information for the appliance details, type, version etc...

Performing a check against the repository shows the No JSON object could be decoded message.

Running vpxd -v hangs and doesn't respond when I run the command.

The build I'm running is 6.5 16613358

Hello,

i am no expert, so excuse.

Yesterday, i did a fresh install of vcsa with newest aviable iso 6.7U2a (Name: VMware-VCSA-all-6.7.0-13643870.iso , Release-Datum: 2019-05-14, Build-Nummer: 13643870), using tiny installation

on a HP proliant ML110 Gen10 with esxi 6.7 (completely patched up to date).

I used tiny instalaltion (10 gb RAM).

Directly after deployment, i opened the vm appliance management site (port 5480) and checked everything. Summary --> Health Status was all green. Then, still in management site, i searched for updates via URL and downloaded and installed  the found patch (date 2019-05-30), so now the appliance has version 6.7.0.3110 (Build Number 13843380).               

Then i first opened the vsphere web client and everything seemed to be ok. After creating datacenter, joining the windows domain, adding the esxi hosts to vcenter, etc, i reopned the appliance management site and saw that under Summary --> Health Status --> RAM i have following Alarm, that appliance is running low on memory and that i should add more meory to the aplliance. Monitor showed a usage of RAm of about 86%.

I went to web client again, and here it tells that vcenter is only using about 2,5GB of the 10 GB that were assigend during tiny installation.

What i did now (although i think this is useless) to reserve the whole 10gb to the vcenter RAM. But this does not change anything. At the Moment, management site tells RAm usage of 70% (low enough to not trigger Alarm in Health Status) an web client tells usage of 2,8 GB out of 10 GB.

What is going on here? Why do management and web client show totally different RAM usage?

I also have another issue:

in vcenter web client, i get a warning saying:

vsphere Health dedected new issues in your environment. Go to Monitor -> Monitor Health for a detailed description of the issues.

Is this triggreed because of the RAM Alarm in management? I dont have any warning, alerts, problems in webclient.

thank you for helping.

Hello

My VAMI Update Manager lists 7.0.1.00000 as an available update.

Can the complete upgrade process be done though Update Manager now?

I have only tried upgrading vCenter by downloading the GUI-installer and running this through my client PC.

Thank you.

With new updates to apply to vCenter 7.0U1 showing in my console (7.0.1.00000 to 7.0.1.00100), I thought I'd update my lab. Unfortunately, I'm now stuck in a loop of failing update checks [see attached screenshots: 1) prechecks succeed, 2) SSO Admin password requested, 3) exception in precheck], and can't escape.

Even after restarting the VCSA, it stays stuck on the exception page; I can't figure out how to end this insanity!

The log I found (attached) seems to indicate that, although the prechecks pass correctly, the update engine can't find some files that should have been staged.

Help! I don't have any support options on this (it's a lab after all), and if I can avoid having to rebuild from backup (yes, I have both the pre-upgrade backup as well as the automated backups that have been running every day since deployment), it would be appreciated.

Hello,

I have 2 vcenter 6.5 servers in one sso domain.

Some time ago I have seen alarm about certificate. So i renewed all from gui, but alarm persisted.

Today I could not log in to vspere web ui, had error "User name and password are required" on the first server, and blank screen on the second one. So i restarted both. After reboot

503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http20NamedPipeServiceSpecE:0x00005567895eb3d0] _serverNamespace = / action = Allow _pipeName =/var/run/vmware/vpxd-webserver-pipe)

error is displayed.

In /var/log/vmware/messages there was error:

faultstring: The token authority rejected an issue request for TimePeriod [startTime=Fri May 08 06:42:07 UTC 2020, endTime=Fri May 08 06:52:07 UTC 2020] :: Signing certificate is not valid at Fri May 08 06:42:07 UTC 2020, cert validity: TimePeriod [startTime=Tue May 08 20:01:11 UTC 2018, endTime=Thu May 07 20:01:11 UTC 2020]

So I have decided to generate new certificates from cli with /usr/lib/vmware-vmca/bin/certificate-manager. Tried regenerating and resetting, but both operations failed when manager tried to start services. Anyway, using cmd /usr/lib/vmware-vmafd/bin/vecs-cli entry list --store MACHINE_SSL_CERT --text showed newly generated certificates.

# service-control --status

Running:

applmgmt lwsmd vmafdd vmcad vmdird vmdnsd vmonapi vmware-cis-license vmware-eam vmware-psc-client vmware-rhttpproxy vmware-sca vmware-statsmonitor vmware-sts-idmd vmware-stsd vmware-vmon vmware-vpostgres vsphere-client vsphere-ui

Stopped:

pschealth vmcam vmware-cm vmware-content-library vmware-imagebuilder vmware-mbcs vmware-netdumper vmware-perfcharts vmware-rbd-watchdog vmware-sps vmware-updatemgr vmware-vapi-endpoint vmware-vcha vmware-vpxd vmware-vpxd-svcs vmware-vsan-health vmware-vsm

Don't know where to look at, but below are some logs. Seems like something with SSO.

grep -i error /var/log/vmware/vpxd/vpxd.log

2020-05-08T12:24:43.997Z error vpxd[7F6D42D58800] [Originator@6876 sub=[SSO][SsoFactory_CreateFacade]] Unable to create SSO facade: N5Vmomi5Fault11SystemError9ExceptionE(vmodl.fault.SystemError)

2020-05-08T12:24:43.999Z error vpxd[7F6D42D58800] [Originator@6876 sub=Main] Init failed. SystemError: N5Vmomi5Fault11SystemError9ExceptionE(vmodl.fault.SystemError)

2020-05-08T12:24:43.999Z error vpxd[7F6D42D58800] [Originator@6876 sub=Default] Failed to intialize VMware VirtualCenter. Shutting down

vapi/endpoint/endpoint.log

2020-05-08T09:35:46.938Z | ERROR | state-manager1            | ComponentManagerClientWrapper  | SSO lookup failed.

java.util.concurrent.ExecutionException: com.vmware.vim.vmomi.client.exception.ConnectionException: org.apache.http.conn.HttpHostConnectException: Connect to localhost:18090 [localhost/127.0.0.1] failed: Connection refused (Connection refused)

        at com.vmware.vim.vmomi.core.impl.BlockingFuture.get(BlockingFuture.java:81)

        at com.vmware.cis.cm.client.ComponentManagerClient.lookup(ComponentManagerClient.java:876)

        at com.vmware.cis.cm.client.ComponentManagerClient$3.call(ComponentManagerClient.java:939)

        at com.vmware.cis.cm.client.ComponentManagerClient$3.call(ComponentManagerClient.java:933)

        at com.vmware.cis.cm.client.ComponentManagerClient.retry(ComponentManagerClient.java:548)

        at com.vmware.cis.cm.client.ComponentManagerClient.cachedLookup(ComponentManagerClient.java:929)

        at com.vmware.cis.cm.client.ComponentManagerClient.cachedLookup(ComponentManagerClient.java:908)

        at com.vmware.cis.cm.client.ComponentManagerClient.lookupSso(ComponentManagerClient.java:993)

        at com.vmware.vapi.endpoint.cis.ComponentManagerClientWrapper.lookupSso(ComponentManagerClientWrapper.java:171)

        at com.vmware.vapi.endpoint.cis.SsoSettingsBuilder.ssoSettings(SsoSettingsBuilder.java:171)

        at com.vmware.vapi.endpoint.cis.SsoSettingsBuilder.buildInitial(SsoSettingsBuilder.java:56)

        at com.vmware.vapi.state.impl.DefaultStateManager.build(DefaultStateManager.java:354)

        at com.vmware.vapi.state.impl.DefaultStateManager$1.doInitialConfig(DefaultStateManager.java:168)

        at com.vmware.vapi.state.impl.DefaultStateManager$1.run(DefaultStateManager.java:151)

        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

        at java.util.concurrent.FutureTask.run(FutureTask.java:266)

        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)

        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

        at java.lang.Thread.run(Thread.java:748)

Caused by: com.vmware.vim.vmomi.client.exception.ConnectionException: org.apache.http.conn.HttpHostConnectException: Connect to localhost:18090 [localhost/127.0.0.1] failed: Connection refused (Connection refused)

        at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.setError(ResponseImpl.java:256)

        at com.vmware.vim.vmomi.client.http.impl.HttpExchange.run(HttpExchange.java:51)

        ... 3 more

Caused by: org.apache.http.conn.HttpHostConnectException: Connect to localhost:18090 [localhost/127.0.0.1] failed: Connection refused (Connection refused)

        at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:140)

        at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:314)

        at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363)

        at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219)

        at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)

        at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)

        at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)

        at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:186)

        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)

        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)

        at com.vmware.vim.vmomi.client.http.impl.HttpExchange.run(HttpExchange.java:45)

        ... 3 more

Caused by: java.net.ConnectException: Connection refused (Connection refused)

        at java.net.PlainSocketImpl.socketConnect(Native Method)

        at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)

        at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)

        at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)

        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)

        at java.net.Socket.connect(Socket.java:589)

        at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:72)

        at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:117)

        ... 13 more

2020-05-08T09:35:46.941Z | ERROR | state-manager1            | SsoSettingsBuilder             | Failded to retrieve SSO settings.

com.vmware.vapi.endpoint.config.ConfigurationException: SSO lookup failed.

        at com.vmware.vapi.endpoint.cis.ComponentManagerClientWrapper.lookupSso(ComponentManagerClientWrapper.java:174)

        at com.vmware.vapi.endpoint.cis.SsoSettingsBuilder.ssoSettings(SsoSettingsBuilder.java:171)

        at com.vmware.vapi.endpoint.cis.SsoSettingsBuilder.buildInitial(SsoSettingsBuilder.java:56)

        at com.vmware.vapi.state.impl.DefaultStateManager.build(DefaultStateManager.java:354)

        at com.vmware.vapi.state.impl.DefaultStateManager$1.doInitialConfig(DefaultStateManager.java:168)

        at com.vmware.vapi.state.impl.DefaultStateManager$1.run(DefaultStateManager.java:151)

        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

        at java.util.concurrent.FutureTask.run(FutureTask.java:266)

        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)

        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

        at java.lang.Thread.run(Thread.java:748)

Caused by: com.vmware.vim.vmomi.client.exception.ConnectionException: org.apache.http.conn.HttpHostConnectException: Connect to localhost:18090 [localhost/127.0.0.1] failed: Connection refused (Connection refused)

        at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.setError(ResponseImpl.java:256)

        at com.vmware.vim.vmomi.client.http.impl.HttpExchange.run(HttpExchange.java:51)

        ... 3 more

Caused by: org.apache.http.conn.HttpHostConnectException: Connect to localhost:18090 [localhost/127.0.0.1] failed: Connection refused (Connection refused)

        at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:140)

        at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:314)

        at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363)

        at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219)

        at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)

        at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)

        at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)

        at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:186)

        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)

        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)

        at com.vmware.vim.vmomi.client.http.impl.HttpExchange.run(HttpExchange.java:45)

        ... 3 more

Caused by: java.net.ConnectException: Connection refused (Connection refused)

        at java.net.PlainSocketImpl.socketConnect(Native Method)

        at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)

        at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)

        at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)

        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)

        at java.net.Socket.connect(Socket.java:589)

        at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:72)

        at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:117)

        ... 13 more

2020-05-08T09:35:46.941Z | INFO  | state-manager1            | HealthStatusCollectorImpl      | HEALTH ORANGE Failed to retrieve SSO settings from component manager.

2020-05-08T09:35:46.941Z | ERROR | state-manager1            | DefaultStateManager            | Could not initialize endpoint runtime state.

com.vmware.vapi.endpoint.config.ConfigurationException: Failed to retrieve SSO settings.

        at com.vmware.vapi.endpoint.cis.SsoSettingsBuilder.buildInitial(SsoSettingsBuilder.java:63)

        at com.vmware.vapi.state.impl.DefaultStateManager.build(DefaultStateManager.java:354)

        at com.vmware.vapi.state.impl.DefaultStateManager$1.doInitialConfig(DefaultStateManager.java:168)

        at com.vmware.vapi.state.impl.DefaultStateManager$1.run(DefaultStateManager.java:151)

        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

        at java.util.concurrent.FutureTask.run(FutureTask.java:266)

        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)

        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

        at java.lang.Thread.run(Thread.java:748)

Caused by: com.vmware.vapi.endpoint.config.ConfigurationException: SSO lookup failed.

        at com.vmware.vapi.endpoint.cis.ComponentManagerClientWrapper.lookupSso(ComponentManagerClientWrapper.java:174)

        at com.vmware.vapi.endpoint.cis.SsoSettingsBuilder.ssoSettings(SsoSettingsBuilder.java:171)

        at com.vmware.vapi.endpoint.cis.SsoSettingsBuilder.buildInitial(SsoSettingsBuilder.java:56)

        ... 10 more

Caused by: com.vmware.vim.vmomi.client.exception.ConnectionException: org.apache.http.conn.HttpHostConnectException: Connect to localhost:18090 [localhost/127.0.0.1] failed: Connection refused (Connection refused)

        at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.setError(ResponseImpl.java:256)

        at com.vmware.vim.vmomi.client.http.impl.HttpExchange.run(HttpExchange.java:51)

        ... 3 more

Caused by: org.apache.http.conn.HttpHostConnectException: Connect to localhost:18090 [localhost/127.0.0.1] failed: Connection refused (Connection refused)

        at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:140)

        at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:314)

        at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363)

        at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219)

        at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)

        at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)

        at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)

        at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:186)

        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)

        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)

        at com.vmware.vim.vmomi.client.http.impl.HttpExchange.run(HttpExchange.java:45)

        ... 3 more

Caused by: java.net.ConnectException: Connection refused (Connection refused)

        at java.net.PlainSocketImpl.socketConnect(Native Method)

        at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)

        at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)

        at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)

        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)

        at java.net.Socket.connect(Socket.java:589)

        at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:72)

        at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:117)

        ... 13 more

2020-05-08T09:35:46.941Z | INFO  | state-manager1            | HealthStatusCollectorImpl      | HEALTH ORANGE Application error has occurred. Please check log files for more information.

2020-05-08T09:35:46.941Z | INFO  | state-manager1            | HealthStatusCollectorImpl      | HEALTH GREEN Current vApi Endpoint health status is created between 2020-05-08T09:35:46UTC and 2020-05-08T09:35:46UTC.

2020-05-08T09:35:46.941Z | INFO  | state-manager1            | HealthConfigurationEventListener | Computed health status is = ORANGE

2020-05-08T09:35:46.941Z | INFO  | state-manager1            | HealthConfigurationEventListener | HEALTH Failed to retrieve SSO settings from component manager.

2020-05-08T09:35:46.941Z | INFO  | state-manager1            | HealthConfigurationEventListener | HEALTH Application error has occurred. Please check log files for more information.

2020-05-08T09:35:46.941Z | INFO  | state-manager1            | HealthConfigurationEventListener | HEALTH Current vApi Endpoint health status is created between 2020-05-08T09:35:46UTC and 2020-05-08T09:35:46UTC.

2020-05-08T09:35:46.941Z | INFO  | state-manager1            | DefaultStateManager            | lock

2020-05-08T09:35:46.942Z | INFO  | state-manager1            | DefaultStateManager            | Initial state build failed. Will retry after 5 seconds.

2020-05-08T09:35:46.942Z | INFO  | state-manager1            | DefaultStateManager            | unlock

2020-05-08T09:35:50.607Z | INFO  | shutdown-hook             | ApiEndpointServer              | Start shutting down...

2020-05-08T09:35:50.607Z | INFO  | shutdown-hook             | DefaultStateManager            | shutdown

2020-05-08T09:35:50.614Z | INFO  | shutdown-hook             | ApiEndpointServer              | Shutdown.

But couldn't find nothing intresting in sso

sso/ssoAdminServer.log

[2020-05-08T12:24:43.988Z pool-6-thread-5 opId=21190014-abf6-4825-8234-ea672d2cdbb0 ERROR com.vmware.vim.vmomi.server.http.impl.CompletionContinuerTask] Failed to serialize response

com.vmware.vim.binding.vmodl.fault.SystemError: Failed to serialize response

        at com.vmware.vim.vmomi.server.exception.ExceptionUtil.buildFaultForInternalException(ExceptionUtil.java:22) ~[vlsi-server.jar:?]

        at com.vmware.vim.vmomi.server.http.impl.CompletionContinuerTask.complete(CompletionContinuerTask.java:95) [vlsi-server.jar:?]

        at com.vmware.vim.vmomi.server.http.impl.CompletionContinuerTask.complete(CompletionContinuerTask.java:63) [vlsi-server.jar:?]

        at com.vmware.vim.vmomi.server.http.impl.CompletionContinuerTask.run(CompletionContinuerTask.java:53) [vlsi-server.jar:?]

        at com.vmware.vim.vmomi.server.common.impl.RunnableWrapper$1.run(RunnableWrapper.java:47) [vlsi-server.jar:?]

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_221]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_221]

        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_221]

Caused by: com.vmware.vim.vmomi.core.exception.MarshallException: Missing non-optional return value

        at com.vmware.vim.vmomi.server.impl.SoapBindingImpl.serializeResponse(SoapBindingImpl.java:168) ~[vlsi-server.jar:?]

        at com.vmware.vim.vmomi.server.http.impl.CompletionContinuerTask.complete(CompletionContinuerTask.java:84) ~[vlsi-server.jar:?]

        ... 6 more

sso/vmware-identity-sts.log //still some problem with certificate?

[2020-05-08T12:58:34.733Z tomcat-http--39 vsphere.local        97b81203-5e98-4499-b11f-1f5b6ade0789 INFO  com.vmware.identity.sts.ws.SOAPFaultHandler] Returning a SOAP Fault with code: ns0:InvalidTimeRange and description: The token authority rejected an issue request for TimePeriod [startTime=Fri May 08 12:58:34 UTC 2020, endTime=Fri May 08 13:08:34 UTC 2020] :: Signing certificate is not valid at Fri May 08 12:58:34 UTC 2020, cert validity: TimePeriod [startTime=Tue May 08 20:01:11 UTC 2018, endTime=Thu May 07 20:01:11 UTC 2020]

sso/lookupServer.log

[2020-05-08T08:09:40.314Z ERROR] [OpenLdapClientLibrary] Exception when calling ldap_search_s: base=cn=4cea3f17-670c-4ee6-938c-c7e1aaec7cfe,cn=ServiceRegistrations,cn=LookupService,cn=silp,cn=sites,cn=configuration,dc=vsphere,dc=local, scope=2, filter=(objectclass=*), attrs=null, attrsonly=0

com.vmware.identity.interop.ldap.NoSuchObjectLdapException: No such object

Any help would be appreciated

I'm trying to migrate the storage of a virtual machine to a different datastore. (on the same san)

When I start the job I see the task :

Relocating virtual machine / Status 'In Progress'

After 10 minutes I get 2 popups :

-

Error

-

Cannot connect to host.

-

OK

-

I tried to move the storage from a different virtual machine, but I got the same error.

Also tried from a different vmhost (but same cluster) but also the same error.

When trying from a host in a different cluster It works without problems (same san/datastore used in the cluster where I got the errors)

There are no difference in the security profile on the hosts.

Any hints ?

Attached logfile (vpxd-353.log) when I was running the migrate storage.

Error part :

2009-11-03 16:49:07.035 02464 info 'App' (1257263347020035) VMotion started

2009-11-03 16:58:35.903 02464 error 'App' (1257263347020035) VMotion failed: vim.fault.HostConnectFault

When it runs ok :

2009-11-03 17:29:49.470 02456 info 'App' (1257265789470153) VMotion started

I upgraded from vCenter Server Appliance 6.7 to 7.0 (specifically 7.0.0a build 16189094) and when I go to Administration > Certificate Management in the vSphere client, I get the following error:

Is anyone else seeing this issue? Does anyone know of a fix?

Thanks

Dear All

I found that the inventory service is not starting up and look up the log in C:\ProgramData\VMware\vCenterServer\logs\vpostgres

The DB status is always in "starting up" with FATAL. Does anyone know how to fix it? Please find attached logs.

2019-10-08 14:28:33.079 HKT 5d9c2c91.a0c 0 VCDB vc FATAL:  the database system is starting up

2019-10-08 14:29:48.425 HKT 5d9c0db9.2104 0   LOG:  received fast shutdown request

2019-10-08 15:09:16.702 HKT 5d9c361c.2790 0   LOG:  database system was interrupted while in recovery at 2019-10-08 12:16:58 HKT

2019-10-08 15:09:16.702 HKT 5d9c361c.2790 0   HINT:  This probably means that some data is corrupted and you will have to use the last backup for recovery.

2019-10-08 15:10:02.234 HKT 5d9c361c.2790 0   LOG:  database system was not properly shut down; automatic recovery in progress

2019-10-08 15:10:02.241 HKT 5d9c361c.2790 0   LOG:  redo starts at 41/83FE29B8

2019-10-08 15:10:05.853 HKT 5d9c361c.2790 0   LOG:  redo done at 41/85FFF6D8

2019-10-08 15:10:05.853 HKT 5d9c361c.2790 0   LOG:  last completed transaction was at log time 2019-10-06 05:45:05.252+08

2019-10-08 15:20:42.924 HKT 5d9c361c.2370 0   LOG:  received fast shutdown request

2019-10-08 15:25:05.862 HKT 5d9c39d1.1870 0   LOG:  database system was interrupted while in recovery at 2019-10-08 15:10:02 HKT

2019-10-08 15:25:05.862 HKT 5d9c39d1.1870 0   HINT:  This probably means that some data is corrupted and you will have to use the last backup for recovery.

2019-10-08 15:25:09.850 HKT 5d9c39d1.1870 0   LOG:  database system was not properly shut down; automatic recovery in progress

2019-10-08 15:25:09.874 HKT 5d9c39d1.1870 0   LOG:  redo starts at 41/83FE29B8

2019-10-08 15:25:14.612 HKT 5d9c39d1.1870 0   LOG:  redo done at 41/85FFF6D8

2019-10-08 15:25:14.618 HKT 5d9c39d1.1870 0   LOG:  last completed transaction was at log time 2019-10-06 05:45:05.252+08

2019-10-08 15:25:25.159 HKT 5d9c39e5.1ad4 0 VCDB vc FATAL:  the database system is starting up

2019-10-08 15:36:04.705 HKT 5d9c3c64.8b8 0 VCDB vc FATAL:  the database system is starting up

2019-10-08 15:36:59.679 HKT 5d9c3c9b.1d8c 0 VCDB vc FATAL:  the database system is starting up

2019-10-08 15:38:25.192 HKT 5d9c3cf1.270 0 VCDB vc FATAL:  the database system is starting up

2019-10-08 15:42:38.272 HKT 5d9c3dee.1648 0 VCDB vc FATAL:  the database system is starting up

2019-10-08 15:43:14.428 HKT 5d9c3e12.1f4c 0 VCDB vc FATAL:  the database system is starting up

I have upgraded to vCenter Server with an embedded Platform Services Controller version 6.7.0.42200.  The service your update manager is there and running, however to normal way to access the feature is not there.  The update tab for the hosts is also missing.

Any help would be much appreciated!

Hello

I'm trying to resolve this issue, has anyone seen this before?  Both the update screen and the main summary screen shows blank information for the appliance details, type, version etc...

Performing a check against the repository shows the No JSON object could be decoded message.

Running vpxd -v hangs and doesn't respond when I run the command.

The build I'm running is 6.5 16613358

Anyone know why a 6.7 vCenter appliance would fail to accept new solution user certificates in both the UI and the CLI (Certificate-Manager)?

Specifics:

- 6.7U3C vCenter appliance in Enhanced-Linked mode

- Machine SSL certificate replaced without issue

- The VPXD, VPDX-extension, machine, and vsphere-webclient certificates will not replace

- There are no wild cards in the certificates [SANs or CNs, etc.]

- All of the vCenters in the environment have the same certificate templates and are the same, but they were upgraded to 6.7. This one is new.

The certificates were generated using open-ssl.

The template uses 4096, what should be the proper enhanced attributes, includes the corresponding type in the CN [e.g. machine-FQDN, VPXD-FQDN, etc.].

This is really odd.

GB

Hello,

I'm starting the learning process on the VMWare platform with a home lab setup. ESXI 6.5 is installed on my server and I am able to successfully manage the system via the web interface. However, I'd like to explore some of the options present in the vCenter Server application. However, I'm unable to locate the correct download for this product.

Pressing the "Get vCenter Server" button from the ESXI web interface does not direct to the correct link.

Browsing through the downloads page seems to be the correct location but I do not have permissions to download: https://my.vmware.com/en/group/vmware/downloads/details?downloadGroup=VC65U3K&productId=614&rPId=50173

Message: You either are not entitled or do not have permissions to download this product. Check with your My VMware Super User, Procurement Contact or Administrator. If you recently purchased this product thorugh VMware Store or through a third party, try downloading later.

I'm looking for help in 1 of 2 ways:

1. Describe how to obtain permissions required for downloading the product from the link below

2. If the link below is not the right approach, please redirect me to a download location for the client interface that I install on my desktop PC.

Download Link I tried:

https://my.vmware.com/en/group/vmware/downloads/details?downloadGroup=VC65U3K&productId=614&rPId=50173

Version of ESXi

ESXi 6.5 A03 (based on ESXi VMKernel Release Build 5310538)

Hi

I have a cluster that consist of 6 hosts where manual vmotion works fine, but when I put my hosts in Maintenance mode, it just doesn't vmotion the vm's to the other hosts in the cluster. This problem started after we had some major network problems and every host have been rebooted after the network problem was solved. I've done vmkping and looked in different logs without finding any clues. Any idea on how to fix this (so that I can update to Update 2 without putting to much manual work into it)?

Anders

Hello,

i have deploy a new VCSA 7U1. I will start the initial setup over the Web UI https://vcsa.domain.de:5480.

I can login and click to set up. So good. But on the Step 2 vCenter Configuration came the failure : Unable to Save IP-Settings

The Wizard go not forward? Have anyone a idea?

I updated vcsa 6.5 to build 4944578 (released 2/2/2017) and the management interface was not working after the update.  Poking around I found that the vami-lighttp service startup was failing.  Looking further it was complaining it couldn't bind to an IPv6 address.  hmmm...   Further checking found there were complaints being spit out about the config file.  So I checked /opt/vmware/etc/lighttpd/lighttpd.conf and there was a duplicate entry for server.use-ipv6 = "disable", with the 2nd occurrence coming on the last line of the file.  I commented this last line out and restarted the service.  Bingo, it works.

Including here so anyone else that hits this problem can find my solution.

Hi,

I recently rebooted my vcsa appliance and after waiting a while for all services to start up my VMware vSphere Web Client started showing the following error message:

503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http20NamedPipeServiceSpecE:0x000055fcde997a60] _serverNamespace = / action = Allow _pipeName =/var/run/vmware/vpxd-webserver-pipe)

I took a look at rhttpproxy.log file and it showed the following output:

2019-03-11T14:07:23.814+01:00 warning rhttpproxy[11879] [Originator@6876 sub=Default] Failed to connect socket; <io_obj p:0x00007f98b0001fa0, h:19, <TCP '127.0.0.1 : 36346'>, <TCP '127.0.0.1 : 8089'>>, e: 111(Connection refused)

2019-03-11T14:07:23.814+01:00 warning rhttpproxy[11879] [Originator@6876 sub=Proxy Req 00601 Tunnel] Error connecting tunnel on TCP socket: (null): Connection refused: The remote service is not running, OR is overloaded, OR a firewall is rejecting connections.

2019-03-11T14:07:29.139+01:00 warning rhttpproxy[11871] [Originator@6876 sub=Default] Failed to connect socket; <io_obj p:0x00007f98a80172d8, h:19, <UNIX ''>, <UNIX '/var/run/vmware/vpxd-webserver-pipe'>>, e: 111(Connection refused)

2019-03-11T14:07:29.139+01:00 warning rhttpproxy[11871] [Originator@6876 sub=Proxy Req 00602] Connection to named pipe /var/run/vmware/vpxd-webserver-pipe failed with error N7Vmacore15SystemExceptionE(Connection refused: The remote service is not running, OR is overloaded, OR a firewall is rejecting connections.)

--> [context]zKq7AVECAQAAAPJSnAAOcmh0dHBwcm94eQAAlLAqbGlidm1hY29yZS5zbwAAIDcbAG67GAD35yIAPIwlAISUJQAasSUA4bolAGlRIwChHiMAaiEjAB0IKwHUcwBsaWJwdGhyZWFkLnNvLjAAAp2MDmxpYmMuc28uNgA=[/context].

Which according to VMware Knowledge Base means that there is a certificate error. When I try resetting all certificates using /usr/lib/vmware-vmca/bin/certificate-manager, the following error message appears:

Status : 0% Completed [Reset Root Cert...]                 

Using config file : /var/tmp/vmware/root.cfg

Error: 382312694, VMCAAddRootCertificatePrivate() failedError: 382312694, Failed to add root certificate

Status : Failed

Error Code : 382312694

Error Message : Access denied, reason = rpc_s_auth_method (0x16c9a0f6).

Status : 0% Completed [Reset operation failed]

please see /var/log/vmware/vmcad/certificate-manager.log for more information.

Does anyone have any advice on how to solve this issue?

Hi can anyone explain the difference between the 2?