A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x0045eed5, pid=1298, tid=2275924848 # # JRE version: Java(TM) SE Runtime Environment (7.0_85-b15) (build 1.7.0_85-b15) # Java VM: Java HotSpot(TM) Server VM (24.85-b06 mixed mode linux-x86 ) # Problematic frame: # C [libc.so.6+0x60ed5] fgets+0x35 # # Core dump written. Default location: //core or core.1298 # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. #
--------------- T H R E A D ---------------
Current thread (0x0b2dd400): JavaThread "localhost-startStop-2" daemon [_thread_in_native, id=5526, stack(0x87a2d000,0x87a7e000)]
I had an issue reported by the users organisation wide that they are not able to access voicemail and send voicemail.
The fix was: restarted 2 services "Connection Conversation Manager" & "Connection Mixer". Once these services are restarted, wait for a couple of minutes and check the functionality of the voicemail by sending and accessing the same.
You can find both these services in :
Cisco Unity Connection Web Page(Version 18.104.22.16800-9) > Cisco Unity Connection Serviceability > Tools > Service Management > Critical Services.
Note: Restart(Stop & Start) the services one after the other (Wait for the fisrt one to come up and go for the next service)
We had a similar issue and it seems to reoccur after connection conversation manager has been running for a long period of time. This latest occurrence was after the connection manager service was up for 2301 hours. Access to voicemail is sporadic when the issue occurs in our environment. Most of the time users can access voicemail, but every so often a user cannot. Restarting the connection conversation manager service on each server resolves the problem. FWIW, we're running CUC and CUCM version 10.5(2)SU2 which I thought was a version that resolved this bug.
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.