Cisco Bug: CSCtb83913 - SRM may finish before database repair is finished
Feb 22, 2014
- Cisco Unity Connection
- Cisco Unity Connection Version 7.0
Known Affected Releases
Symptom: In some cases, where a system is under load during SBR, SRM may time out after an hour and declare a system primary and the other secondary, while cdr is still running. Example, from a system running a significant load: 09/04/2009 07:24:28.389 |10331,,,SRM,5,<evt>  Lost communication with the remote server cuc1b.vnt.cisco.com in the cluster. The remote server may be down.| 09/04/2009 09:51:42.959 |10332,,,SRM,5,<listener> Received connection from /10.1.1.2:46594| 09/04/2009 09:51:45.201 |10331,,,SRM,5,<evt>  Split-brain resolution procedure has been initiated.| 09/04/2009 10:52:30.727 |10331,,,SRM,5,<evt>  Split-brain resolution procedure run successfully.| 09/04/2009 10:53:24.820 |10331,,,SRM,5,<evt> PUB_PRIMARY - Role_activate Done!! - PUBLISHER_PRIMARY [ 51secs. ]| However, CDR didn't finish up until much later: 2009-09-04 12:26:00 + log 'Repair successful.' Conditions: Unity Connection in a clustered environment where SBR has been triggered under significant load. This can happen if there is an extended outage between the publisher and subscriber.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases