We are running CallManager 7.1(5) and the Administration page will not load. I tried to restart the Tomcat service but had not luck. I went to the console and it is scrolling the following message:
ext3-fs error (device sda6) in start_transaction: Journal has aborted
When I sign on to the console I am presented the following error msgs:
Please use Recovery disk to check file system using fsck
log4j: Error no output stream or file set for the appender name (CLI_LOG)
I am downloading the most recent Recovery Disk from Cisco.com but before I start rebooting or start the recovery process I wanted to see if anyone has come across this and if so what did you do to fix the issue?
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...