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.
- 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).
- Examine each instance of root: Boot, and confirm that each instance is preceded by one of these lines:
- 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 18.104.22.16800-37 Start
08/14/2012 17:28:25 | root: Boot 22.214.171.12400-37 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"