CUCM 9.1.2 Kernel Alert

[hanlykent]

Hi All,

Since my failed CUCM upgrade to 10.5(2) yesterday, our CUCM 9.1(2)su2 system has sporadically alerted the following every few hours:

SeverityMatch : Critical

MatchedEvent :
Jan 25 00:00:00 {publisher node name} kern 2 kernel: dbcfs: compressor thread unable to open file /var/log/active/cm/trace/cti/sdl/SDL001_200.index

AppID : Cisco Syslog Agent

ClusterID : 

NodeID : {publisher node name}

TimeStamp : Sun Jan 25 00:00:01 EST 2015

Any insight would be much appreciated.

Thanks

Kent

[Manish Gogna]

Hi Kent,

This alert is specific to a CTI trace file and should not be a cause of any concern. You can try restarting the CTI manager service on this node and see if it is cleared.

HTH

Manish

[jchorlton]

Hi,

Did you figure this out.  (I have also had a failed 10.52 upgrade and I am now seeing something very similar).

Have also noticed that my CDR has stopped outputting.

Thanks

J

[Charles Hill]

Hello jchorlton,

The two bugs/caveats below reference an :

-> upgrade issue to 10.x 

-> CDR analysis and reporting

However, when I attempt to pull up the CSCun60193 bug, it pulls up another bug that references another trouble, that is supposedly a duplicate, but it doesn't look like a duplicate to me.

CSCuj02641

: CAR warning messages in tomcat logs

CSCun60193

: Upgrade from 912 -> 10x runs into

Disk space issues when using 80G disks

Here is a pdf cucm 9.1(2)su2 that references the above caveats.

http://www.cisco.com/web/software/282074295/113937/cucm-readme-912su2.pdf

Hope this helps.

[d.haeni]

J,

I'm exactly where you were some 7 month ago (I get CDRAgentSendFileFailed after a failed upgrade from 9.1 to 10.5)

Were you able to fix the CDR issue on 9.1? Were you able to upgrade eventually?

Thx

/David

[hanlykent]

Hi David,

Yes, we upgraded to 10.5.2 which resolved the CDR issue.

The failure and resolution to the upgrade is recorded here:

https://supportforums.cisco.com/discussion/12404921/cucm-912-1052-failure

Cheers

Kent