I recently upgraded our CUC cluster from 9.1.1.20000-5 to 9.1.2.14900-14. Upgrade went fine and everything appears to be working. However, on my Publisher, the Connection Serviceability feature service is active but stopped. I've rebooted the Pub, still stopped. I've tried starting the service through CLI with utils service start Connection Serviceability, command failed. Service is running fine on Sub and I can access the cuservice page on both the Pub and Sub. Under cluster management, Pub is running as Primary and Sub as secondary. Anyone ever run into this? Should it be this way? If not, thoughts on resolving?
Also, Connection Administration was the same way after upgrade and reboot, but was able to start by simply clicking on the Start button. Haven't rebooted server since I manually started this service to see if it automatically starts.
Thanks guys!
