Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
988
Views
0
Helpful
1
Replies

CUC 8.5.1 Both Servers Have Primary Server Status

ionicpolarity
Level 1
Level 1

‎07-10-2013 06:53 AM - edited ‎03-19-2019 06:58 AM

Hi everyone, I am having an recurring issue of "Communication is not functioning correctly between the servers in the Cisco  Unity Connection cluster"

This occured while trying to configure "Smart host" to relay voicemails to google apps, which so far has been completely unsuccessfull. Both servers were fine and after rebooting services several times trying to configure the "SMTP Config" server/smart host settings all of a sudden I got this error. the rtmt logs show this:

PRIMARY:

05:25:28.549 HDR|07/10/2013 ,Significant

05:25:28.549 |10870,,,SRM,3,<sess-1267> 9 : java.net.SocketInputStream.socketRead0(Native Method)

05:25:43.557 |22537,,,SRM,5,<listener> Received connection from /10.250.4.28:40567

05:25:44.271 |11027,,,SRM,5,<sess-1268> [rcv] Type: Register ID: d2c37c4a-872f-4f6b-a715-2ebc7e0225bd HavePrimaryToken: true NeedSbr: false Version: 8.5.1.14900-5 Instance: f524bcab-996b-48ca-bca6-1e43c4abf528

05:25:44.681 |11027,,,SRM,3,<sess-1268> Rejecting registration due to different instance IDs. Remote: f524bcab-996b-48ca-bca6-1e43c4abf528 Local: ba0d9d73-9cd4-461e-bc14-3c3ab72f6f7a

05:25:44.682 |11027,,,SRM,3,<sess-1268> Session error: java.net.SocketException: Socket closed

05:25:44.682 |11027,,,SRM,3,<sess-1268> 0 : java.lang.Thread.run(Thread.java:662)

05:25:44.682 |11027,,,SRM,3,<sess-1268> 1 : com.cisco.unity.srm.rsrm.Session.run(Session.java:210)

05:25:44.682 |11027,,,SRM,3,<sess-1268> 2 : java.io.ObjectInputStream.readObject(ObjectInputStream.java:350)

05:25:44.682 |11027,,,SRM,3,<sess-1268> 3 : java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1296)

05:25:44.682 |11027,,,SRM,3,<sess-1268> 4 : java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2551)

05:25:44.682 |11027,,,SRM,3,<sess-1268> 5 : java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2541)

05:25:44.682 |11027,,,SRM,3,<sess-1268> 6 : java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2248)

05:25:44.682 |11027,,,SRM,3,<sess-1268> 7 : java.net.SocketInputStream.read(SocketInputStream.java:182)

05:25:44.682 |11027,,,SRM,3,<sess-1268> 8 : java.net.SocketInputStream.read(SocketInputStream.java:129)

05:25:44.682 |11027,,,SRM,3,<sess-1268> 9 : java.net.SocketInputStream.socketRead0(Native Method)

SUBSCRIBER:

06:01:07.245 HDR|07/10/2013 ,Significant

06:01:07.245 |15936,,,SRM,3,<session> 9 : java.net.SocketInputStream.read(SocketInputStream.java:168)

06:01:22.254 |15936,,,SRM,5,<session> Connection to lx099um1.dps/10.250.4.26:22001

06:01:22.792 |15936,,,SRM,5,<session> ER state: 0

06:01:22.792 |15936,,,SRM,5,<session> [snd] Type: Register ID: d2c37c4a-872f-4f6b-a715-2ebc7e0225bd HavePrimaryToken: true NeedSbr: false Version: 8.5.1.14900-5 Instance: f524bcab-996b-48ca-bca6-1e43c4abf528

06:01:23.293 |15936,,,SRM,3,<session> Session error: java.net.SocketException: Connection reset

06:01:23.293 |15936,,,SRM,3,<session> 0 : java.lang.Thread.run(Thread.java:662)

06:01:23.293 |15936,,,SRM,3,<session> 1 : com.cisco.unity.srm.rsrm.Client.run(Client.java:81)

06:01:23.293 |15936,,,SRM,3,<session> 2 : com.cisco.unity.srm.rsrm.Session.run(Session.java:210)

06:01:23.293 |15936,,,SRM,3,<session> 3 : java.io.ObjectInputStream.readObject(ObjectInputStream.java:350)

06:01:23.293 |15936,,,SRM,3,<session> 4 : java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1296)

06:01:23.293 |15936,,,SRM,3,<session> 5 : java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2551)

06:01:23.293 |15936,,,SRM,3,<session> 6 : java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2541)

06:01:23.293 |15936,,,SRM,3,<session> 7 : java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2248)

06:01:23.293 |15936,,,SRM,3,<session> 8 : java.net.SocketInputStream.read(SocketInputStream.java:182)

06:01:23.293 |15936,,,SRM,3,<session> 9 : java.net.SocketInputStream.read(SocketInputStream.java:168)

06:01:38.301 |15936,,,SRM,5,<session> Connection to lx099um1.dps/10.250.4.26:22001

06:01:39.043 |15936,,,SRM,5,<session> ER state: 0

06:01:39.044 |15936,,,SRM,5,<session> [snd] Type: Register ID: d2c37c4a-872f-4f6b-a715-2ebc7e0225bd HavePrimaryToken: true NeedSbr: false Version: 8.5.1.14900-5 Instance: f524bcab-996b-48ca-bca6-1e43c4abf528

Labels:
0 Helpful
1 Reply 1

ionicpolarity
Level 1
Level 1

‎07-25-2013 09:10 AM

Found out that this occurred from rebooting the servers to fast. Fix is to reboot the pub first and wait for it to completely boot up. Then reboot the sub after.

I still had to fix the database using the console commands:

utils dbreplication clusterreset

You can use this command to debug database replication. However, you should only use it if you have already tried utils dbreplication reset all, and it failed to restart replication on the cluster. This command will tear down and rebuild replication for the entire cluster. After using this command, you must restart each subscriber server. After all subscriber servers have been restarted, you must go to the publisher server and issue the CLI command utils dbreplication reset all.

Command Syntax

utils dbreplication clusterreset

Usage Guidelines

Before you run this command, run the command utils dbreplication stop first on all subscribers servers and then on the publisher server.

Requirements

Command privilege level: 0

Allowed during upgrade: No

utils dbreplication dropadmindb

This command drops the Informix syscdr database on any server in the cluster.

Command Syntax

utils dbreplication dropadmindb

Usage Guidelines

You should run this command only if database replication reset or cluster reset fails and replication cannot be restarted.

Requirements

Command privilege level: 0

Allowed during upgrade: No

utils dbreplication forcedatasyncsub

This command forces a subscriber server to have its data restored from data on the publisher server.

Use this command only after you have run the utils dbreplication repair command several times, but the utils dbreplication status command still shows non-dynamic tables that are not in sync

Just have to follow the instructions when prompted.

0 Helpful
Getting Started

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:

Customers Also Viewed These Support Documents