Thank you, Darren, I wonder how it worked in 2.4.1 then, but fair point - I will need to modify the IP addresses to IPv6 on the DHCPv6 side.
Regards Marek On Thu, May 30, 2024 at 11:40 AM Darren Ankney <darren.ank...@gmail.com> wrote: > Hi Marek, > > According to your attached keav4 and keav6 files, your HA > configuration for both DHCPv4 and DHCPv6 is exactly the same as > pertains to "url". Both are trying to listen on > http://192.168.150.221:8000/ and http://192.168.150.222:8000/ > respectively. You can either use a different port for DHCPv6 or use > the IPv6 address. > > Thank you, > Darren Ankney > > On Wed, May 29, 2024 at 5:35 PM <mxhajducze...@gmail.com> wrote: > > > > So I ventured to the upgrade from 2.4.1 to 2.6.0 to see if that helps my > integration problems with Stork in any way. Agent and DHCPv6 restarted fine > after reboot. DHCPv4 for some reason is complaining about address being > already in use. The system worked just fine under 2.4.1 without any > complaints about address binding being a problem. > > > > > > > > May 29 21:18:09 dhcp-kea-node2 kea-dhcp4[2755]: 2024-05-29 21:18:09.388 > DEBUG [kea-dhcp4.dhcpsrv/2755.140174953331136] > DHCPSRV_MEMFILE_BEGIN_EXTRACT_EXTENDED_INFO4 extract extended info with fix > sanity check level > > > > May 29 21:18:09 dhcp-kea-node2 kea-dhcp4[2755]: 2024-05-29 21:18:09.388 > INFO [kea-dhcp4.dhcpsrv/2755.140174953331136] > DHCPSRV_MEMFILE_EXTRACT_EXTENDED_INFO4 extracting extended info saw 0 > leases, extended info sanity checks modified 0 / update> > > > > May 29 21:18:09 dhcp-kea-node2 kea-dhcp4[2755]: 2024-05-29 21:18:09.388 > INFO [kea-dhcp4.dhcpsrv/2755.140174953331136] DHCPSRV_MEMFILE_LFC_SETUP > setting up the Lease File Cleanup interval to 3600 sec > > > > May 29 21:18:09 dhcp-kea-node2 kea-dhcp4[2755]: 2024-05-29 21:18:09.388 > DEBUG [kea-dhcp4.dhcpsrv/2755.140174953331136] > DHCPSRV_TIMERMGR_REGISTER_TIMER registering timer: memfile-lfc, using > interval: 3600000 ms > > > > May 29 21:18:09 dhcp-kea-node2 kea-dhcp4[2755]: 2024-05-29 21:18:09.388 > DEBUG [kea-dhcp4.dhcpsrv/2755.140174953331136] DHCPSRV_TIMERMGR_START_TIMER > starting timer: memfile-lfc > > > > May 29 21:18:09 dhcp-kea-node2 kea-dhcp4[2755]: 2024-05-29 21:18:09.404 > DEBUG [kea-dhcp4.dhcpsrv/2755.140174953331136] > DHCPSRV_TIMERMGR_REGISTER_TIMER registering timer: reclaim-expired-leases, > using interval: 10000 ms > > > > May 29 21:18:09 dhcp-kea-node2 kea-dhcp4[2755]: 2024-05-29 21:18:09.404 > DEBUG [kea-dhcp4.dhcpsrv/2755.140174953331136] DHCPSRV_TIMERMGR_START_TIMER > starting timer: reclaim-expired-leases > > > > May 29 21:18:09 dhcp-kea-node2 kea-dhcp4[2755]: 2024-05-29 21:18:09.404 > DEBUG [kea-dhcp4.dhcpsrv/2755.140174953331136] > DHCPSRV_TIMERMGR_REGISTER_TIMER registering timer: flush-reclaimed-leases, > using interval: 25000 ms > > > > May 29 21:18:09 dhcp-kea-node2 kea-dhcp4[2755]: 2024-05-29 21:18:09.404 > DEBUG [kea-dhcp4.dhcpsrv/2755.140174953331136] DHCPSRV_TIMERMGR_START_TIMER > starting timer: flush-reclaimed-leases > > > > May 29 21:18:09 dhcp-kea-node2 kea-dhcp4[2755]: 2024-05-29 21:18:09.404 > DEBUG [kea-dhcp4.callouts/2755.140174953331136] HOOKS_CALLOUTS_BEGIN begin > all callouts for hook dhcp4_srv_configured > > > > May 29 21:18:09 dhcp-kea-node2 kea-dhcp4[2755]: 2024-05-29 21:18:09.404 > INFO [kea-dhcp4.ha-hooks/2755.140174953331136] HA_LOCAL_DHCP_DISABLE local > DHCP service is disabled while the dhcp-kea-node2 is in the WAITING state > > > > May 29 21:18:09 dhcp-kea-node2 kea-dhcp4[2755]: 2024-05-29 21:18:09.404 > DEBUG [kea-dhcp4.http/2755.140174953331136] HTTP_CLIENT_MT_STARTED > HttpClient has been started in multi-threaded mode running 4 threads > > > > May 29 21:18:09 dhcp-kea-node2 kea-dhcp4[2755]: 2024-05-29 21:18:09.404 > INFO [kea-dhcp4.ha-hooks/2755.140174953331136] HA_SERVICE_STARTED > dhcp-kea-node2: started high availability service in hot-standby mode as > standby server > > > > May 29 21:18:09 dhcp-kea-node2 kea-dhcp4[2755]: 2024-05-29 21:18:09.404 > DEBUG [kea-dhcp4.callouts/2755.140174953331136] HOOKS_CALLOUT_CALLED hooks > library with index 3 has called a callout on hook dhcp4_srv_configured that > has address 0x7f7d044> > > > > May 29 21:18:09 dhcp-kea-node2 kea-dhcp4[2755]: 2024-05-29 21:18:09.404 > DEBUG [kea-dhcp4.callouts/2755.140174953331136] HOOKS_CALLOUTS_COMPLETE > completed callouts for hook dhcp4_srv_configured (total callouts duration: > 0.213 ms) > > > > May 29 21:18:09 dhcp-kea-node2 kea-dhcp4[2755]: 2024-05-29 21:18:09.404 > INFO [kea-dhcp4.dhcpsrv/2755.140174953331136] DHCPSRV_CFGMGR_USE_ALLOCATOR > using the iterative allocator for V4 leases in subnet 10.10.1.0/24 > > > > May 29 21:18:09 dhcp-kea-node2 kea-dhcp4[2755]: 2024-05-29 21:18:09.405 > DEBUG [kea-dhcp4.callouts/2755.140174953331136] HOOKS_CALLOUTS_BEGIN begin > all callouts for hook command_processed > > > > May 29 21:18:09 dhcp-kea-node2 kea-dhcp4[2755]: 2024-05-29 21:18:09.405 > DEBUG [kea-dhcp4.callouts/2755.140174953331136] HOOKS_CALLOUT_CALLED hooks > library with index 3 has called a callout on hook command_processed that > has address 0x7f7d044527> > > > > May 29 21:18:09 dhcp-kea-node2 kea-dhcp4[2755]: 2024-05-29 21:18:09.405 > DEBUG [kea-dhcp4.callouts/2755.140174953331136] HOOKS_CALLOUTS_COMPLETE > completed callouts for hook command_processed (total callouts duration: > 0.032 ms) > > > > May 29 21:18:09 dhcp-kea-node2 kea-dhcp4[2755]: 2024-05-29 21:18:09.405 > ERROR [kea-dhcp4.dhcp4/2755.140174953331136] DHCP4_CONFIG_LOAD_FAIL > configuration error using file: /etc/kea/kea-dhcp4.conf, reason: Error > initializing hooks: CmdHttpListen> > > > > May 29 21:18:09 dhcp-kea-node2 kea-dhcp4[2755]: 2024-05-29 21:18:09.405 > ERROR [kea-dhcp4.dhcp4/2755.140174953331136] DHCP4_INIT_FAIL failed to > initialize Kea server: configuration error using file > '/etc/kea/kea-dhcp4.conf': Error initializing h> > > > > May 29 21:18:09 dhcp-kea-node2 kea-dhcp4[2755]: 2024-05-29 21:18:09.424 > INFO [kea-dhcp4.ha-hooks/2755.140174953331136] HA_DEINIT_OK unloading High > Availability hooks library successful > > > > May 29 21:18:09 dhcp-kea-node2 kea-dhcp4[2755]: 2024-05-29 21:18:09.425 > INFO [kea-dhcp4.stat-cmds-hooks/2755.140174953331136] STAT_CMDS_DEINIT_OK > unloading Stat Commands hooks library successful > > > > May 29 21:18:09 dhcp-kea-node2 kea-dhcp4[2755]: 2024-05-29 21:18:09.425 > INFO [kea-dhcp4.lease-cmds-hooks/2755.140174953331136] > LEASE_CMDS_DEINIT_OK unloading Lease Commands hooks library successful > > > > May 29 21:18:09 dhcp-kea-node2 kea-dhcp4[2755]: 2024-05-29 21:18:09.425 > INFO [kea-dhcp4.hooks/2755.140174953331136] HOOKS_LIBRARY_CLOSED hooks > library /usr/lib/x86_64-linux-gnu/kea/hooks/libdhcp_ha.so successfully > closed > > > > May 29 21:18:09 dhcp-kea-node2 kea-dhcp4[2755]: 2024-05-29 21:18:09.425 > INFO [kea-dhcp4.hooks/2755.140174953331136] HOOKS_LIBRARY_CLOSED hooks > library /usr/lib/x86_64-linux-gnu/kea/hooks/libdhcp_stat_cmds.so > successfully closed > > > > May 29 21:18:09 dhcp-kea-node2 kea-dhcp4[2755]: 2024-05-29 21:18:09.425 > INFO [kea-dhcp4.hooks/2755.140174953331136] HOOKS_LIBRARY_CLOSED hooks > library /usr/lib/x86_64-linux-gnu/kea/hooks/libdhcp_lease_cmds.so > successfully closed > > > > May 29 21:18:09 dhcp-kea-node2 systemd[1]: isc-kea-dhcp4-server.service: > Main process exited, code=exited, status=1/FAILURE > > > > ░░ Subject: Unit process exited > > > > ░░ Defined-By: systemd > > > > ░░ Support: http://www.ubuntu.com/support > > > > ░░ > > > > ░░ An ExecStart= process belonging to unit isc-kea-dhcp4-server.service > has exited. > > > > ░░ > > > > ░░ The process' exit code is 'exited' and its exit status is 1. > > > > May 29 21:18:09 dhcp-kea-node2 systemd[1]: isc-kea-dhcp4-server.service: > Failed with result 'exit-code'. > > > > ░░ Subject: Unit failed > > > > ░░ Defined-By: systemd > > > > ░░ Support: http://www.ubuntu.com/support > > > > ░░ > > > > ░░ The unit isc-kea-dhcp4-server.service has entered the 'failed' state > with result 'exit-code'. > > > > > > > > When I stop DHCPv6 process, I can start DHCPv4, so it seems that > whatever is going on, they are attempting to bind the very same address? I > did notice that HTTP for kea-dhcpv6 seems to bind to IPv4 address? I am not > sure why that would happen > > > > > > > > May 29 21:32:14 dhcp-kea-node2 kea-dhcp6[1882]: 2024-05-29 21:32:14.885 > INFO [kea-dhcp6.commands/1882.140069120603712] COMMAND_RECEIVED Received > command 'ha-heartbeat' > > > > May 29 21:32:14 dhcp-kea-node2 kea-dhcp6[1882]: 2024-05-29 21:32:14.885 > DEBUG [kea-dhcp6.callouts/1882.140069120603712] HOOKS_CALLOUTS_BEGIN begin > all callouts for hook $ha_heartbeat > > > > May 29 21:32:14 dhcp-kea-node2 kea-dhcp6[1882]: 2024-05-29 21:32:14.885 > DEBUG [kea-dhcp6.callouts/1882.140069120603712] HOOKS_CALLOUT_CALLED hooks > library with index 3 has called a callout on hook $ha_heartbeat that has > address 0x7f6464bb4830 (> > > > > May 29 21:32:14 dhcp-kea-node2 kea-dhcp6[1882]: 2024-05-29 21:32:14.885 > DEBUG [kea-dhcp6.callouts/1882.140069120603712] HOOKS_CALLOUTS_COMPLETE > completed callouts for hook $ha_heartbeat (total callouts duration: 0.071 > ms) > > > > May 29 21:32:14 dhcp-kea-node2 kea-dhcp6[1882]: 2024-05-29 21:32:14.885 > DEBUG [kea-dhcp6.callouts/1882.140069120603712] HOOKS_CALLOUTS_BEGIN begin > all callouts for hook command_processed > > > > May 29 21:32:14 dhcp-kea-node2 kea-dhcp6[1882]: 2024-05-29 21:32:14.885 > DEBUG [kea-dhcp6.callouts/1882.140069120603712] HOOKS_CALLOUT_CALLED hooks > library with index 3 has called a callout on hook command_processed that > has address 0x7f6464bb47> > > > > May 29 21:32:14 dhcp-kea-node2 kea-dhcp6[1882]: 2024-05-29 21:32:14.885 > DEBUG [kea-dhcp6.callouts/1882.140069120603712] HOOKS_CALLOUTS_COMPLETE > completed callouts for hook command_processed (total callouts duration: > 0.018 ms) > > > > May 29 21:32:14 dhcp-kea-node2 kea-dhcp6[1882]: 2024-05-29 21:32:14.885 > DEBUG [kea-dhcp6.http/1882.140069120603712] HTTP_SERVER_RESPONSE_SEND > sending HTTP response HTTP/1.1 200 OK to 192.168.150.221 > > > > May 29 21:32:14 dhcp-kea-node2 kea-dhcp6[1882]: 2024-05-29 21:32:14.885 > DEBUG [kea-dhcp6.http/1882.140069120603712] > HTTP_SERVER_RESPONSE_SEND_DETAILS detailed information about response sent > to 192.168.150.221: > > > > > > > > -- > > ISC funds the development of this software with paid support > subscriptions. Contact us at https://www.isc.org/contact/ for more > information. > > > > To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. > > > > Kea-users mailing list > > Kea-users@lists.isc.org > > https://lists.isc.org/mailman/listinfo/kea-users > -- > ISC funds the development of this software with paid support > subscriptions. Contact us at https://www.isc.org/contact/ for more > information. > > To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. > > Kea-users mailing list > Kea-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/kea-users >
-- ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. Kea-users mailing list Kea-users@lists.isc.org https://lists.isc.org/mailman/listinfo/kea-users
