04-24-2025 01:21 PM
Currently have a single UCCX server running 12.5.1.11002-481 that has been working fine for a number of years. It's still impacted by the Bug (CSCvy99583) which requires services restart every 180 days, so logged in yesterday to restart and was greeted w/ a message about an unexpected shutdown (the shutdown occurred 331 days ago but this was the first time this error popped up). Checking the system-history log I saw the reboot. But the issue is the screen just hangs after the message about the unexpected shutdown. You never get the "admin:" prompt, either through ssh or the console. I imagine the reboot from the GUI via the OS admin page should work, but wondering if there is anything else that can be looked at or if the best approach is to just reboot via GUI.
10-29-2025 03:04 PM
Dear mumbles202,
You can alternatively perform a Guest OS from ESXi. The following link shows the steps to do this:
https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/vsphere-single-host-management-vmware-host-client-8-0/virtual-machine-management-with-the-vsphere-host-client-vSphereSingleHostManagementVMwareHostClient/managing-a-guest-operating-sy...
Hope this information helps,
Sincerely,
Marco R.
10-31-2025 03:15 AM
If the admin CLI hangs then it sounds like there is definitely something corrupted. If you have TAC support, you can try to pursue that with them. If not, you will likely need to do a DRS backup, rebuild the node(s) from scratch, and then a DRS restore to get the data back. That is a disruptive process, obviously. If you do the rebuild on new VM's, that will change your licensing information and you would have to involve GLO to get that re-hosted if you are using node specific licenses. That isn't a problem if it is registered with smart licensing.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide