CM Error

[Jake Rounkles]

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

and

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?

TIA

Jake

[Adrian Saavedra]

Hello,

I had similar issue with version 7.1.2. Can't use the web or ping the server. It was a bug -> CSCta73022.

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCta73022

I applied latest update and that fixed. You should verify with TAC if it's related.

Hope it helps, please rate if it does.

Kind regards,

- Adrian.