CCM automatic restart of 2 services

Post a reply


In an effort to prevent automatic submissions, we require that you complete the following challenge.
Smilies
:D :) ;) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :!: :?: :idea: :arrow: :| :mrgreen: :geek: :ugeek:

BBCode is ON
[img] is ON
[flash] is OFF
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: CCM automatic restart of 2 services

Re: CCM automatic restart of 2 services

by anjireddy.thatiparti » Wed Apr 01, 2015 9:35 pm

We also same issue is there any fix

[ ccmFailCauseCode = timerThreadDied(4) ]
[ ccmFailCauseCode - The Cause code of the failure. This cause is derived from a monitoring thread in the CallManager or from a heartbeat monitoring process. unknown: Unknown heartBeatStopped: The CallManager stops generating a heartbeat routerThreadDied: The CallManager detects the death of the router thread timerThreadDied: The CallManager detects the death of the timer thread criticalThreadDied: The CallManager detects the death of one of its critical threads deviceMgrInitFailed: The CallManager fails to start its device manager subsystem digitAnalysisInitFailed: The CallManager fails to start its digit analysis subsystem callControlInitFailed: The CallManager fails to start its call control subsystem linkMgrInitFailed: The CallManager fails to start its link manager subsystem dbMgrInitFailed: The CallManager fails to start its database manager subsystem msgTranslatorInitFailed: The CallManager fails to start its message translation manager subsystem suppServicesInitFailed: The CallManager fails to start its supplementary services subsystem. ]

Re:CCM automatic restart of 2 services

by Guest » Sat Oct 22, 2005 7:20 am


CCM_CALLMANAGER-CALLMANAGER-3-CallManagerFailure : Indicates some failure in the Cisco CallManager system.  Additional Text [Optional] [String] Host name of hosting node. [String] IP address of hosting node. [String] Reason code. [Enum]Explanation   This alarm indicates that some failure occurred in the Cisco CallManager system.Recommended Action   Monitor for other alarms and restart Cisco CallManager service, if necessary. Reason Code - Enum Definitions Enum Definitions - ReasonValue Definition 1 Unknown 2 HeartBeatStopped 3 RouterThreadDied 4 TimerThreadDied 5 CriticalThreadDied 6 DeviceMgrInitFailed 7 DigitAnalysisInitFailed 8 CallControlInitFailed 9 LinkMgrInitFailed 10 DBMgrInitFailed 11 MsgTranslatorInitFailed 12 SuppServiceInitFailed This is a BUGhttp://www.cisco.com/en/US/ts/fn/631/fn63174.html

Re:CCM automatic restart of 2 services

by Guest » Sat Oct 22, 2005 7:04 am


Same problem for me as weillreason code 4

CCM automatic restart of 2 services

by Guest » Sat Oct 22, 2005 6:33 am


Hello guys,I'm facing major issue with Call manager. Some days ago I got this automatic reboot on my CCM. Anyone have faced the same issue? As far as I know noone did access my CCM and only this 2 services were restarted. - Callmanager app - CTI manager This caused my contact center to stop working.I'm using System version: 6.1.2.1000-13Here is the LoG:May 13 07:04:06, 127.0.0.1, Info, 140, : May 13 05:04:06.213 UTC : %CCM_SERVICEMANAGER-GENERIC-6-ServiceStopped: Service stopped. Service Name:Cisco CTIManager App ID:Cisco Service Manager Cluster ID:Node ID:cucm1, 50927May 13 07:04:11, 127.0.0.1, Info, 141, : May 13 05:04:11.516 UTC : %CCM_SERVICEMANAGER-GENERIC-6-ServiceStarted: Service started. Service Name:Cisco CTIManager Process ID:26260 App ID:Cisco ServiceManager Cluster ID: Node ID:cucm1, 50928May 13 07:04:12, cucm1, Info, CTIManager, : DBL SDI Initialization successful, 50929May 13 07:04:12, cucm1, Info, CTIManager, : SysLevel [127] UserMask [1] Enable [TRUE] File[/var/log/active/cm/trace/dbl/sdi/dbl.log], 50930May 13 07:04:15, cucm1, Info, CTIManager, : DBNotify SDI Initialization successful, 50931May 13 07:04:15, cucm1, Info, CTIManager, : SysLevel [127] UserMask [2] Enable [TRUE] File[/var/log/active/cm/trace/dbl/sdi/dbnotify.log], 50932May 13 07:04:17, cucm1, Info, Cisco CTIManager, : SDIDBConfigData:Read successful. ServiceID=4,NodeName=172.16.109.2, 50933May 13 07:04:17, cucm1, Error, , : Unable to resolve the Syslog Server Name, 50934May 13 07:04:53, 127.0.0.1, Info, 142, : May 13 05:04:52.954 UTC : %CCM_SERVICEMANAGER-GENERIC-6-ServiceStopped: Service stopped. Service Name:Cisco CallManager App ID:Cisco Service Manager Cluster ID:Node ID:cucm1, 50935May 13 07:04:56, cucm1, Info, ccm, : DBL SDI Initialization successful, 50936May 13 07:04:56, cucm1, Info, ccm, : SysLevel [127] UserMask [1] Enable [TRUE] File[/var/log/active/cm/trace/dbl/sdi/dbl.log], 50937May 13 07:04:58, cucm1, Info, ccm, : DBNotify SDI Initialization successful, 50938May 13 07:04:58, cucm1, Info, ccm, : SysLevel [127] UserMask [2] Enable [TRUE] File[/var/log/active/cm/trace/dbl/sdi/dbnotify.log], 50939May 13 07:05:00, 127.0.0.1, Info, 143, : May 13 05:05:00.272 UTC : %CCM_SERVICEMANAGER-GENERIC-6-ServiceStarted: Service started. Service Name:Cisco CallManager Process ID:26490 App ID:Cisco ServiceManager Cluster ID: Node ID:cucm1, 50940Thank you all for your help and support!

Top