PeterRTVS
Contributor
Contributor

vCenter 7 unable to use update menus...

Jump to solution

Hi,

I have now upgraded my older vCenter Essentials 6.7U3 to the

After the complete check I was unable go to the updates menus (baselines, HW Tools, VM Hardware). I have there still the rotating wheel.

So I cant acces the Baselines and set it to upgrade my hosts.

I have also I thing with it builded another issues or problems:

1.     In LifeCycle manager I have these error: Status 404 - https://x.x.x.x/ui/vum-ui/rest/vcenters/5a8080e2-5dca-434a-87f4-303c3cb3f9b1/compliance

2.     Anny update menu (submenu or settins) end with rotating wheel

3.     By patch Setup menu have unexpected error

Please is possible to help me?

Thanks.

0 Kudos
1 Solution

Accepted Solutions
vTara
VMware Employee
VMware Employee

Hi Peter,

Have you tried to reset the VUM/vLCM DB Reset ?

Note: This might lead you to manually recreate any custom baseline you might have created.

To reset the DB please check this KB: VMware Knowledge Base

Regards

Tami

Install-Upgrade Specialist

_______________________________________________________________________________________________________

"Did you find this helpful? Let us know by completing this survey (takes 1 minute!)"

View solution in original post

0 Kudos
16 Replies
vTara
VMware Employee
VMware Employee

Hi Peter,

You can try to stop html5 client service and rename the work directory using the below commands,

service-control --stop vsphere-ui

mv /usr/lib/vmware-vsphere-ui/server/work /usr/lib/vmware-vsphere-ui/server/work_old

service-control --start vsphere-ui

And retry to login and check if you still getting unexpected error, if you still receive same error check these logs files,

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

/var/log/vmware/vmware-updatemgr/vum-server/lifecycle.log

Regards

Tami

Install-Upgrade Specialist

0 Kudos
PeterRTVS
Contributor
Contributor

Hi vTara,

I have try it but its the same nothing has changed.

Still have there all the errors, even the first WEB UI start was after more reloads, while from begining I had only a white screen.

Any other idea what can cause it?

Thanks.

0 Kudos
vTara
VMware Employee
VMware Employee

Hi Peter,

Did you get any clues from the logs ?

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

/var/log/vmware/vmware-updatemgr/vum-server/lifecycle.log

Regards

Tami

Install-Upgrade Specialist

0 Kudos
PeterRTVS
Contributor
Contributor

Hi vTara,

I found these in the logs:

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

[2020-06-05T14:27:22.563+02:00] [INFO ] http-nio-5090-exec-5      com.vmware.vum.client.websocket.VumWebSocketEndpoint          [VumWebsocket] onClose: 11 CloseReason: code [1000], reason [null]
[2020-06-05T14:27:26.865+02:00] [INFO ] http-nio-5090-exec-9      com.vmware.vise.util.session.SessionUtil                      Generated hashed session id: 100059
[2020-06-05T14:27:26.865+02:00] [INFO ] http-nio-5090-exec-9     70000634 100059 ###### com.vmware.vise.security.SessionListener                      Session 100059 created with context path: /ui
[2020-06-05T14:27:26.869+02:00] [WARN ] http-nio-5090-exec-7      org.springframework.web.servlet.PageNotFound                  No mapping found for HTTP request with URI [/ui/vum-ui/rest/vcenters/5a8080e2-5dca-434a-87f4-303c3cb3f9b1/compliance] in DispatcherServlet with name 'springServlet'
[2020-06-05T14:27:37.704+02:00] [INFO ] or[StandardEngine[Catalina]]  com.vmware.vise.security.SessionListener                      sessionDestroyed invoked for sessionId 100026
[2020-06-05T14:27:37.705+02:00] [WARN ] or[StandardEngine[Catalina]] ######## 100026 ###### com.vmware.vise.security.SessionListener                      No clientId found for session 100026 with context-path {/ui
[2020-06-05T14:28:27.006+02:00] [INFO ] http-nio-5090-exec-9      com.vmware.vise.util.session.SessionUtil                      Generated hashed session id: 100060
[2020-06-05T14:28:27.007+02:00] [INFO ] http-nio-5090-exec-9     70000641 100060 ###### com.vmware.vise.security.SessionListener                      Session 100060 created with context path: /ui
[2020-06-05T14:28:37.708+02:00] [INFO ] or[StandardEngine[Catalina]]  com.vmware.vise.security.SessionListener                      sessionDestroyed invoked for sessionId 100027
[2020-06-05T14:28:37.708+02:00] [WARN ] or[StandardEngine[Catalina]] ######## 100027 ###### com.vmware.vise.security.SessionListener                      No clientId found for session 100027 with context-path {/ui
[2020-06-05T14:29:19.463+02:00] [INFO ] health-status-4           com.vmware.vise.vim.cm.healthstatus.AppServerHealthService    Memory usage: used=325,490,208; max=557,842,432; percentage=58.348054814159426%. Status: GREEN
[2020-06-05T14:29:19.463+02:00] [INFO ] health-status-4           c.v.v.v.cm.HealthStatusRequestHandler$HealthStatusCollectorTask   Determined health status 'GREEN' in 0 ms
[2020-06-05T14:29:27.096+02:00] [INFO ] http-nio-5090-exec-7      com.vmware.vise.util.session.SessionUtil                      Generated hashed session id: 100061
[2020-06-05T14:29:27.097+02:00] [INFO ] http-nio-5090-exec-7     70000648 100061 ###### com.vmware.vise.security.SessionListener                      Session 100061 created with context path: /ui
[2020-06-05T14:29:37.712+02:00] [INFO ] or[StandardEngine[Catalina]]  com.vmware.vise.security.SessionListener                      sessionDestroyed invoked for sessionId 100029
[2020-06-05T14:29:37.713+02:00] [WARN ] or[StandardEngine[Catalina]] ######## 100029 ###### com.vmware.vise.security.SessionListener                      No clientId found for session 100029 with context-path {/ui
[2020-06-05T14:30:01.469+02:00] [WARN ] http-nio-5090-exec-10     org.springframework.web.servlet.PageNotFound                  No mapping found for HTTP request with URI [/ui/vum-ui/rest//nodes/5a8080e2-5dca-434a-87f4-303c3cb3f9b1/notifications] in DispatcherServlet with name 'springServlet'

/var/log/vmware/vmware-updatemgr/vum-server/lifecycle.log

ImageManagerCTL: 35947: 2020-06-05 14:27:30,010 imagemanagerctl:373 INFO Done: manifests' info from depot

ImageManagerCTL: 36218: 2020-06-05 14:27:30,871 imagemanagerctl:976 INFO Calling with arguments: depotInfo --getcomponentinfo /storage/updatemgr/patch-store/hostupdate/__hostupdate20-consolidated-index__.xml

ImageManagerCTL: 36218: 2020-06-05 14:27:30,871 imagemanagerctl:354 INFO Get component info from depot /storage/updatemgr/patch-store/hostupdate/__hostupdate20-consolidated-index__.xml

ImageManagerCTL: 36218: 2020-06-05 14:27:30,884 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/vmw/vmw-ESXi-7.0-vmtools-11.1-metadata.zip

ImageManagerCTL: 36218: 2020-06-05 14:27:30,891 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/vmw/VMW-ESXi-7.0-IOVP-cumulative_metadata.zip

ImageManagerCTL: 36218: 2020-06-05 14:27:30,922 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/vmw/vmw-ESXi-6.5.0-metadata.zip

ImageManagerCTL: 36218: 2020-06-05 14:27:32,494 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/vmw/vmw-ESXi-6.7.0-metadata.zip

ImageManagerCTL: 36218: 2020-06-05 14:27:33,784 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/vmw/vmw-ESXi-7.0.0-metadata.zip

ImageManagerCTL: 36218: 2020-06-05 14:27:33,984 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/vmw/metadata-159.zip

ImageManagerCTL: 36218: 2020-06-05 14:27:34,029 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/vmw/vmw-ESXi-6.0.0-metadata.zip

ImageManagerCTL: 36218: 2020-06-05 14:27:35,513 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/INT/metadata-175.zip

ImageManagerCTL: 36218: 2020-06-05 14:27:35,568 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/QLogic/metadata-121.zip

ImageManagerCTL: 36218: 2020-06-05 14:27:35,646 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/CHL/metadata-51.zip

ImageManagerCTL: 36218: 2020-06-05 14:27:35,724 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/EMU/metadata-135.zip

ImageManagerCTL: 36218: 2020-06-05 14:27:35,782 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/EMC/metadata-159.zip

ImageManagerCTL: 36218: 2020-06-05 14:27:35,844 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/DEL/DEL-ESXi-7.0-Addon-cumulative_metadata.zip

ImageManagerCTL: 36218: 2020-06-05 14:27:35,958 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/HPE/HPE-ESXi-7.0-Addon-cumulative_metadata.zip

ImageManagerCTL: 36218: 2020-06-05 14:27:36,075 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/fjt/FJT-ESXi-7.0-Addon-cumulative_metadata.zip

ImageManagerCTL: 36218: 2020-06-05 14:28:05,644 imagemanagerctl:373 INFO Done: components' info from depot

And please is possible to tell me how can I export or get the logs that I can use it in my PC?

Thanks.

0 Kudos
vTara
VMware Employee
VMware Employee

Hi Peter,

From the above snippets I did not get much details as such. Can you take a putty session and run tail -f /var/log/vmware/vmware-updatemgr/vum-server/lifecycle.log and click on the Life Cycle Manager to get the unexpected error and make a note of the time stamp and press Ctrl+C to stop the log flow and check around the same time if you see any error message. If not check in the offline downloaded log bundle around the same time.

To collect the logs follow the below steps:

Collecting a support bundle from vCenter 6.x/7.x Server Appliance using a web browser

Open a web browser and navigate to https://vCenter_server_FQDN:443/appliance/support-bundle

  1. When prompted enter the root credentials and click Enter.

    The download will begin automatically as vm-support.tgz.

For more details check this KB: VMware Knowledge Base

Regards

Tami

Install-Upgrade Specialist

0 Kudos
PeterRTVS
Contributor
Contributor

Hi vTara,

thanks for help. I have done it, but in logs is nothig:

tail -f /var/log/vmware/vmware-updatemgr/vum-server/lifecycle.log

ImageManagerCTL: 16732: 2020-06-08 06:59:11,411 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/vmw/vmw-ESXi-6.0.0-metadata.zip

ImageManagerCTL: 16732: 2020-06-08 06:59:12,903 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/INT/metadata-175.zip

ImageManagerCTL: 16732: 2020-06-08 06:59:12,963 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/QLogic/metadata-121.zip

ImageManagerCTL: 16732: 2020-06-08 06:59:13,029 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/CHL/metadata-51.zip

ImageManagerCTL: 16732: 2020-06-08 06:59:13,089 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/EMU/metadata-135.zip

ImageManagerCTL: 16732: 2020-06-08 06:59:13,151 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/EMC/metadata-159.zip

ImageManagerCTL: 16732: 2020-06-08 06:59:13,212 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/DEL/DEL-ESXi-7.0-Addon-cumulative_metadata.zip

ImageManagerCTL: 16732: 2020-06-08 06:59:13,274 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/HPE/HPE-ESXi-7.0-Addon-cumulative_metadata.zip

ImageManagerCTL: 16732: 2020-06-08 06:59:13,365 Metadata:116 INFO Reading metadata zip /storage/updatemgr/patch-store/hostupdate/fjt/FJT-ESXi-7.0-Addon-cumulative_metadata.zip

ImageManagerCTL: 16732: 2020-06-08 06:59:46,146 imagemanagerctl:373 INFO Done: components' info from depot

but what i dont understand, is that after restartof vCenter and some days of free working is it now working. Can be th eproblem only in that, that after upgrade it needed a longer time to check evrything, and actualoise his databases?

Thanks.

0 Kudos
scott28tt
VMware Employee
VMware Employee

Moderator: Thread moved to the vSphere Upgrade & Install area.


-------------------------------------------------------------------------------------------------------------------------------------------------------------

Although I am a VMware employee I contribute to VMware Communities voluntarily (ie. not in any official capacity)
VMware Training & Certification blog
0 Kudos
vTara
VMware Employee
VMware Employee

Hi Peter,

Have you tried to reset the VUM/vLCM DB Reset ?

Note: This might lead you to manually recreate any custom baseline you might have created.

To reset the DB please check this KB: VMware Knowledge Base

Regards

Tami

Install-Upgrade Specialist

_______________________________________________________________________________________________________

"Did you find this helpful? Let us know by completing this survey (takes 1 minute!)"

0 Kudos
PeterRTVS
Contributor
Contributor

Hi vTara,

thanks, all together helped.

Now it working.

0 Kudos
tbm_dk
Contributor
Contributor

I had the same error, but for me it was just the borwser cache, that needed to cleared

AllanKjaer
Enthusiast
Enthusiast

I had the same error, but for me it was just the browser cache, that needed to cleared

hazmuka-spc-net
Contributor
Contributor

Clear the cache working for me too. Thanks for forum.

AllanKjaer
Enthusiast
Enthusiast

I LifeCycle manager I have these error: Status 404 - https://x.x.x.x/ui/vum-ui/rest/vcenters/5a8080e2-5dca-434a-87f4-303c3cb3f9b1/compliance

This is a known issue with 7.0 Update 3. 

See this VMware KB: https://kb.vmware.com/s/article/85962

0 Kudos
kalweins
Contributor
Contributor

Thanks

0 Kudos
NoSoup4Jared
Contributor
Contributor

Thank you.  Clear browser cache worked !

AbbasZ
Contributor
Contributor

Thanks. I faced same issue and it was just browser cache for me. Clearing cache fixed the issue and I was able to create baselines.

Tags (1)
0 Kudos