Hi Rich,
I can tell the core is an IntentionalAbort , Core dumps that include the "IntentionalAbort" statement indicate a system resource issue that was responsible for the service fault. check the link below which talks about troubleshooting this type of issue in detail.
https://supportforums.cisco.com/document/56631/troubleshooting-core-dumps#Performing_Core_Analysis
On surface, you can make sure below is good.
- Server is build with recommended OVA specification.
- NO VM snapshots.
if the above is good i would recommend collect the below logs and open TAC case.
. 1 Collect all CallManager SDI and SDL traces in detail from all the nodes. Make sure they include the time window where the core dump got generated. Even though the core dump belongs to a different service like CTI Manager we need the CallManager traces.
- If the core dump belongs to another service, like CTI Manager collect the traces for the offending service.
- Collect the application and System logs from the syslog viewer with RTMT
- Collect RIS Data collector performance logs.
- Collect ProgLogs, to see if there's any file available. Proglogs may not have been written, however we need to confirm the presence of proglogs during the time of the failure.
- Perform a utils core analyze and gather all the output
- Download the core dump with RTMT to the customer computer. Zip the core dump, and attach it to the case notes via the web page since it will be likely a large file.
- Collect server info
- Show version active
- Show version inactive
- Show status
- Show hardware
From internal BUG scrub i see some related BUGs, but looking at logs would be better way to go.
HTH
JB
