KEA and service watchdog
-
Hi,
Is anyone aware of an issue with Kea dhcp service stopping when watchdog is enabled?
Process PID Message
kea-dhcp4 19315 WARN [kea-dhcp4.dhcp4.0x33176c212000] DHCP4_MULTI_THREADING_INFO enabled: yes, number of threads: 8, queue size: 64
kea-dhcp4 19315 WARN [kea-dhcp4.dhcpsrv.0x33176c212000] DHCPSRV_NO_SOCKETS_OPEN no interface configured to listen to DHCP traffic
kea-dhcp4 19315 WARN [kea-dhcp4.dhcpsrv.0x33176c212000] DHCPSRV_OPEN_SOCKET_FAIL failed to open socket: Failed to open socket on interface ix1.1206, reason: failed to bind fallback socket to address 192.168.200.1, port 67, reason: Address already in use - is another DHCP server running?
kea-dhcp4 19315 WARN [kea-dhcp4.dhcpsrv.0x33176c212000] DHCPSRV_OPEN_SOCKET_FAIL failed to open socket: Failed to open socket on interface ix1.1206, reason: failed to bind fallback socket to address 192.168.200.2, port 67, reason: Address already in use - is another DHCP server running?
kea-dhcp4 19315 WARN [kea-dhcp4.dhcpsrv.0x33176c212000] DHCPSRV_OPEN_SOCKET_FAIL failed to open socket: Failed to open socket on interface ix1.1201, reason: failed to bind fallback socket to address 10.10.10.1, port 67, reason: Address already in use - is another DHCP server running?
kea-dhcp4 19315 WARN [kea-dhcp4.dhcpsrv.0x33176c212000] DHCPSRV_OPEN_SOCKET_FAIL failed to open socket: Failed to open socket on interface ix1.1201, reason: failed to bind fallback socket to address 100.64.0.1, port 67, reason: Address already in use - is another DHCP server running?
kea-dhcp4 19315 WARN [kea-dhcp4.dhcpsrv.0x33176c212000] DHCPSRV_OPEN_SOCKET_FAIL failed to open socket: Failed to open socket on interface ix1.1201, reason: failed to bind fallback socket to address 100.64.0.2, port 67, reason: Address already in use - is another DHCP server running?
kea-dhcp4 19315 WARN [kea-dhcp4.dhcpsrv.0x33176c212000] DHCPSRV_OPEN_SOCKET_FAIL failed to open socket: Failed to open socket on interface ix1.1200, reason: failed to bind fallback socket to address 192.168.255.1, port 67, reason: Address already in use - is another DHCP server running?
kea-dhcp4 19315 WARN [kea-dhcp4.dhcpsrv.0x33176c212000] DHCPSRV_OPEN_SOCKET_FAIL failed to open socket: Failed to open socket on interface ix1.1200, reason: failed to bind fallback socket to address 192.168.255.2, port 67, reason: Address already in use - is another DHCP server running?
kea-dhcp4 19315 WARN [kea-dhcp4.dhcpsrv.0x33176c212000] DHCPSRV_MULTIPLE_RAW_SOCKETS_PER_IFACE current configuration will result in opening multiple broadcast capable sockets on some interfaces and some DHCP messages may be duplicated
kea-dhcp4 19315 WARN [kea-dhcp4.dhcp4.0x33176c212000] DHCP4_RESERVATIONS_LOOKUP_FIRST_ENABLED Multi-threading is enabled and host reservations lookup is always performed first.
kea-dhcp4 19315 WARN [kea-dhcp4.dhcpsrv.0x33176c212000] DHCPSRV_MT_DISABLED_QUEUE_CONTROL disabling dhcp queue control when multi-threading is enabled.
kea-dhcp4 60221 WARN [kea-dhcp4.dhcp4.0x5bf27612000] DHCP4_MULTI_THREADING_INFO enabled: yes, number of threads: 8, queue size: 64
kea-dhcp4 60221 WARN [kea-dhcp4.dhcpsrv.0x5bf27612000] DHCPSRV_NO_SOCKETS_OPEN no interface configured to listen to DHCP traffic -
@Mr_JinX There was another thread about where another KEA instance was running (or not stopped for some reason).
In that other case, stopping KEA and check if there's still another KEA running did help. And then of corse kill that process and restart KEA from the GUI.
Basically the message does say that there's another process bound to the same port and therefore KEA can't bind to it.
kea-dhcp4 19315 WARN [kea-dhcp4.dhcpsrv.0x33176c212000] DHCPSRV_NO_SOCKETS_OPEN no interface configured to listen to DHCP traffic
Have you setup KEA to listen to some interfaces?
-
@patient0 Hi, thank you, kia should be listening on all LAN interfaces (and VIP's) it seems to run for a short time then stop, moving back ICS seems to have fixed the issue.
I don't understand why irtwould run and then stop,
