PDF(5.9 KB) View with Adobe Reader on a variety of devices
ePub(77.6 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(72.4 KB) View on Kindle device or Kindle app on multiple devices
Updated:May 13, 2016
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes how to identify an unexpected shutdown of a Cisco Unified Communications Manager (CallManager) (CUCM), Cisco Unity Connection (UC), Cisco Unified Contact Center Express (UCCX), Cisco Emergency Responder (CER), Cisco Prime, or any application that runs on top of Cisco's customized Voice Operating System (VOS). If the server experiences an unexpected shutdown, the file system consistency cannot be guaranteed. Files might be removed unexpectedly, ownership of file permissions might 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.
Download the install/upgrade logs from the Cisco Unified Real-Time Monitoring Tool (RTMT), and gather the system-history.log. or Enter the file view install system-history.log command on the command-line interface (CLI).
Examine each instance of root: Boot, and confirm that each instance is preceded by one of these lines:
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"
Cisco bug ID CSCuy94644, "Cisco Emergency Responder corruption after unexpected shutdown"
Note: If the server runs 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 might not be included in the system-history.log.