I am getting the following message when i try to remediate or stage VMware Updates.
The host returns esxupdate error code:99. An unhandled exception was encountered. Check the Update Manager log files and esxupdate log files for more details.
Im not sure what log file i need to post... is it "vmware-vum-server-log4cpp.log.1"?
Hello,
The latest custom ESXi iso for Cisco servers available on VMware is 6.7.0 build number 14320388 released on 20/8/2019.
Is it recommended to install the newest embedded and installed patches that follow? (the latest is 09/06/2020 with build number 16316930) or it's better to keep the custom iso at it's original version. I am asking this to see if I will experience any issues with these servers if I decide to upgrade.
I don't have internet access on my vCenter, should I download the patch bundle from myvmware and upload it manually to VUM. And should I remediate it all or should I exclude some of the patch files?
Thank you!
I did not see a specific forum for VUM so I landed here. Let me know if this post would be better elsewhere.
We have a 4 host vCenter 6.5 cluster that I inherited a bit back. I felt my first task was to bring all the hosts and VMs up to the current software baselines and am ready to move to VMware Tools.
In VUM the VMware Tools Upgrade Predefined Baseline is gone, I assume at some point it was deleted. After a lot of googling and some searching here, I cannot find how to recreate a predefined baseline.
Could anyone point me in the right direction? Blog, KB article, etc etc.
Thanks
Don
Hi all,
I have recently set ESXi 7.0 up with a Vsphere VM on a new HPE server ( using the custom HPE image) however while setting up scheduled tasks for my VM I noticed there wasn't a "Remediation" option under scheduled tasks for the host. The image came with lifecycle manager so the option should be there but it doesn't appear to be at all, We need this so it keeps Vmware tools up to date. Has anyone experienced this before/know how to get the option to appear?
Hi,
i'm i little bit confused about this behavior.
In the Lifecycle Manager i have entered my email address to get notifications when new patches are available and in the vCenter configration i have entered my internal smtp server.
But now i noticed on my external messaging gateway that the vcenter connects that gateway to send me that notification mail.
From where is he getting that ip/name from?
Do the Lifecycle Manager ask the mx record to deliver emails? Why isn't he using the configured mail host?
Kind regards
Stefan
Running 6.7 virtual center appliance embedded update manager. Everytime I tried to upload a rollup patch using "Upload From File" makes me wonder where the uploaded patches went to? I can't seem to find article or settings related. The patches I usually upload from file are 400MB per each, worried if I have enough capacity in that repository uploaded to, especially it's a virtual appliance. Thanks.
Hi,
Would VUM still show the ESXi as being compliant when an interactive upgrade is done?
Have a situation in which some of the ESXi hosts in the cluster show as compliant and others not even though the same vendor image was used and they have same built
Anything further I can check to proof they are all the same and/or fix compliance?
Thanks
Hi guys, i am new here. Wanted to ask is there any way to update multiple guest operating systems, and what tool to use. Can i use vcenter for that.
Hello,
Has anyone used LifeCycle Manger to update VMware Tools and VM hardware in vSphere 7?
I'd like some screenshots please to see the process. I find the documentation a bit vague.
thanks
Tony
Hi,
Has anyone used UDMS in vSphere 7? The documentation is a bit vague.
1) Can UDMS download ISOs?
2) What URLS do you need for HPe custom ISOs? The manual says: vmware-umds -S --add-url https://host_URL/index.xml --url-type HOST,
so that suggests vmware-umds -S --add-url https://www.hpe.com/index.xml --url-type HOST
3) is the command to push the downloads to a web server vmware-umds -E –export-store https://Web_server
4) What format are the downloads in? Zip or ISO or something else?
5) If LifeCycle Manager is pointing at the web server as its repository does it just work?
6) What about certificates? If the web server has certificates, how does LifeCycle Manager authenticate?
Hopefully there is a nice readable document with these answers and more somewhere.
Thanks
Tony
Hello,
Is it possible to remediate (apply fixes and patch with VUM or lifecylce manager) if the ESX we want to remediate is the one hosting vcenter ?
We have 2 esx hosting each one their own datastore, one is active, one is passive, I would like to know which is the best practice to update esx hosting vcenter appliance, thanks
I recently in-place upgraded our vCenter Server Windows with embedded Platform Services from 6.5 to 6.7. I also installed a new ESXi 6.7 host on an HP DL360 Gen10 server to replace the existing ESXi 6.5 HP ML350 Gen6 server. I originally was going to upgrade to vSphere 7, but found that a Cisco Firewall related VM is not compatible with 7.
After the upgrade, the Update Manager tab is missing and I am getting constant queued "com.vmware.vcIntegrity.CheckNotificationTask.label" tasks initiated by "VMware vSphere Update Manager Check Notification"
If I look at Client Plug-ins using the HTML5 web interface I see the Update Manager (with a suspicious name of "description") and the vSan Web Client listed as "Incompatible". I click "Incompatible", the popup says "The plug-in supports only vSphere Web Client (Flash).":
If I go to the Plug-ins using the Flash client, it doesn't show the Update Manager at all:
I've been searching for answers to this problem for 2 days and can find plenty of solutions for the Appliance and vCenter with external platform services, but nothing for this configuration.
Thanks in advance,
Dave
Hi,
i have configure my update manager on my vsphere 6.7 server.
Connection test is ok, but i can't download patches.
If i click "Download now" nothing happens.
In my repository last patches from 19.12.2019.
What can causes this?
Regards
Dennis
Hi All,
I have a quick question regarding the security of the updates/patches that update manager uses.
Do you know if these updates are signed by VMware and then checked before they are deployed? If so, is there an article or document that states this for record purposes?
I have several ESXi clusters. One cluster in particular won't let me stage updates. It's 7.0. The error is not very specific. "Staging did not succeed for my.host"
On a whim, I decided to create a baseline for each patch provider - vmware, Marvell, and Broadcom. The first two will stage, but the Broadcom baseline gets the same error.
Other hosts in my environment can install all patches. Why do you think there's a problem with this company, and what can I do to try to fix it?
I was read Lifecycle manager document as I understood with t we can do follow tasks :
1 - updae esxi
2- update vcsa
3- if using HPE server can via SPP can update firmware and all drivers on server
Is that correct or can do other things ?
4 - As I understood we had to just use ILO Ampifier and integrate it with vcsa is that correct or in adition had to deploy oneview for lifecycle manager ?
BR
Hi,
since i updated to vCenter 7.0.1 i can't "Sync Updates", just before the update, the sync was success, i got the infos to update the hosts to 7.0.1, but now:
Download patch definitions task failed while syncing depots. Error: 'integrity.fault.HostPatchInvalidVendorCode'.
I found this KB: https://kb.vmware.com/s/article/78688 "Import offline bundle or sync operations may fail in vSphere Lifecycle Manager (78688)"
But when executing the script i get:
DELETE 0
ERROR: update or delete on table "pm_depot_components" violates foreign key constraint "pm_depot_addons_components_component_name_fkey" on table "pm_depot_addons_components"
DETAIL: Key (name, version)=(smxProvider, 700.03.16.00.12-14828939) is still referenced from table "pm_depot_addons_components".
And the problem is still there...
Wat can i do else?
Kind regards
Stefan
Hello All,
I am having an issue to start a VUM service based on VCSA 6.5 with HA & 2 PSCs.
Below are some info regarding the issue:
This is while I am trying to start the service.
[ ~ ]# service-control --start vmware-updatemgr
Perform start operation. vmon_profile=None, svc_names=['vmware-updatemgr'], include_coreossvcs=False, include_leafossvcs=False
2020-10-20T08:45:33.389Z Service updatemgr state STOPPED
Error executing start on service updatemgr. Details {
"resolution": null,
"detail": [
{
"args": [
"updatemgr"
],
"id": "install.ciscommon.service.failstart",
"localized": "An error occurred while starting service 'updatemgr'",
"translatable": "An error occurred while starting service '%(0)s'"
}
],
"componentKey": null,
"problemId": null
}
Service-control failed. Error {
"resolution": null,
"detail": [
{
"args": [
"updatemgr"
],
"id": "install.ciscommon.service.failstart",
"localized": "An error occurred while starting service 'updatemgr'",
"translatable": "An error occurred while starting service '%(0)s'"
}
],
"componentKey": null,
"problemId": null
}
updatemgr-utility.log
[2020-10-20 11:44:57,995 ERROR] Unable to update CM service info
[2020-10-20 11:45:33,714 INFO] Install Key store for Jetty
[2020-10-20 11:45:35,427 INFO] Keystore installed successfully.
[2020-10-20 11:45:35,767 INFO] Updating VUM extension with VC
[2020-10-20 11:45:36,175 INFO] Updating CM service info
[2020-10-20 11:45:36,310 ERROR] CM ReRegisterService failure. Exception is (cis.cm.fault.ComponentManagerFault) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
msg = '',
faultCause = <unset>,
faultMessage = (vmodl.LocalizableMessage) [],
errorCode = 0,
errorMessage = 'UNKNOWN'
}
[2020-10-20 11:45:36,310 ERROR] Unable to update CM service info
cm.log (I have changed some specific information for security reasons)
2020-10-20T11:44:57.989+03:00 [pool-2-thread-1 [] ERROR com.vmware.cis.services.cm.service.ServiceManagerImplTemplate (cf3b9c43-81d5-4d1a-aad6-1bf3dd4b8971)] reRegisterService v1: Failed to re-register 70604e8d-0505-4ee9-ab0c-ad765d4cd1b7 (vpxd-extension-678b208e-5d5e-4c43-b100-bb0f3a079af6@domain.local, com.vmware.vcIntegrity/vcIntegrity 6.5.0)
com.vmware.vim.binding.vmodl.fault.InvalidArgument: null
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[?:1.8.0_162]
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) ~[?:1.8.0_162]
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[?:1.8.0_162]
at java.lang.reflect.Constructor.newInstance(Constructor.java:423) ~[?:1.8.0_162]
at java.lang.Class.newInstance(Class.java:442) ~[?:1.8.0_162]
at com.vmware.vim.vmomi.core.types.impl.ComplexTypeImpl.newInstance(ComplexTypeImpl.java:174) ~[vlsi-core.jar:?]
at com.vmware.vim.vmomi.core.types.impl.DefaultDataObjectFactory.newDataObject(DefaultDataObjectFactory.java:25) ~[vlsi-core.jar:?]
at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.ComplexStackContext.<init>(ComplexStackContext.java:30) ~[vlsi-core.jar:?]
at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallSoapFaultContext.parse(UnmarshallerImpl.java:150) ~[vlsi-core.jar:?]
at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallSoapFaultContext.unmarshall(UnmarshallerImpl.java:101) ~[vlsi-core.jar:?]
at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl.unmarshalSoapFault(UnmarshallerImpl.java:88) ~[vlsi-core.jar:?]
at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl.unmarshalSoapFault(UnmarshallerImpl.java:83) ~[vlsi-core.jar:?]
at com.vmware.vim.vmomi.client.common.impl.SoapFaultStackContext.setValue(SoapFaultStackContext.java:40) ~[vlsi-client.jar:?]
at com.vmware.vim.vmomi.client.common.impl.ResponseUnmarshaller.processNextElement(ResponseUnmarshaller.java:127) ~[vlsi-client.jar:?]
at com.vmware.vim.vmomi.client.common.impl.ResponseUnmarshaller.unmarshal(ResponseUnmarshaller.java:70) ~[vlsi-client.jar:?]
at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.unmarshalResponse(ResponseImpl.java:274) ~[vlsi-client.jar:?]
at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.setResponse(ResponseImpl.java:230) ~[vlsi-client.jar:?]
at com.vmware.vim.vmomi.client.http.impl.HttpExchangeBase.parseResponse(HttpExchangeBase.java:150) ~[vlsi-client.jar:?]
at com.vmware.vim.vmomi.client.http.impl.HttpExchange.run(HttpExchange.java:48) ~[vlsi-client.jar:?]
at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingBase.executeRunnable(HttpProtocolBindingBase.java:226) ~[vlsi-client.jar:?]
at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingImpl.send(HttpProtocolBindingImpl.java:110) ~[vlsi-client.jar:?]
at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.sendCall(MethodInvocationHandlerImpl.java:613) ~[vlsi-client.jar:?]
at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.executeCall(MethodInvocationHandlerImpl.java:594) ~[vlsi-client.jar:?]
at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.completeCall(MethodInvocationHandlerImpl.java:345) ~[vlsi-client.jar:?]
at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invokeOperation(MethodInvocationHandlerImpl.java:305) ~[vlsi-client.jar:?]
at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invoke(MethodInvocationHandlerImpl.java:179) ~[vlsi-client.jar:?]
at com.sun.proxy.$Proxy100.set(Unknown Source) ~[?:?]
at com.vmware.cis.services.cm.service.impl.LsVmomiSiteStore$LsVmomiWrapper$3.execute(LsVmomiSiteStore.java:229) ~[service-cm.jar:?]
at com.vmware.cis.services.cm.service.impl.LsVmomiSiteStore$LsVmomiWrapper$3.execute(LsVmomiSiteStore.java:226) ~[service-cm.jar:?]
at com.vmware.cis.services.cm.service.impl.LsVmomiSiteStore$LsVmomiWrapper.callLs(LsVmomiSiteStore.java:302) ~[service-cm.jar:?]
at com.vmware.cis.services.cm.service.impl.LsVmomiSiteStore$LsVmomiWrapper.set(LsVmomiSiteStore.java:224) ~[service-cm.jar:?]
at com.vmware.cis.services.cm.service.impl.LsVmomiSiteStore.updateService(LsVmomiSiteStore.java:622) ~[service-cm.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_162]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_162]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_162]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_162]
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:333) ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190) ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
at com.vmware.cis.services.common.perfmon.PerfmonInterceptor.invoke(PerfmonInterceptor.java:31) ~[service-common.jar:?]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92) ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:213) ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
at com.sun.proxy.$Proxy67.updateService(Unknown Source) ~[?:?]
at com.vmware.cis.services.cm.service.ServiceManagerImplTemplate.reRegisterService(ServiceManagerImplTemplate.java:306) [service-cm.jar:?]
at com.vmware.cis.services.cm.service.ServiceManagerImpl.reRegisterService(ServiceManagerImpl.java:291) [service-cm.jar:?]
at sun.reflect.GeneratedMethodAccessor182.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_162]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_162]
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:333) [spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190) [spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) [spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
at com.vmware.cis.services.common.perfmon.PerfmonInterceptor.invoke(PerfmonInterceptor.java:31) [service-common.jar:?]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) [spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92) [spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) [spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:213) [spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
at com.sun.proxy.$Proxy68.reRegisterService(Unknown Source) [?:?]
at sun.reflect.GeneratedMethodAccessor182.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_162]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_162]
at com.vmware.vim.vmomi.server.impl.InvocationTask.run(InvocationTask.java:65) [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_162]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_162]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_162]
2020-10-20T11:45:25.430+03:00 [pool-15-thread-4 [] INFO com.vmware.vim.lookup.client.SiteAffinityServerEndpointProvider ()] Site affinity is disabled
2020-10-20T11:45:25.505+03:00 [pool-15-thread-4 [] INFO com.vmware.vim.lookup.client.SiteAffinityServerEndpointProvider ()] Site affinity is disabled
2020-10-20T11:45:25.531+03:00 [pool-15-thread-4 [] INFO com.vmware.vim.lookup.client.SiteAffinityServerEndpointProvider ()] Site affinity is disabled
2020-10-20T11:45:35.471+03:00 [pool-15-thread-1 [] INFO com.vmware.cis.services.cm.service.ServiceManagerImplTemplate ()] search v1: Unauthorized, modifying search to only return SSO.
2020-10-20T11:45:35.472+03:00 [pool-15-thread-1 [] INFO com.vmware.vim.lookup.client.SiteAffinityServerEndpointProvider ()] Site affinity is disabled
2020-10-20T11:45:35.588+03:00 [pool-2-thread-1 [] INFO com.vmware.identity.token.impl.SamlTokenImpl (54d7ec2e-40eb-41cf-959f-7fd13f89ecf0)] SAML token for SubjectNameId [value=vpxd-extension-678b208e-5d5e-4c43-b100-bb0f3a079af6@domain.local, format=http://schemas.xmlsoap.org/claims/UPN] successfully parsed from Element
2020-10-20T11:45:35.590+03:00 [pool-2-thread-1 [] INFO com.vmware.cis.services.common.sso.LoginHelper (54d7ec2e-40eb-41cf-959f-7fd13f89ecf0)] loginByToken: Successfully authenticated 'vpxd-extension-678b208e-5d5e-4c43-b100-bb0f3a079af6@domain.local' on session 01fcfd00-95fa-4a5f-a67e-a98dc60b9560
2020-10-20T11:45:35.594+03:00 [pool-15-thread-2 [] INFO com.vmware.vim.lookup.client.SiteAffinityServerEndpointProvider ()] Site affinity is disabled
2020-10-20T11:45:36.184+03:00 [pool-2-thread-1 [] INFO com.vmware.identity.token.impl.SamlTokenImpl (6a4f8100-0b95-4429-8d8b-969c0726fdec)] SAML token for SubjectNameId [value=vpxd-extension-678b208e-5d5e-4c43-b100-bb0f3a079af6@domain.local, format=http://schemas.xmlsoap.org/claims/UPN] successfully parsed from Element
2020-10-20T11:45:36.185+03:00 [pool-2-thread-1 [] INFO com.vmware.cis.services.common.sso.LoginHelper (6a4f8100-0b95-4429-8d8b-969c0726fdec)] loginByToken: Successfully authenticated 'vpxd-extension-678b208e-5d5e-4c43-b100-bb0f3a079af6@domain.local' on session a18aa98c-07b9-4cdf-920c-4b3b9f3f2949
2020-10-20T11:45:36.189+03:00 [pool-15-thread-3 [] INFO com.vmware.vim.lookup.client.SiteAffinityServerEndpointProvider ()] Site affinity is disabled
2020-10-20T11:45:36.229+03:00 [pool-2-thread-1 [] INFO com.vmware.vim.lookup.client.SiteAffinityServerEndpointProvider (da3d8caa-7207-4af8-8782-934dca2833f0)] Site affinity is disabled
2020-10-20T11:45:36.256+03:00 [pool-2-thread-1 [] INFO com.vmware.vim.lookup.client.SiteAffinityServerEndpointProvider (da3d8caa-7207-4af8-8782-934dca2833f0)] Site affinity is disabled
2020-10-20T11:45:36.270+03:00 [pool-2-thread-1 [] INFO com.vmware.vim.lookup.client.SiteAffinityServerEndpointProvider (da3d8caa-7207-4af8-8782-934dca2833f0)] Site affinity is disabled
2020-10-20T11:45:36.305+03:00 [pool-2-thread-1 [] INFO com.vmware.vim.lookup.client.SiteAffinityServerEndpointProvider (da3d8caa-7207-4af8-8782-934dca2833f0)] Site affinity is disabled
2020-10-20T11:45:36.305+03:00 [pool-2-thread-1 [] WARN com.vmware.cis.services.cm.service.impl.LsVmomiSiteStore (da3d8caa-7207-4af8-8782-934dca2833f0)] Call to lookup service failed; uri::https://PSC01.domain.com/lookupservice/sdk [(vmodl.fault.InvalidArgument) {
faultCause = null,
faultMessage = null,
invalidProperty = Invalid certificate
}]
2020-10-20T11:45:36.305+03:00 [pool-2-thread-1 [] ERROR com.vmware.cis.services.cm.service.ServiceManagerImplTemplate (da3d8caa-7207-4af8-8782-934dca2833f0)] reRegisterService v1: Failed to re-register 70604e8d-0505-4ee9-ab0c-ad765d4cd1b7 (vpxd-extension-678b208e-5d5e-4c43-b100-bb0f3a079af6@domain.local, com.vmware.vcIntegrity/vcIntegrity 6.5.0)
com.vmware.vim.binding.vmodl.fault.InvalidArgument: null
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[?:1.8.0_162]
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) ~[?:1.8.0_162]
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[?:1.8.0_162]
at java.lang.reflect.Constructor.newInstance(Constructor.java:423) ~[?:1.8.0_162]
at java.lang.Class.newInstance(Class.java:442) ~[?:1.8.0_162]
at com.vmware.vim.vmomi.core.types.impl.ComplexTypeImpl.newInstance(ComplexTypeImpl.java:174) ~[vlsi-core.jar:?]
at com.vmware.vim.vmomi.core.types.impl.DefaultDataObjectFactory.newDataObject(DefaultDataObjectFactory.java:25) ~[vlsi-core.jar:?]
at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.ComplexStackContext.<init>(ComplexStackContext.java:30) ~[vlsi-core.jar:?]
at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallSoapFaultContext.parse(UnmarshallerImpl.java:150) ~[vlsi-core.jar:?]
at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallSoapFaultContext.unmarshall(UnmarshallerImpl.java:101) ~[vlsi-core.jar:?]
at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl.unmarshalSoapFault(UnmarshallerImpl.java:88) ~[vlsi-core.jar:?]
at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl.unmarshalSoapFault(UnmarshallerImpl.java:83) ~[vlsi-core.jar:?]
at com.vmware.vim.vmomi.client.common.impl.SoapFaultStackContext.setValue(SoapFaultStackContext.java:40) ~[vlsi-client.jar:?]
at com.vmware.vim.vmomi.client.common.impl.ResponseUnmarshaller.processNextElement(ResponseUnmarshaller.java:127) ~[vlsi-client.jar:?]
at com.vmware.vim.vmomi.client.common.impl.ResponseUnmarshaller.unmarshal(ResponseUnmarshaller.java:70) ~[vlsi-client.jar:?]
at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.unmarshalResponse(ResponseImpl.java:274) ~[vlsi-client.jar:?]
at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.setResponse(ResponseImpl.java:230) ~[vlsi-client.jar:?]
at com.vmware.vim.vmomi.client.http.impl.HttpExchangeBase.parseResponse(HttpExchangeBase.java:150) ~[vlsi-client.jar:?]
at com.vmware.vim.vmomi.client.http.impl.HttpExchange.run(HttpExchange.java:48) ~[vlsi-client.jar:?]
at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingBase.executeRunnable(HttpProtocolBindingBase.java:226) ~[vlsi-client.jar:?]
at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingImpl.send(HttpProtocolBindingImpl.java:110) ~[vlsi-client.jar:?]
at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.sendCall(MethodInvocationHandlerImpl.java:613) ~[vlsi-client.jar:?]
at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.executeCall(MethodInvocationHandlerImpl.java:594) ~[vlsi-client.jar:?]
at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.completeCall(MethodInvocationHandlerImpl.java:345) ~[vlsi-client.jar:?]
at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invokeOperation(MethodInvocationHandlerImpl.java:305) ~[vlsi-client.jar:?]
at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invoke(MethodInvocationHandlerImpl.java:179) ~[vlsi-client.jar:?]
at com.sun.proxy.$Proxy100.set(Unknown Source) ~[?:?]
at com.vmware.cis.services.cm.service.impl.LsVmomiSiteStore$LsVmomiWrapper$3.execute(LsVmomiSiteStore.java:229) ~[service-cm.jar:?]
at com.vmware.cis.services.cm.service.impl.LsVmomiSiteStore$LsVmomiWrapper$3.execute(LsVmomiSiteStore.java:226) ~[service-cm.jar:?]
at com.vmware.cis.services.cm.service.impl.LsVmomiSiteStore$LsVmomiWrapper.callLs(LsVmomiSiteStore.java:302) ~[service-cm.jar:?]
at com.vmware.cis.services.cm.service.impl.LsVmomiSiteStore$LsVmomiWrapper.set(LsVmomiSiteStore.java:224) ~[service-cm.jar:?]
at com.vmware.cis.services.cm.service.impl.LsVmomiSiteStore.updateService(LsVmomiSiteStore.java:622) ~[service-cm.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_162]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_162]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_162]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_162]
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:333) ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190) ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
at com.vmware.cis.services.common.perfmon.PerfmonInterceptor.invoke(PerfmonInterceptor.java:31) ~[service-common.jar:?]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92) ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:213) ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
at com.sun.proxy.$Proxy67.updateService(Unknown Source) ~[?:?]
at com.vmware.cis.services.cm.service.ServiceManagerImplTemplate.reRegisterService(ServiceManagerImplTemplate.java:306) [service-cm.jar:?]
at com.vmware.cis.services.cm.service.ServiceManagerImpl.reRegisterService(ServiceManagerImpl.java:291) [service-cm.jar:?]
at sun.reflect.GeneratedMethodAccessor182.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_162]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_162]
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:333) [spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190) [spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) [spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
at com.vmware.cis.services.common.perfmon.PerfmonInterceptor.invoke(PerfmonInterceptor.java:31) [service-common.jar:?]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) [spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92) [spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) [spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:213) [spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]
at com.sun.proxy.$Proxy68.reRegisterService(Unknown Source) [?:?]
at sun.reflect.GeneratedMethodAccessor182.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_162]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_162]
at com.vmware.vim.vmomi.server.impl.InvocationTask.run(InvocationTask.java:65) [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_162]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_162]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_162]
2020-10-20T11:48:27.891+03:00 [pool-15-thread-4 [] INFO com.vmware.vim.lookup.client.SiteAffinityServerEndpointProvider ()] Site affinity is disabled
2020-10-20T11:48:27.968+03:00 [pool-15-thread-4 [] INFO com.vmware.vim.lookup.client.SiteAffinityServerEndpointProvider ()] Site affinity is disabled
2020-10-20T11:48:27.994+03:00 [pool-15-thread-4 [] INFO com.vmware.vim.lookup.client.SiteAffinityServerEndpointProvider ()] Site affinity is disabled
2020-10-20T11:48:28.239+03:00 [pool-15-thread-1 [] INFO com.vmware.vim.lookup.client.SiteAffinityServerEndpointProvider ()] Site affinity is disabled
2020-10-20T11:48:28.273+03:00 [pool-15-thread-2 [] INFO com.vmware.vim.lookup.client.SiteAffinityServerEndpointProvider ()] Site affinity is disabled
2020-10-20T11:48:35.191+03:00 [pool-2-thread-1 [] INFO com.vmware.cis.services.common.sso.LoginHelper (af898b09-76d9-4ab5-94b5-18d287f29cd0)] loginByToken: User 'vsphere-webclient-678b208e-5d5e-4c43-b100-bb0f3a079af6@domain.local' is already authenticated
2020-10-20T11:48:35.193+03:00 [pool-15-thread-3 [] INFO com.vmware.vim.lookup.client.SiteAffinityServerEndpointProvider ()] Site affinity is disabled
2020-10-20T11:48:35.204+03:00 [pool-15-thread-3 [] INFO com.vmware.vim.lookup.client.SiteAffinityServerEndpointProvider ()] Site affinity is disabled
2020-10-20T11:48:35.230+03:00 [pool-15-thread-3 [] INFO com.vmware.vim.lookup.client.SiteAffinityServerEndpointProvider ()] Site affinity is disabled
2020-10-20T11:48:35.493+03:00 [pool-2-thread-1 [] INFO com.vmware.cis.services.common.sso.LoginHelper (0feecd59-fdc2-4631-9849-e6349adf3e0a)] loginByToken: User 'vsphere-webclient-678b208e-5d5e-4c43-b100-bb0f3a079af6@domain.local' is already authenticated
2020-10-20T11:48:35.521+03:00 [pool-15-thread-4 [] INFO com.vmware.vim.lookup.client.SiteAffinityServerEndpointProvider ()] Site affinity is disabled
2020-10-20T11:48:35.639+03:00 [pool-15-thread-1 [] INFO com.vmware.vim.lookup.client.SiteAffinityServerEndpointProvider ()] Site affinity is disabled
2020-10-20T11:48:35.783+03:00 [pool-15-thread-2 [] INFO com.vmware.vim.lookup.client.SiteAffinityServerEndpointProvider ()] Site affinity is disabled
2020-10-20T11:48:35.828+03:00 [pool-15-thread-3 [] INFO com.vmware.vim.lookup.client.SiteAffinityServerEndpointProvider ()] Site affinity is disabled
2020-10-20T11:48:35.853+03:00 [pool-15-thread-4 [] INFO com.vmware.vim.lookup.client.SiteAffinityServerEndpointProvider ()] Site affinity is disabled
2020-10-20T11:48:35.882+03:00 [pool-15-thread-1 [] INFO com.vmware.vim.lookup.client.SiteAffinityServerEndpointProvider ()] Site affinity is disabled
2020-10-20T11:48:35.922+03:00 [pool-15-thread-2 [] INFO com.vmware.vim.lookup.client.SiteAffinityServerEndpointProvider ()] Site affinity is disabled
2020-10-20T11:48:35.955+03:00 [pool-15-thread-3 [] INFO com.vmware.vim.lookup.client.SiteAffinityServerEndpointProvider ()] Site affinity is disabled
2020-10-20T11:49:47.847+03:00 [pool-15-thread-4 [] INFO com.vmware.vim.lookup.client.SiteAffinityServerEndpointProvider ()] Site affinity is disabled
After I checked these details and did a quick search, I found these articles below:
https://kb.vmware.com/s/article/76298
https://communities.vmware.com/thread/598354
There is some mention regarding:
The SSL certificate of STS service cannot be verified
But I couldn't find it in my log.
This is the output from the suggest command: Openssl s_client -connect <PSC/VCSA-FQDN/IP>:7444 | less
Openssl s_client -connect psc01.domain.com:7444
CONNECTED(00000194)
depth=0 CN = psc01.domain.com, C = XX, ST = XX, L = Palo Alto, O = XX, OU = VMware Engineering
verify error:num=20:unable to get local issuer certificate
verify return:1
depth=0 CN = psc01.domain.com, C = XX, ST = XX, L = Palo Alto, O = XX, OU = VMware Engineering
verify error:num=21:unable to verify the first certificate
verify return:1
---
Certificate chain
0 s:CN = psc01.domain.com, C = XX, ST = XX, L = Palo Alto, O = XX, OU = VMware Engineering
i:CN = psc01.domain.com, DC = XX, DC = local, C = XX, ST = XX, O = psc01.domain.com, OU = VMware Engineering
---
Server certificate
-----BEGIN CERTIFICATE-----
XXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXX
-----END CERTIFICATE-----
subject=CN = psc01.domain.com, C = XX, ST = XX, L = Palo Alto, O = XX, OU = VMware Engineering
issuer=CN = psc01.domain.com, DC = XX, DC = local, C = XX, ST = XX, O = psc01.domain.com, OU = VMware Engineering
---
No client certificate CA names sent
Peer signing digest: SHA256
Peer signature type: RSA
Server Temp Key: ECDH, P-256, 256 bits
---
SSL handshake has read 1592 bytes and written 451 bytes
Verification error: unable to verify the first certificate
---
New, TLSv1.2, Cipher is ECDHE-RSA-AES256-GCM-SHA384
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
Protocol : TLSv1.2
Cipher : ECDHE-RSA-AES256-GCM-SHA384
Session-ID: XXXXXXXXXXXXXXXXXXXXXXXXXXXX
Session-ID-ctx:
Master-Key: XXXXXXXXXXXXXXXXXXXXXXXXXXXX
PSK identity: None
PSK identity hint: None
SRP username: None
Start Time: 1603185518
Timeout : 7200 (sec)
Verify return code: 21 (unable to verify the first certificate)
Extended master secret: yes
---
read:errno=0
I made bold some possible errors/issues. The problem looks quite similar with the one I am dealing with but still couldn't find any solution yet. Any help would be much appreciated.