[stork-users] HA-status unavailable

[Andrey Kostin]

Hi Stork-users,

I have two pairs of Kea-dhcp servers in ha-mode. In one pair the standby 
server shows HA-status of the primary as unavailable (for both dhcp4 and 
dhcp6).
Here is how it's seen in stork web interface:
High Availability

Local server
Status time:	2024-02-23 11:52:04
Status checked:	1 minutes ago
Role:	standby
Control status:	online
Heartbeat status:	ok
State:	hot-standby
Scopes served:	none (standby server)
Last in partner-down:	never
Unacked clients:	n/a
Connecting clients:	n/a
Analyzed packets:	n/a

Remote server Kea at X.X.X.251
Status time:	2024-02-23 11:52:03
Status checked:	1 minutes ago
Role:	primary
Control status:	offline	         <<<< Here is the problem
Heartbeat status:	ok
State:	unavailable	         <<<< Here is the problem
Scopes served:	none
Last in partner-down:	never
Unacked clients:	n/a
Connecting clients:	n/a
Analyzed packets:	n/a

 From primary server's perspective everything is ok. In another pair of 
dhcp servers both looks mutually ok.
In direct API call to the standby server's Kea control agent the status 
looks ok:
API call is successful
Result code: 0
{
     "high-availability": [
         {
             "ha-mode": "hot-standby",
             "ha-servers": {
                 "local": {
                     "role": "standby",
                     "scopes": [],
                     "state": "hot-standby"
                 },
                 "remote": {
                     "age": 0,
                     "analyzed-packets": 0,
                     "communication-interrupted": false,
                     "connecting-clients": 0,
                     "in-touch": true,
                     "last-scopes": [
                         "keadhcp01"
                     ],
                     "last-state": "hot-standby",
                     "role": "primary",
                     "unacked-clients": 0,
                     "unacked-clients-left": 0
                 }
             }
         }
     ],
     "multi-threading-enabled": true,
     "packet-queue-size": 28,
     "packet-queue-statistics": [
         1.0,
         1.0,
         1.0
     ],
     "pid": 20269,
     "reload": 12092253,
     "thread-pool-size": 4,
     "uptime": 12426307
}

I checked the logs but couldn't identify the problem. What connection 
should I look for? Is it stork server, stork agent or control agent that 
establishes this connection and performs the check?

Kind regards,
Andrey