VCSA Stale Task - vSphere Client service has stopped working

VCSA Stale Task – vSphere Client service has stopped working

1 year ago

You follow KB 378061 to clear a stale task from vCenter by stopping and starting the vsphere-ui service (VMware vSphere Client).
Example reason – vCenter still thinks a s-vmotion is still taking place when the ESXi host and datastore show it is complete.
Issue – The vCenter login page reports – vSphere Client service has stopped working.

Testing on
VCSA 7.0.3 21290409
VCSA 8.0.3 24022515
I prefer to run the stop and start commands one at a time to validate the stop and start succeeded.

SSH into the VCSA as root.

service-control --stop --verbose vsphere-ui

service-control --status --verbose vsphere-ui

service-control --start --verbose vsphere-ui

service-control --status --verbose vsphere-ui

Run the 2nd command for vmware-vpxd (VMware vCenter Server listed in https://knowledge.broadcom.com/external/article?articleNumber=344633) , then stop/start the vsphere-ui again. My guess why is some dependency/sequence reason.

service-control --stop --verbose vmware-vpxd
service-control --status --verbose vmware-vpxd
service-control --start --verbose vmware-vpxd
service-control --status --verbose vmware-vpxd


service-control --stop --verbose vsphere-ui
service-control --status --verbose vsphere-ui
service-control --start --verbose vsphere-ui
service-control --status --verbose vsphere-ui