Here's the background. I have two CUC servers in a cluster. About a week ago we started noticing extremely slow voicemail response (upwards of 30 seconds). During this time the web page and SSH response from the servers was extremely slow. To the point I could not manage them and had to hard boot the primary CUC server. This fixed the problem for 5 days then the same problem came back. Except this time I could pull up the web page and SSH to the backup CUC server fine. I still had problems accessing the primary CUC server and again hard booted it. This time it did not come back online so I'm running on the backup now as primary. We're still exhibiting the same delay except it is not on all calls this time. Sometimes when I access voicemail it picks up right away and works fine. Other times I see the long delay. Could I be hitting ports from the UCM to the CUC that are down because of the primary server being powered off? I've been working with TAC and they suspected the IMAP process that was showing high CPU utilization but we turned that off and the issue is still here.
Here's some output from the backup CUC server that is online:
Host Name : CUC-02
Date : Wed Jan 15, 2014 07:24:45
Time Zone : Eastern Standard Time (America/New_York)
I'm having a similar issue in my Unity Cluster as well. The first and second time, everything went back to normal after rebooting the Publisher. The third time I rebooted the Publisher, the services failed to start and we were not able to bring the Publisher up. Cisco found that the sadmin db was full which might have caused this issue, However there is no fix yet and the suggestion was to perform the dbOverwrite which is not preferable. Just wondering if you managed to find the solution of this problem?
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.