VMware Cloud Community
dmitry_er
Contributor
Contributor
‎10-23-2017 02:25 AM
Jump to solution

The "Check VM Storage Policy Compliance" operation failed for the entity with the following error message.

После обновления vCenter Appliance c 6.0 до 6.5 перестала запускакться проверка "Check VM Storage Policy Compliance" на виртуальных машинах в vSAN.

После запуска появляется сообщение:

The "Check VM Storage Policy Compliance" operation failed for the entity with the following error message.

The error has no message.

При этом сами политики vSAN применяются, но статус объектов в хранилище "VM Storage Policy Compliance" не меняется.

Проблеме уже почти пол-года. Думал с обновлениями проблема уйдет. Установил посление апдейты 6.5 на хосты и на vCenter, но проблема остается. Перезагрузка хостов и преустановка Storage Provider не помогает.

Пвторю на English

After the vCenter Appliance was updated from 6.0 to 6.5, the check "Check VM Storage Policy Compliance" on virtual machines in vSAN stopped running.

After startup, the message:

The "Check VM Storage Policy Compliance" operation failed for the entity with the following error message.

The error has no message.

​

In this case, the vSAN policies themselves are applied, but the status of objects in the "VM Storage Policy Compliance" repository does not change.

The problem is almost half a year. I thought with the updates the problem will be gone. Installed the update update 6.5 to the hosts and to vCenter, but the problem remains. Restarting hosts and reinstalling the Storage Provider does not help.

0 Kudos
1 Solution

Accepted Solutions
dmitry_er
Contributor
Contributor
‎11-14-2017 10:53 AM
Jump to solution

I contacted vSAN support and they resolved the issue.

They removed nonexistent providers.

View solution in original post

0 Kudos
6 Replies
TheBobkin
Champion
Champion
‎10-23-2017 12:42 PM
Jump to solution

Hello Dmitry,

Check the web-client logs on the vCenter at the time of this blank error message occurring which may potentially give more information about the nature of the problem:

VCSA:

/var/log/vmware/vsphere-client/logs/vsphere_client_virgo.log

Windows:

C:\ProgramData\VMware\vCenterServer\logs\vsphere-client\logs\vsphere_client_virgo.log

If the vCenter is a Windows-based machine, is the OS installed in English, and/or is the vSphere client being accessed in another language?

I ask as language localization (such as Cyrillic characters) can cause error messages to appear blank or return no message.

Bob

0 Kudos
dmitry_er
Contributor
Contributor
‎10-24-2017 01:46 AM
Jump to solution

listing /var/log/vmware/vsphere-client/logs/vsphere_client_virgo.log

[2017-10-24T11:39:29.505+03:00] [INFO ] http-bio-9090-exec-116       70024366 103985 203888 com.vmware.vise.util.session.SessionUtil                          Added clientId 203894. Total clientIds so far (incl. the newly added one): 7
[2017-10-24T11:39:29.505+03:00] [INFO ] http-bio-9090-exec-116       70024366 103985 203888 com.vmware.vise.util.session.SessionUtil                          Generated hashed session id: 103993
[2017-10-24T11:39:29.505+03:00] [INFO ] http-bio-9090-exec-116       70024366 103985 203888 com.vmware.vise.util.session.SessionUtil                          Mapping: ds/sdk: sessionid to -> 103993 with clientId: 203894
[2017-10-24T11:39:29.505+03:00] [INFO ] http-bio-9090-exec-116       70024366 103985 203888 com.vmware.vise.util.session.SessionUtil                          Associated sessionId 103993 with clientId 203894. Context path: ds/sdk
[2017-10-24T11:39:29.505+03:00] [INFO ] http-bio-9090-exec-116       70024366 103985 203888 com.vmware.vise.util.session.SessionUtil                          Assigned clientId 203894 to session 103993 with context path: ds/sdk
[2017-10-24T11:39:29.505+03:00] [INFO ] http-bio-9090-exec-116       70024366 103985 203888 com.vmware.vise.util.session.SessionUtil                          ClientId 203894 was automatically generated
[2017-10-24T11:39:29.505+03:00] [WARN ] http-bio-9090-exec-116       70024366 103985 203888 com.vmware.vise.util.session.SessionUtil                          Just clobbered an existing httpRequest
[2017-10-24T11:39:29.721+03:00] [WARN ] http-bio-9090-exec-116       70024385 103993 203894 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl          The VMODL version is not available for VC https://***********:443/sdk (69efff8d-d8fc-4fe5-98e5-923db719c141). Assuming it is version11
[2017-10-24T11:39:29.722+03:00] [INFO ] http-bio-9090-exec-116       70024385 103993 203894 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl          Initializing vmomi for vc - https://***********:443/sdk at VMODL version com.vmware.vim.binding.vim.version.internal.version11
[2017-10-24T11:39:29.737+03:00] [WARN ] http-bio-9090-exec-116       70024385 103993 203894 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl          VC https://***********:443/sdk doesn't support the requested locale "en_US". Will use "en" instead.
[2017-10-24T11:39:29.737+03:00] [INFO ] http-bio-9090-exec-116       70024385 103993 203894 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl          Vmomi initialization successful for VC https://***********:443/sdk (69efff8d-d8fc-4fe5-98e5-923db719c141), locale=en
[2017-10-24T11:39:29.737+03:00] [INFO ] http-bio-9090-exec-116       70024385 103993 203894 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      Processing peer vc servers - https://***********:443/sdk
[2017-10-24T11:39:29.737+03:00] [INFO ] http-bio-9090-exec-116       70024385 103993 203894 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      Peer VC servers: []
[2017-10-24T11:39:29.737+03:00] [INFO ] http-bio-9090-exec-116       70024385 103993 203894 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      Created VC registry: https://***********:443/sdk(69efff8d-d8fc-4fe5-98e5-923db719c141)
[2017-10-24T11:39:29.737+03:00] [INFO ] http-bio-9090-exec-116       70024385 103993 203894 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      Logging into startup VC: https://***********:443/sdk
[2017-10-24T11:39:29.784+03:00] [INFO ] http-bio-9090-exec-116       70024385 103993 203894 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl          loginByToken successful on vc https://***********:443/sdk
[2017-10-24T11:39:29.784+03:00] [INFO ] http-bio-9090-exec-116       70024385 103993 203894 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl          logged in VC with id 3003895
[2017-10-24T11:39:29.784+03:00] [INFO ] http-bio-9090-exec-116       70024385 103993 203894 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl          Successfully logged into VC https://***********:443/sdk for session: 103993
[2017-10-24T11:39:29.784+03:00] [INFO ] http-bio-9090-exec-116       70024385 103993 203894 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      Login successful to start-up VC: https://***********:443/sdk
[2017-10-24T11:39:29.784+03:00] [INFO ] http-bio-9090-exec-116       70024385 103993 203894 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      Login to peer vc servers for startup VC https://***********:443/sdk
[2017-10-24T11:39:29.784+03:00] [INFO ] http-bio-9090-exec-116       70024385 103993 203894 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      Peer vc servers for https://***********:443/sdk:
[2017-10-24T11:39:29.784+03:00] [INFO ] http-bio-9090-exec-116       70024385 103993 203894 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      There are no peers
[2017-10-24T11:39:29.865+03:00] [INFO ] linkedVcGroup-pool-3248      70024386 103988 203891 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl          Logging out of VC https://***********:443/sdk (guid 69efff8d-d8fc-4fe5-98e5-923db719c141, id 3003892, username null, sessionID 103988, clientId 203891)
[2017-10-24T11:39:29.878+03:00] [INFO ] linkedVcGroup-pool-3248      70024386 103988 203891 com.vmware.vise.util.debug.TimeMonitor                            VcServiceImpl logout: 12 milliseconds
[2017-10-24T11:39:29.880+03:00] [INFO ] http-bio-9090-exec-133       70024386 103988 203891 com.vmware.vise.util.session.SessionUtil                          Removed clientId 203891 for sessionId 103988 with context path ds/sdk. Total clientIds after the removal: 6

[2017-10-24T11:39:41.251+03:00] [INFO ] http-bio-9090-exec-132       70024365 103992 203893 com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl           Successfully acquired token for user: {Name: aisaev, Domain: ***********}
[2017-10-24T11:39:41.251+03:00] [INFO ] http-bio-9090-exec-132       70024365 103992 203893 com.vmware.vise.util.session.SessionUtil                          Added clientId 203895. Total clientIds so far (incl. the newly added one): 7
[2017-10-24T11:39:41.251+03:00] [INFO ] http-bio-9090-exec-132       70024365 103992 203893 com.vmware.vise.util.session.SessionUtil                          Generated hashed session id: 103994
[2017-10-24T11:39:41.251+03:00] [INFO ] http-bio-9090-exec-132       70024365 103992 203893 com.vmware.vise.util.session.SessionUtil                          Mapping: ds/sdk: sessionid to -> 103994 with clientId: 203895
[2017-10-24T11:39:41.252+03:00] [INFO ] http-bio-9090-exec-132       70024365 103992 203893 com.vmware.vise.util.session.SessionUtil                          Associated sessionId 103994 with clientId 203895. Context path: ds/sdk
[2017-10-24T11:39:41.252+03:00] [INFO ] http-bio-9090-exec-132       70024365 103992 203893 com.vmware.vise.util.session.SessionUtil                          Assigned clientId 203895 to session 103994 with context path: ds/sdk
[2017-10-24T11:39:41.252+03:00] [INFO ] http-bio-9090-exec-132       70024365 103992 203893 com.vmware.vise.util.session.SessionUtil                          ClientId 203895 was automatically generated
[2017-10-24T11:39:41.252+03:00] [WARN ] http-bio-9090-exec-132       70024365 103992 203893 com.vmware.vise.util.session.SessionUtil                          Just clobbered an existing httpRequest
[2017-10-24T11:39:41.340+03:00] [WARN ] http-bio-9090-exec-132       70024387 103994 203895 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl          The VMODL version is not available for VC https://***********:443/sdk (69efff8d-d8fc-4fe5-98e5-923db719c141). Assuming it is version11
[2017-10-24T11:39:41.341+03:00] [INFO ] http-bio-9090-exec-132       70024387 103994 203895 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl          Initializing vmomi for vc - https://***********:443/sdk at VMODL version com.vmware.vim.binding.vim.version.internal.version11
[2017-10-24T11:39:41.351+03:00] [WARN ] http-bio-9090-exec-132       70024387 103994 203895 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl          VC https://***********:443/sdk doesn't support the requested locale "en_US". Will use "en" instead.
[2017-10-24T11:39:41.351+03:00] [INFO ] http-bio-9090-exec-132       70024387 103994 203895 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl          Vmomi initialization successful for VC https://***********:443/sdk (69efff8d-d8fc-4fe5-98e5-923db719c141), locale=en
[2017-10-24T11:39:41.351+03:00] [INFO ] http-bio-9090-exec-132       70024387 103994 203895 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      Processing peer vc servers - https://***********:443/sdk
[2017-10-24T11:39:41.351+03:00] [INFO ] http-bio-9090-exec-132       70024387 103994 203895 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      Peer VC servers: []
[2017-10-24T11:39:41.351+03:00] [INFO ] http-bio-9090-exec-132       70024387 103994 203895 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      Created VC registry: https://***********:443/sdk(69efff8d-d8fc-4fe5-98e5-923db719c141)
[2017-10-24T11:39:41.351+03:00] [INFO ] http-bio-9090-exec-132       70024387 103994 203895 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      Logging into startup VC: https://***********:443/sdk
[2017-10-24T11:39:41.469+03:00] [INFO ] http-bio-9090-exec-132       70024387 103994 203895 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl          loginByToken successful on vc https://***********:443/sdk
[2017-10-24T11:39:41.469+03:00] [INFO ] http-bio-9090-exec-132       70024387 103994 203895 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl          logged in VC with id 3003896
[2017-10-24T11:39:41.469+03:00] [INFO ] http-bio-9090-exec-132       70024387 103994 203895 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl          Successfully logged into VC https://***********:443/sdk for session: 103994
[2017-10-24T11:39:41.469+03:00] [INFO ] http-bio-9090-exec-132       70024387 103994 203895 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      Login successful to start-up VC: https://***********:443/sdk
[2017-10-24T11:39:41.469+03:00] [INFO ] http-bio-9090-exec-132       70024387 103994 203895 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      Login to peer vc servers for startup VC https://***********:443/sdk
[2017-10-24T11:39:41.469+03:00] [INFO ] http-bio-9090-exec-132       70024387 103994 203895 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      Peer vc servers for https://***********:443/sdk:
[]
[2017-10-24T11:39:41.469+03:00] [INFO ] http-bio-9090-exec-132       70024387 103994 203895 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      There are no peers
[2017-10-24T11:39:41.541+03:00] [INFO ] linkedVcGroup-pool-3248      70024388 103991 203892 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl          Logging out of VC https://***********:443/sdk (guid 69efff8d-d8fc-4fe5-98e5-923db719c141, id 3003893, username null, sessionID 103991, clientId 203892)
[2017-10-24T11:39:41.555+03:00] [INFO ] linkedVcGroup-pool-3248      70024388 103991 203892 com.vmware.vise.util.debug.TimeMonitor                            VcServiceImpl logout: 13 milliseconds
[2017-10-24T11:39:41.556+03:00] [INFO ] http-bio-9090-exec-115       70024388 103991 203892 com.vmware.vise.util.session.SessionUtil                          Removed clientId 203892 for sessionId 103991 with context path ds/sdk. Total clientIds after the removal: 6
[2017-10-24T11:40:06.094+03:00] [INFO ] http-bio-9090-exec-133       70024386 103988 203891 com.vmware.identity.token.impl.SamlTokenImpl                      SAML token for SubjectNameId [value=vkorovitsyn@***********, format=http://schemas.xmlsoap.org/claims/UPN] successfully parsed from XML
[2017-10-24T11:40:06.110+03:00] [INFO ] http-bio-9090-exec-133       70024386 103988 203891 com.vmware.identity.token.impl.SamlTokenImpl                      SAML token for SubjectNameId [value=vkorovitsyn@***********, format=http://schemas.xmlsoap.org/claims/UPN] successfully parsed from XML
[2017-10-24T11:40:06.175+03:00] [INFO ] http-bio-9090-exec-133       70024386 103988 203891 com.vmware.vim.sso.client.impl.SiteAffinityServiceDiscovery       Site affinity is disabled
[2017-10-24T11:40:06.512+03:00] [INFO ] http-bio-9090-exec-133       70024386 103988 203891 com.vmware.identity.token.impl.SamlTokenImpl                      SAML token for SubjectNameId [value=vkorovitsyn@***********, format=http://schemas.xmlsoap.org/claims/UPN] successfully parsed from Element
[2017-10-24T11:40:06.513+03:00] [INFO ] http-bio-9090-exec-133       70024386 103988 203891 com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl           Successfully acquired token for user: {Name: vkorovitsyn, Domain: ***********}
[2017-10-24T11:40:06.513+03:00] [INFO ] http-bio-9090-exec-133       70024386 103988 203891 com.vmware.vise.util.session.SessionUtil                          Added clientId 203896. Total clientIds so far (incl. the newly added one): 7
[2017-10-24T11:40:06.513+03:00] [INFO ] http-bio-9090-exec-133       70024386 103988 203891 com.vmware.vise.util.session.SessionUtil                          Generated hashed session id: 103995
[2017-10-24T11:40:06.513+03:00] [INFO ] http-bio-9090-exec-133       70024386 103988 203891 com.vmware.vise.util.session.SessionUtil                          Mapping: ds/sdk: sessionid to -> 103995 with clientId: 203896
[2017-10-24T11:40:06.513+03:00] [INFO ] http-bio-9090-exec-133       70024386 103988 203891 com.vmware.vise.util.session.SessionUtil                          Associated sessionId 103995 with clientId 203896. Context path: ds/sdk
[2017-10-24T11:40:06.514+03:00] [INFO ] http-bio-9090-exec-133       70024386 103988 203891 com.vmware.vise.util.session.SessionUtil                          Assigned clientId 203896 to session 103995 with context path: ds/sdk
[2017-10-24T11:40:06.514+03:00] [INFO ] http-bio-9090-exec-133       70024386 103988 203891 com.vmware.vise.util.session.SessionUtil                          ClientId 203896 was automatically generated
[2017-10-24T11:40:06.514+03:00] [WARN ] http-bio-9090-exec-133       70024386 103988 203891 com.vmware.vise.util.session.SessionUtil                          Just clobbered an existing httpRequest
[2017-10-24T11:40:06.627+03:00] [WARN ] http-bio-9090-exec-133       70024389 103995 203896 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl          The VMODL version is not available for VC https://***********:443/sdk (69efff8d-d8fc-4fe5-98e5-923db719c141). Assuming it is version11
[2017-10-24T11:40:06.627+03:00] [INFO ] http-bio-9090-exec-133       70024389 103995 203896 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl          Initializing vmomi for vc - https://***********:443/sdk at VMODL version com.vmware.vim.binding.vim.version.internal.version11
[2017-10-24T11:40:06.636+03:00] [WARN ] http-bio-9090-exec-133       70024389 103995 203896 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl          VC https://***********:443/sdk doesn't support the requested locale "en_US". Will use "en" instead.
[2017-10-24T11:40:06.636+03:00] [INFO ] http-bio-9090-exec-133       70024389 103995 203896 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl          Vmomi initialization successful for VC https://***********:443/sdk (69efff8d-d8fc-4fe5-98e5-923db719c141), locale=en
[2017-10-24T11:40:06.636+03:00] [INFO ] http-bio-9090-exec-133       70024389 103995 203896 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      Processing peer vc servers - https://***********:443/sdk
[2017-10-24T11:40:06.636+03:00] [INFO ] http-bio-9090-exec-133       70024389 103995 203896 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      Peer VC servers: []
[2017-10-24T11:40:06.636+03:00] [INFO ] http-bio-9090-exec-133       70024389 103995 203896 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      Created VC registry: https://***********:443/sdk(69efff8d-d8fc-4fe5-98e5-923db719c141)
[2017-10-24T11:40:06.636+03:00] [INFO ] http-bio-9090-exec-133       70024389 103995 203896 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      Logging into startup VC: https://***********:443/sdk
[2017-10-24T11:40:06.716+03:00] [INFO ] http-bio-9090-exec-133       70024389 103995 203896 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl          loginByToken successful on vc https://***********:443/sdk
[2017-10-24T11:40:06.716+03:00] [INFO ] http-bio-9090-exec-133       70024389 103995 203896 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl          logged in VC with id 3003897
[2017-10-24T11:40:06.716+03:00] [INFO ] http-bio-9090-exec-133       70024389 103995 203896 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl          Successfully logged into VC https://***********:443/sdk for session: 103995
[2017-10-24T11:40:06.716+03:00] [INFO ] http-bio-9090-exec-133       70024389 103995 203896 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      Login successful to start-up VC: https://***********:443/sdk
[2017-10-24T11:40:06.716+03:00] [INFO ] http-bio-9090-exec-133       70024389 103995 203896 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      Login to peer vc servers for startup VC https://***********:443/sdk
[2017-10-24T11:40:06.716+03:00] [INFO ] http-bio-9090-exec-133       70024389 103995 203896 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      Peer vc servers for https://***********:443/sdk:
[]
[2017-10-24T11:40:06.716+03:00] [INFO ] http-bio-9090-exec-133       70024389 103995 203896 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      There are no peers
[2017-10-24T11:40:06.765+03:00] [INFO ] linkedVcGroup-pool-3248      70024390 103992 203893 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl          Logging out of VC https://***********:443/sdk (guid 69efff8d-d8fc-4fe5-98e5-923db719c141, id 3003894, username null, sessionID 103992, clientId 203893)
[2017-10-24T11:40:06.775+03:00] [INFO ] linkedVcGroup-pool-3248      70024390 103992 203893 com.vmware.vise.util.debug.TimeMonitor                            VcServiceImpl logout: 9 milliseconds
[2017-10-24T11:40:06.776+03:00] [INFO ] http-bio-9090-exec-128       70024390 103992 203893 com.vmware.vise.util.session.SessionUtil                          Removed clientId 203893 for sessionId 103992 with context path ds/sdk. Total clientIds after the removal: 6
[2017-10-24T11:40:20.333+03:00] [WARN ] http-bio-9090-exec-125       70024391 ###### ###### com.vmware.vise.util.session.SessionUtil                          Just clobbered an existing httpRequest
[2017-10-24T11:40:20.333+03:00] [INFO ] http-bio-9090-exec-125       70024391 ###### ###### com.vmware.vise.vim.cm.HealthStatusRequestHandler                 Received a health status request
[2017-10-24T11:40:20.334+03:00] [INFO ] http-bio-9090-exec-125       70024391 ###### ###### com.vmware.vise.vim.cm.HealthStatusRequestHandler                 Done processing health status request: GREEN
[2017-10-24T11:40:25.341+03:00] [INFO ] http-bio-9090-exec-115       70024388 103991 203892 org.springframework.flex.servlet.MessageBrokerHandlerAdapter      Channel endpoint amf received request.
[2017-10-24T11:40:34.047+03:00] [INFO ] http-bio-9090-exec-55         com.vmware.identity.token.impl.SamlTokenImpl                      SAML token for SubjectNameId [value=dyatskiv@***********, format=http://schemas.xmlsoap.org/claims/UPN] successfully parsed from XML
[2017-10-24T11:40:34.075+03:00] [INFO ] http-bio-9090-exec-55         com.vmware.identity.token.impl.SamlTokenImpl                      SAML token for SubjectNameId [value=dyatskiv@***********, format=http://schemas.xmlsoap.org/claims/UPN] successfully parsed from XML
[2017-10-24T11:40:34.195+03:00] [INFO ] http-bio-9090-exec-55         com.vmware.vim.sso.client.impl.SiteAffinityServiceDiscovery       Site affinity is disabled
[2017-10-24T11:40:34.598+03:00] [INFO ] http-bio-9090-exec-55         com.vmware.identity.token.impl.SamlTokenImpl                      SAML token for SubjectNameId [value=dyatskiv@***********, format=http://schemas.xmlsoap.org/claims/UPN] successfully parsed from Element
[2017-10-24T11:40:34.599+03:00] [INFO ] http-bio-9090-exec-55         com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl           Successfully acquired token for user: {Name: dyatskiv, Domain: ***********}
[2017-10-24T11:40:34.599+03:00] [INFO ] http-bio-9090-exec-55         com.vmware.vise.util.session.SessionUtil                          Added clientId 203897. Total clientIds so far (incl. the newly added one): 7
[2017-10-24T11:40:34.599+03:00] [INFO ] http-bio-9090-exec-55         com.vmware.vise.util.session.SessionUtil                          Generated hashed session id: 103996
[2017-10-24T11:40:34.599+03:00] [INFO ] http-bio-9090-exec-55         com.vmware.vise.util.session.SessionUtil                          Mapping: ds/sdk: sessionid to -> 103996 with clientId: 203897
[2017-10-24T11:40:34.599+03:00] [INFO ] http-bio-9090-exec-55         com.vmware.vise.util.session.SessionUtil                          Associated sessionId 103996 with clientId 203897. Context path: ds/sdk
[2017-10-24T11:40:34.599+03:00] [INFO ] http-bio-9090-exec-55         com.vmware.vise.util.session.SessionUtil                          Assigned clientId 203897 to session 103996 with context path: ds/sdk
[2017-10-24T11:40:34.599+03:00] [INFO ] http-bio-9090-exec-55         com.vmware.vise.util.session.SessionUtil                          ClientId 203897 was automatically generated
[2017-10-24T11:40:34.657+03:00] [WARN ] http-bio-9090-exec-55        70024393 103996 203897 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl          The VMODL version is not available for VC https://***********:443/sdk (69efff8d-d8fc-4fe5-98e5-923db719c141). Assuming it is version11
[2017-10-24T11:40:34.657+03:00] [INFO ] http-bio-9090-exec-55        70024393 103996 203897 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl          Initializing vmomi for vc - https://***********:443/sdk at VMODL version com.vmware.vim.binding.vim.version.internal.version11
[2017-10-24T11:40:34.669+03:00] [WARN ] http-bio-9090-exec-55        70024393 103996 203897 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl          VC https://***********:443/sdk doesn't support the requested locale "en_US". Will use "en" instead.
[2017-10-24T11:40:34.669+03:00] [INFO ] http-bio-9090-exec-55        70024393 103996 203897 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl          Vmomi initialization successful for VC https://***********:443/sdk (69efff8d-d8fc-4fe5-98e5-923db719c141), locale=en
[2017-10-24T11:40:34.669+03:00] [INFO ] http-bio-9090-exec-55        70024393 103996 203897 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      Processing peer vc servers - https://***********:443/sdk
[2017-10-24T11:40:34.669+03:00] [INFO ] http-bio-9090-exec-55        70024393 103996 203897 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      Peer VC servers: []
[2017-10-24T11:40:34.669+03:00] [INFO ] http-bio-9090-exec-55        70024393 103996 203897 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      Created VC registry: https://***********:443/sdk(69efff8d-d8fc-4fe5-98e5-923db719c141)
[2017-10-24T11:40:34.669+03:00] [INFO ] http-bio-9090-exec-55        70024393 103996 203897 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      Logging into startup VC: https://***********:443/sdk
[2017-10-24T11:40:34.749+03:00] [INFO ] http-bio-9090-exec-55        70024393 103996 203897 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl          loginByToken successful on vc https://***********:443/sdk
[2017-10-24T11:40:34.749+03:00] [INFO ] http-bio-9090-exec-55        70024393 103996 203897 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl          logged in VC with id 3003898
[2017-10-24T11:40:34.749+03:00] [INFO ] http-bio-9090-exec-55        70024393 103996 203897 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl          Successfully logged into VC https://***********:443/sdk for session: 103996
[2017-10-24T11:40:34.749+03:00] [INFO ] http-bio-9090-exec-55        70024393 103996 203897 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      Login successful to start-up VC: https://***********:443/sdk
[2017-10-24T11:40:34.749+03:00] [INFO ] http-bio-9090-exec-55        70024393 103996 203897 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      Login to peer vc servers for startup VC https://***********:443/sdk
[2017-10-24T11:40:34.749+03:00] [INFO ] http-bio-9090-exec-55        70024393 103996 203897 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      Peer vc servers for https://***********:443/sdk:
[]
[2017-10-24T11:40:34.749+03:00] [INFO ] http-bio-9090-exec-55        70024393 103996 203897 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      There are no peers
[2017-10-24T11:40:34.802+03:00] [INFO ] linkedVcGroup-pool-3248      70024394 103986 203889 com.vmware.vise.vim.commons.vcservice.impl.VcServiceImpl          Logging out of VC https://***********:443/sdk (guid 69efff8d-d8fc-4fe5-98e5-923db719c141, id 3003890, username null, sessionID 103986, clientId 203889)
[2017-10-24T11:40:34.813+03:00] [INFO ] linkedVcGroup-pool-3248      70024394 103986 203889 com.vmware.vise.util.debug.TimeMonitor                            VcServiceImpl logout: 11 milliseconds
[2017-10-24T11:40:34.814+03:00] [INFO ] http-bio-9090-exec-99        70024394 103986 203889 com.vmware.vise.util.session.SessionUtil                          Removed clientId 203889 for sessionId 103986 with context path ds/sdk. Total clientIds after the removal: 6
[2017-10-24T11:40:35.805+03:00] [WARN ] http-bio-9090-exec-55        70024393 103996 203897 com.vmware.vise.util.session.SessionUtil                          Just clobbered an existing httpRequest
[2017-10-24T11:40:58.622+03:00] [INFO ] health-status-61              com.vmware.vise.vim.cm.healthstatus.AppServerHealthService        Memory usage: used=475,399,288; max=796,393,472; percentage=59.694021198606706%. Status: GREEN
[2017-10-24T11:40:58.622+03:00] [INFO ] health-status-61              c.v.v.v.cm.HealthStatusRequestHandler$HealthStatusCollectorTask   Determined health status 'GREEN' in 0 ms
[2017-10-24T11:41:39.375+03:00] [ERROR] http-bio-9090-exec-130       70024384 103888 203802 com.vmware.vsphere.client.spbm.util.PbmUtil                       Failed to retrieve VmRollupComplianceSummay:  java.util.concurrent.ExecutionException: (pbm.fault.PBMFault) {
   faultCause = null,
   faultMessage = null
}
at com.vmware.vim.vmomi.core.impl.BlockingFuture.get(BlockingFuture.java:81)
at com.vmware.vsphere.client.spbm.util.PbmUtil.getVmRollupComplianceSummay(PbmUtil.java:726)
at com.vmware.vsphere.client.spbm.impl.PbmMutationProvider.apply(PbmMutationProvider.java:657)
at sun.reflect.GeneratedMethodAccessor3962.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.vmware.vise.data.provider.DelegatingServiceBase.invokeProviderInternal(DelegatingServiceBase.java:400)
at com.vmware.vise.data.provider.DelegatingServiceBase.delegate(DelegatingServiceBase.java:115)
at com.vmware.vise.data.mutation.impl.MutationServiceImpl.apply(MutationServiceImpl.java:150)
at com.vmware.vise.data.mutation.impl.MutationServiceImpl.applyOnMultiEntity(MutationServiceImpl.java:208)
at sun.reflect.GeneratedMethodAccessor3730.invoke(Unknown Source)
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.$Proxy221.applyOnMultiEntity(Unknown Source)
at sun.reflect.GeneratedMethodAccessor3961.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at flex.messaging.services.remoting.adapters.JavaAdapter.invoke(JavaAdapter.java:386)
at com.vmware.vise.messaging.remoting.JavaAdapterEx.invoke(JavaAdapterEx.java:72)
at flex.messaging.services.RemotingService.serviceMessage(RemotingService.java:180)
at flex.messaging.MessageBroker.routeMessageToService(MessageBroker.java:1472)
at flex.messaging.endpoints.AbstractEndpoint.serviceMessage(AbstractEndpoint.java:1046)
at flex.messaging.endpoints.AbstractEndpoint$$FastClassByCGLIB$$1a3ef066.invoke(<generated>)
at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at org.springframework.flex.core.MessageInterceptionAdvice.invoke(MessageInterceptionAdvice.java:66)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.framework.adapter.ThrowsAdviceInterceptor.invoke(ThrowsAdviceInterceptor.java:124)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.framework.Cglib2AopProxy$FixedChainStaticTargetInterceptor.intercept(Cglib2AopProxy.java:573)
at com.vmware.vise.messaging.endpoints.AMFEndpoint$$EnhancerByCGLIB$$883ce869.serviceMessage(<generated>)
at flex.messaging.endpoints.amf.MessageBrokerFilter.invoke(MessageBrokerFilter.java:101)
at flex.messaging.endpoints.amf.LegacyFilter.invoke(LegacyFilter.java:154)
at flex.messaging.endpoints.amf.SessionFilter.invoke(SessionFilter.java:42)
at flex.messaging.endpoints.amf.BatchProcessFilter.invoke(BatchProcessFilter.java:63)
at flex.messaging.endpoints.amf.SerializationFilter.invoke(SerializationFilter.java:190)
at flex.messaging.endpoints.BaseHTTPEndpoint.service(BaseHTTPEndpoint.java:328)
at com.vmware.vise.messaging.endpoints.AMFEndpoint$$EnhancerByCGLIB$$883ce869.service(<generated>)
at org.springframework.flex.servlet.MessageBrokerHandlerAdapter.handle(MessageBrokerHandlerAdapter.java:109)
at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:923)
at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:852)
at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:882)
at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:789)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at com.vmware.vise.security.SessionManagementFilter.doFilterInternal(SessionManagementFilter.java:82)
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at com.vmware.vsphere.client.logging.MDCLogFilter.doFilterInternal(MDCLogFilter.java:41)
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:505)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at org.apache.catalina.valves.RemoteIpValve.invoke(RemoteIpValve.java:683)
at org.eclipse.virgo.web.tomcat.support.ApplicationNameTrackingValve.invoke(ApplicationNameTrackingValve.java:33)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:423)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1079)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:620)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:318)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)
Caused by: com.vmware.vim.binding.pbm.fault.PBMFault: null
at sun.reflect.GeneratedConstructorAccessor944.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at java.lang.Class.newInstance(Class.java:442)
at com.vmware.vim.vmomi.core.types.impl.ComplexTypeImpl.newInstance(ComplexTypeImpl.java:174)
at com.vmware.vim.vmomi.core.types.impl.DefaultDataObjectFactory.newDataObject(DefaultDataObjectFactory.java:25)
at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.ComplexStackContext.<init>(ComplexStackContext.java:30)
at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallSoapFaultContext.parse(UnmarshallerImpl.java:150)
at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallSoapFaultContext.unmarshall(UnmarshallerImpl.java:101)
at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl.unmarshalSoapFault(UnmarshallerImpl.java:88)
at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl.unmarshalSoapFault(UnmarshallerImpl.java:83)
at com.vmware.vim.vmomi.client.common.impl.SoapFaultStackContext.setValue(SoapFaultStackContext.java:40)
at com.vmware.vim.vmomi.client.common.impl.ResponseUnmarshaller.processNextElement(ResponseUnmarshaller.java:127)
at com.vmware.vim.vmomi.client.common.impl.ResponseUnmarshaller.unmarshal(ResponseUnmarshaller.java:70)
at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.unmarshalResponse(ResponseImpl.java:274)
at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.setResponse(ResponseImpl.java:230)
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 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
... 1 common frames omitted

[2017-10-24T11:41:39.383+03:00] [ERROR] http-bio-9090-exec-130       70024384 103888 203802 com.vmware.vsphere.client.spbm.impl.PbmMutationProvider           Failed to check rollup compliance for VM: [69efff8d-d8fc-4fe5-98e5-923db719c141] com.vmware.vim.binding.pbm.fault.PBMFault: null
at sun.reflect.GeneratedConstructorAccessor944.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at java.lang.Class.newInstance(Class.java:442)
at com.vmware.vim.vmomi.core.types.impl.ComplexTypeImpl.newInstance(ComplexTypeImpl.java:174)
at com.vmware.vim.vmomi.core.types.impl.DefaultDataObjectFactory.newDataObject(DefaultDataObjectFactory.java:25)
at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.ComplexStackContext.<init>(ComplexStackContext.java:30)
at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallSoapFaultContext.parse(UnmarshallerImpl.java:150)
at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallSoapFaultContext.unmarshall(UnmarshallerImpl.java:101)
at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl.unmarshalSoapFault(UnmarshallerImpl.java:88)
at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl.unmarshalSoapFault(UnmarshallerImpl.java:83)
at com.vmware.vim.vmomi.client.common.impl.SoapFaultStackContext.setValue(SoapFaultStackContext.java:40)
at com.vmware.vim.vmomi.client.common.impl.ResponseUnmarshaller.processNextElement(ResponseUnmarshaller.java:127)
at com.vmware.vim.vmomi.client.common.impl.ResponseUnmarshaller.unmarshal(ResponseUnmarshaller.java:70)
at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.unmarshalResponse(ResponseImpl.java:274)
at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.setResponse(ResponseImpl.java:230)
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 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)

[2017-10-24T11:41:39.802+03:00] [INFO ] http-bio-9090-exec-130        org.springframework.flex.servlet.MessageBrokerHandlerAdapter      Channel endpoint amf received request.
[2017-10-24T11:41:39.838+03:00] [INFO ] http-bio-9090-exec-128       70024390 103992 203893 org.springframework.flex.servlet.MessageBrokerHandlerAdapter      Channel endpoint amf received request.
[2017-10-24T11:41:39.838+03:00] [INFO ] http-bio-9090-exec-125       70024397 103888 203802 org.springframework.flex.servlet.MessageBrokerHandlerAdapter      Channel endpoint ds-public-amf received request.
[2017-10-24T11:41:39.839+03:00] [WARN ] http-bio-9090-exec-116       70024399 103888 203802 com.vmware.vise.util.session.SessionUtil                          Just clobbered an existing httpRequest
[2017-10-24T11:41:39.839+03:00] [INFO ] http-bio-9090-exec-116       70024399 103888 203802 org.springframework.flex.servlet.MessageBrokerHandlerAdapter      Channel endpoint amf received request.
[2017-10-24T11:41:39.841+03:00] [WARN ] http-bio-9090-exec-133       70024400 103888 203802 com.vmware.vise.util.session.SessionUtil                          Just clobbered an existing httpRequest
[2017-10-24T11:41:39.841+03:00] [INFO ] http-bio-9090-exec-133       70024400 103888 203802 org.springframework.flex.servlet.MessageBrokerHandlerAdapter      Channel endpoint ds-core-amf received request.
[2017-10-24T11:41:39.853+03:00] [INFO ] http-bio-9090-exec-116       70024401 103888 203802 org.springframework.flex.servlet.MessageBrokerHandlerAdapter      Channel endpoint ds-core-amf received request.
[2017-10-24T11:41:40.568+03:00] [INFO ] http-bio-9090-exec-130       70024402 103888 203802 org.springframework.flex.servlet.MessageBrokerHandlerAdapter      Channel endpoint ds-core-amf received request.
[2017-10-24T11:41:40.570+03:00] [INFO ] http-bio-9090-exec-116       70024403 103888 203802 org.springframework.flex.servlet.MessageBrokerHandlerAdapter      Channel endpoint ds-public-amf received request.
[2017-10-24T11:41:40.686+03:00] [INFO ] http-bio-9090-exec-116        org.springframework.flex.servlet.MessageBrokerHandlerAdapter      Channel endpoint amf received request.
[2017-10-24T11:41:40.790+03:00] [ERROR] http-bio-9090-exec-133       70024400 103888 203802 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      getVcService returned null for: GLOBAL
[2017-10-24T11:41:40.791+03:00] [ERROR] http-bio-9090-exec-133       70024400 103888 203802 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      getVcService returned null for: GLOBAL
[2017-10-24T11:41:40.791+03:00] [ERROR] http-bio-9090-exec-133       70024400 103888 203802 com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl      getVcService returned null for: GLOBAL
VCs in group: https://***********:443/sdk(69efff8d-d8fc-4fe5-98e5-923db719c141)
at com.vmware.vise.vim.commons.vcservice.impl.LinkedVcGroupImpl.getVcService(LinkedVcGroupImpl.java:461)
at com.vmware.vise.messaging.amf.vim.ManagedObjectReferenceProxy.getStartupVcService(ManagedObjectReferenceProxy.java:176)
at com.vmware.vise.messaging.amf.vim.ManagedObjectReferenceProxy.getVcVersion(ManagedObjectReferenceProxy.java:111)
at com.vmware.vise.messaging.amf.vim.ManagedObjectReferenceProxy.getValue(ManagedObjectReferenceProxy.java:81)
at flex.messaging.io.amf.Amf3Output.writePropertyProxy(Amf3Output.java:852)
at flex.messaging.io.amf.Amf3Output.writeCustomObject(Amf3Output.java:783)
at flex.messaging.io.amf.Amf3Output.writeObject(Amf3Output.java:221)
at com.vmware.vise.messaging.amf.Amf3Output.writeObject(Amf3Output.java:41)
at flex.messaging.io.amf.Amf3Output.writeObjectProperty(Amf3Output.java:272)
at flex.messaging.io.amf.Amf3Output.writePropertyProxy(Amf3Output.java:853)
at flex.messaging.io.amf.Amf3Output.writeCustomObject(Amf3Output.java:783)
at flex.messaging.io.amf.Amf3Output.writeObject(Amf3Output.java:221)
at com.vmware.vise.messaging.amf.Amf3Output.writeObject(Amf3Output.java:41)
at flex.messaging.io.amf.Amf3Output.writeObjectArray(Amf3Output.java:1106)
at flex.messaging.io.amf.Amf3Output.writeAMFArray(Amf3Output.java:696)
at flex.messaging.io.amf.Amf3Output.writeObject(Amf3Output.java:207)
at com.vmware.vise.messaging.amf.Amf3Output.writeObject(Amf3Output.java:41)
at flex.messaging.io.amf.Amf3Output.writeObjectProperty(Amf3Output.java:272)
at flex.messaging.io.amf.Amf3Output.writePropertyProxy(Amf3Output.java:853)
at flex.messaging.io.amf.Amf3Output.writeCustomObject(Amf3Output.java:783)
at flex.messaging.io.amf.Amf3Output.writeObject(Amf3Output.java:221)
at com.vmware.vise.messaging.amf.Amf3Output.writeObject(Amf3Output.java:41)
at flex.messaging.io.amf.Amf3Output.writeObjectArray(Amf3Output.java:1106)
at flex.messaging.io.amf.Amf3Output.writeAMFArray(Amf3Output.java:696)
at flex.messaging.io.amf.Amf3Output.writeObject(Amf3Output.java:207)
at com.vmware.vise.messaging.amf.Amf3Output.writeObject(Amf3Output.java:41)
at flex.messaging.io.amf.Amf3Output.writeObjectProperty(Amf3Output.java:272)
at flex.messaging.io.amf.Amf3Output.writePropertyProxy(Amf3Output.java:853)
at flex.messaging.io.amf.Amf3Output.writeCustomObject(Amf3Output.java:783)
at flex.messaging.io.amf.Amf3Output.writeObject(Amf3Output.java:221)
at com.vmware.vise.messaging.amf.Amf3Output.writeObject(Amf3Output.java:41)
at flex.messaging.messages.AbstractMessage.writeExternalBody(AbstractMessage.java:703)
at flex.messaging.messages.AbstractMessage.writeExternal(AbstractMessage.java:434)
at flex.messaging.messages.AsyncMessage.writeExternal(AsyncMessage.java:133)
at flex.messaging.messages.AcknowledgeMessage.writeExternal(AcknowledgeMessage.java:92)
at flex.messaging.messages.AcknowledgeMessageExt.writeExternal(AcknowledgeMessageExt.java:53)
at flex.messaging.io.amf.Amf3Output.writePropertyProxy(Amf3Output.java:845)
at flex.messaging.io.amf.Amf3Output.writeCustomObject(Amf3Output.java:783)
at flex.messaging.io.amf.Amf3Output.writeObject(Amf3Output.java:113)
at com.vmware.vise.messaging.amf.Amf3Output.writeObject(Amf3Output.java:41)
at flex.messaging.io.amf.Amf0Output.writeObject(Amf0Output.java:204)
at com.vmware.vise.messaging.amf.Amf0Output.writeObject(Amf0Output.java:41)
at flex.messaging.io.amf.AmfMessageSerializer.writeObject(AmfMessageSerializer.java:157)
at flex.messaging.io.amf.AmfMessageSerializer.writeBody(AmfMessageSerializer.java:147)
at flex.messaging.io.amf.AmfMessageSerializer.writeMessage(AmfMessageSerializer.java:103)
at flex.messaging.endpoints.amf.SerializationFilter.invoke(SerializationFilter.java:222)
at flex.messaging.endpoints.BaseHTTPEndpoint.service(BaseHTTPEndpoint.java:328)
at com.vmware.vise.messaging.endpoints.AMFEndpoint$$EnhancerByCGLIB$$883ce869.service(<generated>)
at org.springframework.flex.servlet.MessageBrokerHandlerAdapter.handle(MessageBrokerHandlerAdapter.java:109)
at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:923)
at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:852)
at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:882)
at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:789)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at com.vmware.vise.security.SessionManagementFilter.doFilterInternal(SessionManagementFilter.java:82)
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at com.vmware.vsphere.client.logging.MDCLogFilter.doFilterInternal(MDCLogFilter.java:41)
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:505)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at org.apache.catalina.valves.RemoteIpValve.invoke(RemoteIpValve.java:683)
at org.eclipse.virgo.web.tomcat.support.ApplicationNameTrackingValve.invoke(ApplicationNameTrackingValve.java:33)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:423)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1079)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:620)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)
[2017-10-24T11:41:40.792+03:00] [WARN ] http-bio-9090-exec-133       70024400 103888 203802 com.vmware.vise.messaging.amf.vim.I18nFilterProxy                 Device order number not found: Keyboard 
[2017-10-24T11:41:40.792+03:00] [WARN ] http-bio-9090-exec-133       70024400 103888 203802 com.vmware.vise.messaging.amf.vim.I18nFilterProxy                 Device order number not found: Pointing device
[2017-10-24T11:41:40.793+03:00] [WARN ] http-bio-9090-exec-133       70024400 103888 203802 com.vmware.vise.messaging.amf.vim.I18nFilterProxy                 Device order number not found: Video card 
[2017-10-24T11:41:40.793+03:00] [WARN ] http-bio-9090-exec-133       70024400 103888 203802 com.vmware.vise.messaging.amf.vim.I18nFilterProxy                 Device order number not found: VMCI device
[2017-10-24T11:41:41.410+03:00] [WARN ] http-bio-9090-exec-132       70024405 103888 203802 com.vmware.vise.util.session.SessionUtil                          Just clobbered an existing httpRequest
[2017-10-24T11:41:41.410+03:00] [INFO ] http-bio-9090-exec-132       70024405 103888 203802 org.springframework.flex.servlet.MessageBrokerHandlerAdapter      Channel endpoint ds-core-amf received request.
[2017-10-24T11:41:41.558+03:00] [INFO ] http-bio-9090-exec-132       70024406 103888 203802 org.springframework.flex.servlet.MessageBrokerHandlerAdapter      Channel endpoint ds-core-amf received request.

0 Kudos
TheBobkin
Champion
Champion
‎10-24-2017 09:38 AM
Jump to solution

Hello Dmitry,

It looks like it is failing to retrieve the compliance data:

[2017-10-24T11:41:39.375+03:00] [ERROR] http-bio-9090-exec-130       70024384 103888 203802 com.vmware.vsphere.client.spbm.util.PbmUtil                       Failed to retrieve VmRollupComplianceSummay:  java.util.concurrent.ExecutionException: (pbm.fault.PBMFault) {

   faultCause = null,

   faultMessage = null

}

And thus can't check the compliance:

[2017-10-24T11:41:39.383+03:00] [ERROR] http-bio-9090-exec-130       70024384 103888 203802 com.vmware.vsphere.client.spbm.impl.PbmMutationProvider           Failed to check rollup compliance for VM: [69efff8d-d8fc-4fe5-98e5-923db719c141] com.vmware.vim.binding.pbm.fault.PBMFault: null

You should open a support request with GSS, likely a System Management engineer should look into the above closer and/or use this as a starting point for analyzing other logs to narrow down the cause.

Bob

0 Kudos
dmitry_er
Contributor
Contributor
‎10-26-2017 08:25 AM
Jump to solution

listing from /var/log/vmware/vmware-sps

2017-10-26T18:13:12.242+03:00 [pool-32-thread-2] ERROR opId=CheckVmRollupComplianceResolver-applyOnMultiEntity-18076-ngc:70001902 com.vmware.vim.sms.provider.ProviderCache - [getProvider] No provider exists with uid: a7989ced-5755-4ee3-ac14-dd475c32e254

2017-10-26T18:13:12.242+03:00 [pool-32-thread-2] ERROR opId=CheckVmRollupComplianceResolver-applyOnMultiEntity-18076-ngc:70001902 com.vmware.vim.sms.provider.ProviderFactory - [getActiveProvider] Failed to retrieve the provider!

(vim.fault.NotFound) {

   faultCause = null,

   faultMessage = null

}

at com.vmware.vim.sms.provider.ProviderFactory.getProvider(ProviderFactory.java:348)

at com.vmware.vim.sms.provider.ProviderFactory.getActiveProvider(ProviderFactory.java:390)

at com.vmware.vim.sms.provider.ProviderFactory.getVasaClientRetryProxy(ProviderFactory.java:365)

at com.vmware.vim.sms.policy.PolicyManagerImpl.queryComplianceResult(PolicyManagerImpl.java:174)

at com.vmware.sps.pbm.impl.LocalSMSServiceImpl.queryComplianceResult(LocalSMSServiceImpl.java:68)

at com.vmware.sps.pbm.compliance.ObjectStorageComplianceTask.run(ObjectStorageComplianceTask.java:160)

at com.vmware.vim.storage.common.task.opctx.RunnableOpCtxDecorator.run(RunnableOpCtxDecorator.java:38)

at com.vmware.vim.storage.common.task.opctx.RunnableOpCtxDecorator.run(RunnableOpCtxDecorator.java:38)

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

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

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

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

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

How to remove this provider with uid: a7989ced-5755-4ee3-ac14-dd475c32e254 ?

0 Kudos
dmitry_er
Contributor
Contributor
‎11-14-2017 10:53 AM
Jump to solution

I contacted vSAN support and they resolved the issue.

They removed nonexistent providers.

0 Kudos
TheBobkin
Champion
Champion
‎11-14-2017 11:33 AM
Jump to solution

Hello Dmitry,

Thanks for updating here - always good to hear how things were solved.

Can you share any details regarding the method of removing nonexistent providers?

Did it involve manual removal from the vCenter DB, invoke via the MOB interface or just removed from VASA providers in Web Client?

Bob

0 Kudos