[Kea-users] Failed to Sync lease updates from primary to backup in Hot-standby mode in V1.5.0

[Marcin Siodelski]

Hello,

Thank you for your email. It would be useful to see the log from the
primary server to see why it went to the "terminated" state. The standby
server apparently transitioned to the "terminated" state seeing that the
partner is in that state. Note that the server which transitioned to the
"terminated" state (e.g. as a result of too high clock skew) will not
transition out of this state automatically, even if the clocks get
synchronized. It must be stopped and started again. Perhaps, the primary
server wasn't restarted after syncing the clocks?

Marcin Siodelski
Sr. Software Engineer
ISC

On 02/04/2020 10:36, luckydog xf wrote:
>   Hi, list,
> 
>   I'm using Kea V1.5.0 and running two dhcp servers in Hot-standby mode.
> My lease database is Memfile. I setup NTP for both servers. 
> 
>    Here is part of my configuration, 
> ===============
>               "high-availability": [ {
>                     "this-server-name": "server2",
>                     "mode": "hot-standby",
>                     "heartbeat-delay": 10000,
>                     "max-response-delay": 10000,
>                     "max-ack-delay": 5000,
>                     "max-unacked-clients": 5,
> 
>                     "send-lease-updates": true,
>                     "sync-leases": true,
>                     "sync-page-limit": 10000,
>                     "sync-timeout": 30000,
> 
>                     "peers": [
>                         {
>                             "name": "server1",
>                             "url": "http://172.16.232.18:8080/",
>                             "role": "primary",
>                             "auto-failover": true
>                         },
>                         {
>                             "name": "server2",
>                             "url": "http://172.16.232.20:8080/",
>                             "role": "standby",
>                             "auto-failover": true
>                         }
> =============
> 
> Yet  on standby server ,it says that,
> ===============
> 2020-04-02 11:08:19.269 INFO  [kea-dhcp4.ha-hooks/11468]
> HA_LOCAL_DHCP_DISABLE local DHCP service is disabled while the server2
> is in the WAITING state
> 2020-04-02 11:08:19.269 INFO  [kea-dhcp4.ha-hooks/11468]
> HA_SERVICE_STARTED started high availability service in hot-standby mode
> as standby server
> 2020-04-02 11:08:19.269 INFO  [kea-dhcp4.dhcp4/11468] DHCP4_STARTED Kea
> DHCPv4 server version 1.5.0 started
> 2020-04-02 11:08:31.283 INFO  [kea-dhcp4.ha-hooks/11468]
> HA_STATE_TRANSITION server transitions from WAITING to TERMINATED state,
> partner state is TERMINATED
> 2020-04-02 11:08:31.283 INFO  [kea-dhcp4.ha-hooks/11468]
> HA_LEASE_UPDATES_DISABLED lease updates will not be sent to the partner
> while in TERMINATED state
> 2020-04-02 11:08:31.283 INFO  [kea-dhcp4.ha-hooks/11468]
> HA_LOCAL_DHCP_ENABLE local DHCP service is enabled while the server2 is
> in the TERMINATED state
> 2020-04-02 11:08:31.283 ERROR [kea-dhcp4.ha-hooks/11468] HA_TERMINATED
> HA service terminated because of the unacceptable clock skew; fix the
> problem and restart!
> 
> ============
> 
> I'm sure two severs get correct date time. So what's the reason ?
> 
> Is it related
> to https://gitlab.isc.org/isc-projects/kea/-/merge_requests/414 ?
> 
> Thanks and take care.
> 
> -hongquan
> 
> 
> _______________________________________________
> Kea-users mailing list
> Kea-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/kea-users
>