Unity connection: 188.8.131.5200-10
Unified Messaging with Office 365 / auto-discovery
I am getting following core dumps and voice-mail to e-mail stopped.
At Wed Aug 28 17:45:46 EDT 2013 on node 10.10.30.254, the following CoreDumpFileFound events generated:
TotalCoresFound : 1
CoreDetails : The following lists up to 6 cores dumped by corresponding applications.
Core1 : Connection Mailbox Sync (core.1269.6.CuMbxSync.1377726312)
AppID : Cisco Log Partition Monitoring Tool
NodeID : cmbe8
TimeStamp : Wed Aug 28 17:45:16 EDT 2013 At Wed Aug 28 17:45:46 EDT 2013 on node 10.10.30.254, the following CoreDumpFileFound events generated: TotalCoresFound : 1CoreDetails : The following lists up to 6 cores dumped by corresponding applications.Core1 : Connection Mailbox Sync (core.1269.6.CuMbxSync.1377726312)AppID : Cisco Log Partition Monitoring ToolClusterID : NodeID : cmbe8TimeStamp : Wed Aug 28 17:45:16 EDT 2013
I did a bug search and found some relevant ones but the conditions didn't match exactly except for the following:
CSCtz31625 - CuMbxSync Cores while logging Autodiscovery diagnostics
Workaround:Disable CsExMbxLocator INFO level Micro traces (Trace Number: 12)
I have already confirmed that the above trace is not enabled but I am still getting core dumps.
Upon analysing the Core dump file, I see the following error but I am unable to find anything relevant on this error:
Core was generated by `/opt/cisco/connection/bin/CuMbxSync'.Program terminated with signal 11, Segmentation fault.
I have double checked, we are not using special characters in User names which may have been another possible cause for the core dump.
I'll appreciate any help on this. I am attaching the Core dump file if someone would like to have a look.
You are hitting this defect
CSCud56304-MBXSync service crashes & core generated due to null entry in UC cache
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: