Cisco Unified Communications Manager (CallManager)

How to Identify an Unexpected Shutdown of a CUCM, UC, or UCCX Server

Document ID: 116717

Updated: Nov 05, 2013

Contributed by Adam Frankel, Cisco TAC Engineer.



This document describes how to identify an unexpected shutdown of a Cisco Unified Communications Manager (CallManager) (CUCM), Cisco Unified Communications (UC), or Cisco Unified Contact Center Express (UCCX) server. If a CUCM, UC, or UCCX server experiences an unexpected shutdown, the file system consistency cannot be guaranteed. Files may be removed unexpectedly, ownership of file permissions may be changed, or the contents of files might be corrupted.

In order to temporarily recover the system, run the system recovery disc released for the corresponding software version.

Verify Improper Shutdown

Review the system-history.log in order to determine if a system has been shut down improperly.

Note: The system-history.log was added as part of Cisco Bug ID CSCsl94283, "CCM 5.X should track all install/upgrade with History.log like 4.X." Versions in earlier releases were not tracked. The History.log was enhanced in order to track improper shutdowns with Cisco bug ID CSCtr88859 in order to add alarms and alerts for unexpected reboots that are integrated in CUCM Versions 9.1(1) and later.

  1. Download the install/upgrade logs from the Cisco Unified Real-Time Monitoring Tool (RTMT), and gather the system-history.log.
    Enter the file view install system-history.log command on the command-line interface (CLI).

  2. Examine each instance of root: Boot, and confirm that each instance is preceded by one of these lines:

    root: Restart
    root: Shutdown
    root: Install
    root: Upgrade
  3. If a boot instance is not proceeded by a Restart, Shutdown, Install, or Upgrade, there was likely an unclean shutdown.

This is an example of an unclean shutdown:

08/14/2012 13:36:09 | root: Boot Start
08/14/2012 17:28:25 | root: Boot Start

In this example, the server must be rebuilt in order to ensure file system consistency. See these Cisco Bug IDs for further details:

  • Cisco Bug ID CSCth60800, "Recovery Disc warning to rebuild system after file system repair"
  • Cisco Bug ID CSCth53322, "Document the need for system rebuild after file system repair"

Note: If the server is running on VMware on a version without the fix for Cisco Bug ID CSCtw73590, "VSphere initiated shutdown or restart not logged to system-history.log" and if the server is shut down through VSphere when a guest shutdown is initiated, that entry may not be included in the system-history.log.

Updated: Nov 05, 2013
Document ID: 116717