onichan
Mar 14, 2018, updated at 13:19:15 (UTC)
view6016
view2
0
Goto Top

VCenter Server 6.5 Webinterface nicht mehr lauffähig

GermansolvedQuestionVMwareVirtualization
Moin zusammen,

aufgrund eines Stromausfalls sind letztens unsere ESX Hosts heruntergefahren und seitdem funktioniert das vCenter Webinterface nicht mehr.
Der vCenter Server kommt, je nachdem, welche URL man aufruft, mit den folgenden Fehlermeldungen um die Ecke:

Infos zur Umgebung:
vCenter 6.5
ESXi 6.0 Server

Im C:\ProgramData\VMware\vCenterServer\logs\vsphere-client\logs\vsphere_client_virgo.log finden sich folgende Fehler:

[2018-03-14T10:06:01.925+01:00] [ERROR] CEIPSynchronizerTimer         com.vmware.vise.vim.cm.impl.ComponentManagerServiceImpl           Error when creating component manager service: https://HOSTNAME.DOMAIN.local/cm/sdk?hostid=dd46da30-9f8e-11e7-8424-000c295fcfc1 com.vmware.vim.vmomi.client.common.UnexpectedStatusCodeException: Unexpected status code: 503
	at com.vmware.vim.vmomi.client.common.Response$Status.getStatus(Response.java:58)
	at com.vmware.vim.vmomi.client.http.impl.HttpExchangeBase.parseResponse(HttpExchangeBase.java:150)
	at com.vmware.vim.vmomi.client.http.impl.HttpExchange.run(HttpExchange.java:48)
	at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingBase.executeRunnable(HttpProtocolBindingBase.java:226)
	at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingImpl.send(HttpProtocolBindingImpl.java:110)
	at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.sendCall(MethodInvocationHandlerImpl.java:613)
	at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.executeCall(MethodInvocationHandlerImpl.java:594)
	at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.completeCall(MethodInvocationHandlerImpl.java:345)
	at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invokeOperation(MethodInvocationHandlerImpl.java:305)
	at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invoke(MethodInvocationHandlerImpl.java:179)
	at com.sun.proxy.$Proxy159.retrieveServiceInstanceContent(Unknown Source)
	at com.vmware.vise.vim.cm.impl.ComponentManagerServiceImpl.getComponentManager(ComponentManagerServiceImpl.java:658)
	at com.vmware.vise.vim.cm.impl.ComponentManagerServiceImpl.getComponentManager(ComponentManagerServiceImpl.java:573)
	at com.vmware.vise.vim.cm.impl.ComponentManagerServiceImpl.searchSso(ComponentManagerServiceImpl.java:209)
	at com.vmware.vise.vim.security.sso.impl.SsoCmLocatorImpl.getSsoServerInfo(SsoCmLocatorImpl.java:148)
	at com.vmware.vise.vim.security.sso.impl.SsoServiceImpl.getServerInfo(SsoServiceImpl.java:416)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319)
	at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.doInvoke(ServiceInvoker.java:56)
	at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:60)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
	at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
	at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
	at org.eclipse.gemini.blueprint.service.importer.support.LocalBundleContextAdvice.invoke(LocalBundleContextAdvice.java:57)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
	at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
	at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
	at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
	at com.sun.proxy.$Proxy370.getServerInfo(Unknown Source)
	at com.vmware.ph.ceip.authentication.DsSessionSimulatorImpl$TokenProvider.createSolutionStsClient(DsSessionSimulatorImpl.java:260)
	at com.vmware.ph.ceip.authentication.DsSessionSimulatorImpl$TokenProvider.createToken(DsSessionSimulatorImpl.java:243)
	at com.vmware.ph.ceip.authentication.DsSessionSimulatorImpl.simulate(DsSessionSimulatorImpl.java:117)
	at com.vmware.ph.ceip.impl.Synchronizer$1.run(Synchronizer.java:71)
	at java.util.TimerThread.mainLoop(Timer.java:555)
	at java.util.TimerThread.run(Timer.java:505)

[2018-03-14T10:06:01.935+01:00] [ERROR] CEIPSynchronizerTimer         com.vmware.ph.ceip.authentication.DsSessionSimulatorImpl          There was an error while getting SSO Server information and we cannot access the SSO Server. As a result no token can be acquired for solution user: vpxd-extension For more information see the SsoService logs and the underlying exception: Cannot connect to the VMware Component Manager https://HOSTNAME.DOMAIN.local/cm/sdk?hostid=dd46da30-9f8e-11e7-8424-000c295fcfc1 com.vmware.vise.vim.cm.ComponentManagerConnectionException: Cannot connect to the VMware Component Manager https://HOSTNAME.DOMAIN.local/cm/sdk?hostid=dd46da30-9f8e-11e7-8424-000c295fcfc1
	at com.vmware.vise.vim.cm.impl.ComponentManagerServiceImpl.getComponentManager(ComponentManagerServiceImpl.java:690)
	at com.vmware.vise.vim.cm.impl.ComponentManagerServiceImpl.getComponentManager(ComponentManagerServiceImpl.java:573)
	at com.vmware.vise.vim.cm.impl.ComponentManagerServiceImpl.searchSso(ComponentManagerServiceImpl.java:209)
	at com.vmware.vise.vim.security.sso.impl.SsoCmLocatorImpl.getSsoServerInfo(SsoCmLocatorImpl.java:148)
	at com.vmware.vise.vim.security.sso.impl.SsoServiceImpl.getServerInfo(SsoServiceImpl.java:416)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319)
	at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.doInvoke(ServiceInvoker.java:56)
	at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:60)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
	at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
	at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
	at org.eclipse.gemini.blueprint.service.importer.support.LocalBundleContextAdvice.invoke(LocalBundleContextAdvice.java:57)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
	at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
	at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
	at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
	at com.sun.proxy.$Proxy370.getServerInfo(Unknown Source)
	at com.vmware.ph.ceip.authentication.DsSessionSimulatorImpl$TokenProvider.createSolutionStsClient(DsSessionSimulatorImpl.java:260)
	at com.vmware.ph.ceip.authentication.DsSessionSimulatorImpl$TokenProvider.createToken(DsSessionSimulatorImpl.java:243)
	at com.vmware.ph.ceip.authentication.DsSessionSimulatorImpl.simulate(DsSessionSimulatorImpl.java:117)
	at com.vmware.ph.ceip.impl.Synchronizer$1.run(Synchronizer.java:71)
	at java.util.TimerThread.mainLoop(Timer.java:555)
	at java.util.TimerThread.run(Timer.java:505)
Caused by: com.vmware.vim.vmomi.client.common.UnexpectedStatusCodeException: Unexpected status code: 503
	at com.vmware.vim.vmomi.client.common.Response$Status.getStatus(Response.java:58)
	at com.vmware.vim.vmomi.client.http.impl.HttpExchangeBase.parseResponse(HttpExchangeBase.java:150)
	at com.vmware.vim.vmomi.client.http.impl.HttpExchange.run(HttpExchange.java:48)
	at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingBase.executeRunnable(HttpProtocolBindingBase.java:226)
	at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingImpl.send(HttpProtocolBindingImpl.java:110)
	at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.sendCall(MethodInvocationHandlerImpl.java:613)
	at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.executeCall(MethodInvocationHandlerImpl.java:594)
	at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.completeCall(MethodInvocationHandlerImpl.java:345)
	at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invokeOperation(MethodInvocationHandlerImpl.java:305)
	at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invoke(MethodInvocationHandlerImpl.java:179)
	at com.sun.proxy.$Proxy159.retrieveServiceInstanceContent(Unknown Source)
	at com.vmware.vise.vim.cm.impl.ComponentManagerServiceImpl.getComponentManager(ComponentManagerServiceImpl.java:658)
	... 28 common frames omitted

[2018-03-14T10:06:01.972+01:00] [ERROR] CEIPSynchronizerTimer         com.vmware.ph.ceip.impl.Synchronizer                              Global consent status synchronizer has stopped unexpectedly. As a result the local consent state will not be synchronized with other consent states. To recover please verify/fix the exact reason in the cause exception and restart the service java.lang.RuntimeException: There was an error while getting SSO Server information and we cannot access the SSO Server. As a result no token can be acquired for solution user: vpxd-extension For more information see the SsoService logs and the underlying exception: Cannot connect to the VMware Component Manager https://HOSTNAME.DOMAIN.local/cm/sdk?hostid=dd46da30-9f8e-11e7-8424-000c295fcfc1
	at com.vmware.ph.ceip.authentication.DsSessionSimulatorImpl$TokenProvider.createSolutionStsClient(DsSessionSimulatorImpl.java:271)
	at com.vmware.ph.ceip.authentication.DsSessionSimulatorImpl$TokenProvider.createToken(DsSessionSimulatorImpl.java:243)
	at com.vmware.ph.ceip.authentication.DsSessionSimulatorImpl.simulate(DsSessionSimulatorImpl.java:117)
	at com.vmware.ph.ceip.impl.Synchronizer$1.run(Synchronizer.java:71)
	at java.util.TimerThread.mainLoop(Timer.java:555)
	at java.util.TimerThread.run(Timer.java:505)
Caused by: com.vmware.vise.vim.cm.ComponentManagerConnectionException: Cannot connect to the VMware Component Manager https://HOSTNAME.DOMAIN.local/cm/sdk?hostid=dd46da30-9f8e-11e7-8424-000c295fcfc1
	at com.vmware.vise.vim.cm.impl.ComponentManagerServiceImpl.getComponentManager(ComponentManagerServiceImpl.java:690)
	at com.vmware.vise.vim.cm.impl.ComponentManagerServiceImpl.getComponentManager(ComponentManagerServiceImpl.java:573)
	at com.vmware.vise.vim.cm.impl.ComponentManagerServiceImpl.searchSso(ComponentManagerServiceImpl.java:209)
	at com.vmware.vise.vim.security.sso.impl.SsoCmLocatorImpl.getSsoServerInfo(SsoCmLocatorImpl.java:148)
	at com.vmware.vise.vim.security.sso.impl.SsoServiceImpl.getServerInfo(SsoServiceImpl.java:416)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319)
	at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.doInvoke(ServiceInvoker.java:56)
	at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:60)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
	at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
	at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
	at org.eclipse.gemini.blueprint.service.importer.support.LocalBundleContextAdvice.invoke(LocalBundleContextAdvice.java:57)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
	at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
	at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
	at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
	at com.sun.proxy.$Proxy370.getServerInfo(Unknown Source)
	at com.vmware.ph.ceip.authentication.DsSessionSimulatorImpl$TokenProvider.createSolutionStsClient(DsSessionSimulatorImpl.java:260)
	... 5 common frames omitted
Caused by: com.vmware.vim.vmomi.client.common.UnexpectedStatusCodeException: Unexpected status code: 503
	at com.vmware.vim.vmomi.client.common.Response$Status.getStatus(Response.java:58)
	at com.vmware.vim.vmomi.client.http.impl.HttpExchangeBase.parseResponse(HttpExchangeBase.java:150)
	at com.vmware.vim.vmomi.client.http.impl.HttpExchange.run(HttpExchange.java:48)
	at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingBase.executeRunnable(HttpProtocolBindingBase.java:226)
	at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingImpl.send(HttpProtocolBindingImpl.java:110)
	at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.sendCall(MethodInvocationHandlerImpl.java:613)
	at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.executeCall(MethodInvocationHandlerImpl.java:594)
	at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.completeCall(MethodInvocationHandlerImpl.java:345)
	at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invokeOperation(MethodInvocationHandlerImpl.java:305)
	at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invoke(MethodInvocationHandlerImpl.java:179)
	at com.sun.proxy.$Proxy159.retrieveServiceInstanceContent(Unknown Source)
	at com.vmware.vise.vim.cm.impl.ComponentManagerServiceImpl.getComponentManager(ComponentManagerServiceImpl.java:658)
	... 28 common frames omitted

Google spuckt hier auch nicht wirklich viel aus bzw ich bin einfach zu dumm um Google zu benutzen ;P

Was hab ich bisher gemacht:
Reboot: ohne Erfolg
Dienste verifiziert: laufen alle
Restore von Backup: Ich befürchte, dass der Fehler bereits gebackupt wurde....
Zeitkonfiguration geprüft: auf den ESX Hosts hat der NTP Server gefehlt, ich habe ihn eingepflegt aber es gibt immer noch eine 1 Std. Differenz, da die ESX Hosts in der UTC Zeitzone stecken.

Hat noch jemand gute Ideen oder hatte den Fehler schon mal?

Vielen Dank

Grüße
Oni
comment-contentCommentShareShare
Share on Facebook Share on Twitter Share on Reddit Share on Linkedin

Content-Key: 367993

Url: https://administrator.de/contentid/367993

Printed on: April 25, 2024 at 10:04 o'clock

2 Comments
Latest comment
Goto Top
Member: Voiper
Voiper Mar 14, 2018 updated at 12:20:30 (UTC)
Goto Top
Moin,

was sagt denn der Hersteller dazu?

Edit: Google Treffer Nummer 1: https://kb.vmware.com/s/article/2121043 ist wohl das, was du oben gemacht hast

Gruß, V
Member: GrueneSosseMitSpeck
Solution GrueneSosseMitSpeck Mar 14, 2018 at 12:33:13 (UTC)
Goto Top
Das Sichern und wiederherstellen der SSO-Datenbank im SSO-Server ist genauso frickelig wie das Sichern der ESX Hostkonfiguration ohne VCenter Verwaltung face-sad Hantieren mit Textdateien...

Ich würd mir mal nen alten Vsphere Client besorgen, der sich direkt am ESX Host anmelden kann, von da aus kann man sich dann weiterhangeln.
Den VCenter Server - falls er denn läuft - müßte man vorher wohl per SSH Kommandozeile runterfahren, weil der Host sonst rummeckert daß er von einem Vcenter aus verwaltet wird und ohne SSO ist halt kein Login möglich face-sad Ohne Vcenter und ohne SSO Server geht das aber (zumindestens noch beim ESX 6.0).

Mit dem alten Client kann man aber wenigstens seinen Host verwalten und weitere Diangosen betreiben, was auf der Konsolenebene echt mühsam ist. Vermutlich ist die Datenbank im SSO Server zerschosse, oder es ist noch eine Stufe fieser, wenn der SSO die in Windows integrierte Datenbank verwendet (die geht gern mal kaputt beim harten Ausschalten). Die repariert sich dann auch nicht mehr.
GermansolvedQuestionVMwareVirtualization
Hotly discussed
gleixnerdCheck of ZFW Firewallgleixnerd - 5 CommentsjstrickerWireguard VPN on UDM Pro behind Fritzbox - Handshake did not completejstricker - 3 Comments