Guest

Preview Tool

Cisco Bug: CSCup27133 - CCM Service Parameter "CUCMOverallInitializationTime' value is incorrect

Last Modified

Jul 03, 2017

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

8.6(2.24122.1)

Description (partial)

Symptom:ccm traces may show:
21:18:35.852 |CMProcMon::waitForCMExit - CUCMOverallInitializationTime is 0, reset to 60, CHECK THIS VALUE OR THE CAUSE FOR THIS|*^*^*
21:18:35.852 |CMProcMon::waitForCMExit, now: 05/23/2014 21:18:35--application will exit if initialization does not complete by: 05/23/2014 22:18:35|*^*^*

000002728 |2014/05/21 06:05:35.604 |100 |AlarmErr  |                                       |                               |                                 |                                 |                                         |AlarmClass: CallManager, AlarmName: CMOverallInitTimeExceeded, AlarmSeverity: Alert, AlarmMessage: , AlarmDescription: Initialization of the Unified CM system has taken longer than allowed by the System Initialization Timer service parameter; the system automatically restarts to attempt initialization again, AlarmParameters:  CMOverallInitializationTime:0, AppID:Cisco CallManager, ClusterID:StandAloneCluster, NodeID:CUCM-PUB,

Conditions:This occurs during initialization on most systems.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.