TIE Slave replication taking a long time (?)

[SPKR1126]

Hello, I've been trying to get a new TIE server running as a secondary with the intention of promoting it to primary and removing the other one.

I've installed the new TIE server from the OVA and enabled DXL (and MAR), it will also replace another DXL server eventually but for now it shows up fine bridged.

Had some early issues with version mismatch that I finally got solved and am left the server as a secondary in the topology but highlighted red with the DXL error "Unable to reach tie server via DXL".  on the console I get this from replication-monitorying.sh -monitor:

*****************************************************
TIE Service Database Replication status monitor
*****************************************************
Current Time: Sun Feb 27 21:15:06 UTC 2022

This is a Secondary server

**** Secondary server configuration ****
/data/tieserver_pg/recovery.conf

Standby mode (Secondary mode): 'on'
Primary connection user: rep
Primary connection host: x.x.x.x
Primary connection port: XXXX
Primary connection ssl mode: verify-full
Primary connection ssl compression: 1

**** Replication Status ****
Is Replication in progress: true
Is Replication paused: false
Last WAL receive location: 34B/21F3C4D8
Current WAL location in Primary: 34B/21F3C4D8
Gap between Primary and Received in Secondary: 0 bytes
Last WAL replay location: 34B/21F3C4D8
Gap between Primary and Replayed in Secondary: 0 bytes
Last WAL replay time: Sun Feb 27 21:14:38 UTC 2022
Replication lag: 29 seconds

I see the "Last WAL rec/replay location" do go up so it is doing something apparently but this has been going since about 2/25 around 5PM EDT, about a day and a half.  Should I just wait?

Thank you 

[bbarnes · Accepted solution]

Hello SPKR1126, 

I do not believe your issue is based on replication and there may be a different reason the server is not showing online. We likely need to review logs from the device to identify the issue. I would recommend working with support on this and collecting a MER for troubleshooting the issue.

https://kc.mcafee.com/corporate/index?page=content&id=KB82850

Thanks

Brian

[SPKR1126]

Thanks! Actually I've found that the DXL client is not connecting which is likely the issue. I've started another post for that.