hi,
i've already installed 2 cucm which is one i assign as publisher and the other one as subscriber using clustering. All the database i've put in the cucm pub so that cucm sub will get automatically the database from the pub. after 3 days i've playing with both cucm, the pub cucm goes down and shown an error

EXT3-fs error (device sda6) in start_transaction: Journal has aborted.

i've done the recovery process by using recovery cd,but after a few hours, it shown back this error. i do the same process (recovery), and at last, the other error come out which is

Message from syslogd@CallManager-01 at Mon Jun 6 17:05:39 2011 ... CallManager-01 local7 0 : 1: CallManager-01.unimap.edu.my: Jun 06 2011 09:05:39.508 UTC : %UC_SERVICEMANAGER-0-FailedToReadConfig: %[Filename=/usr/local/platform/conf/activate.conf][Reason=XML Parser failed][AppID=Cisco Service Manager][ClusterID=][NodeID=CallManager-01]: Service Manager failed to read configuration file.

How can i recover back my cucm publisher without losing any database that i've entered before?

can anybody help me to resolve this problem? really need your help.

What version is it? As far as I know from version above 6.0, you have to install the CUCM software in a virtual machine(for educational purposes). The software MUST be installed in a MCS server for production purposes.

Thanks a lot for respond carlitos. I use version 8.0 and i've installed the software in MCS server for production purposes. Yesterday, i've reinstalled back my server using installation cd given by Cisco. After one night and today i've found the error "EXT3-fs error (device sda6) in start_transaction: Journal has aborted" occurred again.

It is because of the hardware corrupted or any other reason? Because it just happen at 'device sda6' only.

I think Google is your only help now. I found this:

http://rackerhacker.com/2007/11/20/ext3-fs-error-device-hda3-in-start_transaction-journal-has-aborted/

May be if you know Linux, you could understand that.

I've found this article and it's not helping me in solving my problem.

run the CUCM recovery DVD if the problem persists open a case with TAC

Anytime you get an EXT3 error, that's either the hardware or the OS dying; I'm pretty sure there is a firmware update from Cisco to update the hard drive firmware which should fix this.

_________________
"A problem well stated is a problem half solved". (Charles Kettering)