Cisco Cisco MeetingTime Quick Setup Guide

Core files are useful for determining what state a program was in before it terminated. A utility called 
checkcores reports new cores found, raises an alarm (EX_CORESPACE), and compresses and archives 
the cores to the /mpx-record/cores directory.. 

Unless the cause of the core file is already known, all core files should be escalated to Cisco TAC. 

During startup, if new cores are found, the following message is echoed to the session after “Starting 
MeetingPlace application”: 

   NOTE: new core files found in /var

   See /mpx-record/cores/checkcores.log for more information

                                                          [  OK  ]

If no cores are found, the utility does not log anything. If run interactively, the utility either echoes the 
two lines shown above if cores are found, or echoes “no cores found”. 

A maximum of 10 core files are saved to this location. The approximate total max space requred for 
compressed core images is 200MB. If there is insufficient space in the /mpx-record directory, an alarm 
is raised: 

   346) MAJ 10006c    4 Mar 22 05:58  Mar 22 06:00   0 SW MODULE=0

       insufficient space in /mpx-record filesystem to manage cores

A logfile, /mpx-record/cores/checkcores.log, is maintained in the /mpx-record/cores directory. If this 
logfile grows beyond 100K, it is backed up to checkcores.log.old and a new log is started (only one 
backup is maintained). 

Cores are archived in the form: 

yymmddhhmmss-path1-path2-path3-core.pid.datetime.gz 

yymmddhhmmss is the current date/timestamp 

path1-path2-path3 is the full path translated to hyphen-separated names; for example, 
/var/mp/nmpagent is translated to var-mp-nmpagent 

pid is the process id of the aborted process 

datetime is the date/timestamp of the core file creation as displayed by ls -l, but in a compressed 
form (for example, Mar2-14:52, Jan22-09:15). 

Alarm and Exception Code Reference for Cisco Unified MeetingPlace at