CUPS Services not starting on one of the Nodes

symptom: Services on one of the nodes (Pub or Sub) start and then after 30-60 sec stop again

ssh onto the effected node

admin:utils dbreplication status
-------------------- utils dbreplication status --------------------
Replication status check is now running in background.
Use command 'utils dbreplication runtimestate' to check its progress
The final output will be in file cm/trace/dbl/sdi/ReplicationStatus.2013_02_06_13_02_08.out
Please use "file view activelog cm/trace/dbl/sdi/ReplicationStatus.2013_02_06_13_02_08.out " command to see the output

admin:file view activelog cm/trace/dbl/sdi/ReplicationStatus.2013_02_06_13_02_08.out
g_wokup01_ccm8_6_1_10000_34 2 Active Local 0
g_wokup02_ccm8_6_1_10000_34 3 Active Connected 306 Jan 30 11:10:47

end of the file reached
options: q=quit, n=next, p=prev, b=begin, e=end (lines 1 - 4 of 4)

!Under QUEUE there should be 0. The fact the number is 306 means that there are 306 transactions that have not been replicated to the other database.
!Also check under “System > Cluster Topology” there should be a red X icon next to the server

!display db replication monitoring
admin:set replwatcher monitor disable
!services should start coming back up. Check with
admin:utils service list page

Go through the same commands again as above to check database
admin:utils dbreplication status
admin:file view activelog cm/trace/dbl/sdi/ReplicationStatus.XXXXXXXXXXXX.out

!Under QUEUE this time all should be 0
!ReEnable replwatcher
set replwatcher monitor enable

Go to CUPS Admin GUI
System > Cluster Topology
Because we have Active Active setup click on “Edit” under Subcluster1. On the server that was having the issue click on the “Fallback” button. This will balance the users between the server


Note users will be logged out of the CUPC when this is done. If its not Done they will be logged out within the next 30 minutes anyway

Tags: ,

About Alexis Katsavras

Working as Freelance Cisco Unified Communications Consultant in the UK.