3512788 - Dpserver's replication status become UNKNOWN

You notice that the dpserver's replication status is UNKNOWN, and when you check the dpserver trace, you find the information similar as below.

[81369]{-1}[-1/-1] 2024-08-06 01:47:54.008729 i sr_dataaccess    DisasterRecoveryPrimaryImpl.cpp(01507) : Start listen to specific interface 127.0.0.1 port:40446
[81369]{-1}[-1/-1] 2024-08-06 01:47:54.010263 e Stream           NetworkAddress.cpp(01064) : socket info for 127.0.0.1/40446_tcp: [ 453: 0100007F:9DFE 0100007F:76CA 01 00000000:00000000 02:00000AD2 00000000 100000113        0 19065837 2 0000000000000000 20 4 0 10 -1              ]
[81369]{-1}[-1/-1] 2024-08-06 01:47:54.036010 e Stream           NetworkChannel.cpp(00609) : [a46fb34af2e967e3,127.0.0.1:40446,-,REP,0] Cannot bind to a local address: tcp port 40446 on 127.0.0.1 => socket[19065837], user ""q2hadm:100000113", port blocked due to state TCP_ESTABLISHED
[81369]{-1}[-1/-1] 2024-08-06 01:47:54.036118 e sr_dataaccess    DisasterRecoveryPrimaryImpl.cpp(01538) : Listener cannot be started, because port 40446 is already in use!
[81369]{-1}[-1/-1] 2024-08-06 01:47:54.036120 e sr_dataaccess    DisasterRecoveryPrimaryImpl.cpp(01539) : A system replication primary uses replication ports in the range of instance number(s) from 04 to 04

• SAP HANA PLATFORM 2.0

dpserver, port, ip_local_reserved_ports, ip_local_port_range, replication status, UNKNOWN , KBA , HAN-DB-HA , SAP HANA High Availability (System Replication, DR, etc.) , Problem