Citrix Application Delivery management (ADM / NMAS) - Database sync Issue

Issue Occurred : The issue occurred in a new deployment , even being it a fresh deployment, this issue was occurring. Where as both the ADM were in the same VLAN and same network.

It shows - Database streaming channel is broken between HA nodes.

To solve this:

1. Please run this command on Secondary Box (Replace with original IP addresses in the command):
• nohup sh /mps/scripts/pgsql/join_streaming_replication.sh SecondaryIP PrimaryIP nsroot > /var/mps/log/join_streaming_replication_console.log 2>&1 &
2. Monitor the output of this command in /var/mps/log:
• ‘tail -f join_streaming_replication_console.log'

3 . Wait for a few minutes / hour depending on DB Size and confirm if the HA channel is UP by running the command

• ‘ps -ax | grep -i wal’

4. You should see this line to confirm if the channel is UP

• ?? Ss 0:14.14 postgres: wal receiver process streaming

bash-3.2#

bash-3.2# nohup sh /mps/scripts/pgsql/join_streaming_replication.sh 172.16.2.40                                                                                                              172.16.2.39 nsroot > /var/mps/log/join_streaming_replication_console.log 2>&1 &

[1] 4952

bash-3.2#

bash-3.2# cd /var/mps/log

bash-3.2# tail -f join_streaming_replication_console.log

Stopping appd

Stopping nsulfd

Reinitializing monit daemon

Reinitializing monit daemon

monit daemon with pid [629] killed

Stopped nsulfd

Stopped appd

waiting for server to shut down.... done

server stopped

cleaning up postgres data...

physical replication

---------------------

backup data from master node...this might take some time..

sleeping 20 seconds...

pg_basebackup: Done

set kernel params for tcp keepalive parameters

net.inet.tcp.keepidle: 7200000 -> 5000

net.inet.tcp.keepintvl: 75000 -> 1000

server starting

shutdown: [pid 5319]

Shutdown NOW!

*** FINAL System shutdown message from nsroot@ctadm02 ***

System going down IMMEDIATELY

Shutdown NOW!

System shutdown time has arrived

Message from syslogd@ctadm02 at Jul 30 13:18:41 ...

<auth.emerg> ctadm02 init: Rebooting via init mechanism