Cisco Bug: CSCuj36053 - After RepDB failover, dnscStart failed to start EC processes properly
Feb 27, 2015
- Headend System Releases
Known Affected Releases
Symptom: During a fail over from RepDB primary to secondary dncs processes failed to show 'in service' even though processes were actually running. Conditions: Fail over from primary server to secondary server. Start the processes on the secondary server using dncsStart. Note status in UI and status in CLI dncsControl -list do not match.
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