Kea DHCPv4 crashing Netgate 4100
-
I just redid my home network as I got 2Gbps Internet and my 3100 wasn't cutting it. So I had a 4100 laying around.
kea-dhcp4 stopped working today, and the service will not start. I made no changes since it was running last. I have 23.09.1.
My primary WAN port is actually LAN4 because it is 2.5Gb connected to my modem which has a 2.5Gb port. LAN1 is my lan and the backup internet is on WAN1. I have 4 vlans. Wifi, Work, IOIT & Kids. DHCP sends everything out from the firewall. I am de-servering my house. I don't feel like paying the power bills, I have datacenters anyway to put labs.
Dec 20 12:13:06 kea-dhcp4 96038 ERROR [kea-dhcp4.dhcp4.0x8195f412000] DHCP4_INIT_FAIL failed to initialize Kea server: configuration error using file '/usr/local/etc/kea/kea-dhcp4.conf': cannot lock socket lockfile, /tmp/kea4-ctrl-socket.lock, : Resource temporarily unavailable Dec 20 12:13:06 kea-dhcp4 96038 ERROR [kea-dhcp4.dhcp4.0x8195f412000] DHCP4_CONFIG_LOAD_FAIL configuration error using file: /usr/local/etc/kea/kea-dhcp4.conf, reason: cannot lock socket lockfile, /tmp/kea4-ctrl-socket.lock, : Resource temporarily unavailable Dec 20 12:13:06 kea-dhcp4 96038 ERROR [kea-dhcp4.dhcp4.0x8195f412000] DHCP4_PARSER_COMMIT_FAIL parser failed to commit changes: cannot lock socket lockfile, /tmp/kea4-ctrl-socket.lock, : Resource temporarily unavailableI wonder if the built in storage just died. I am afraid to reboot it.
-
Update: reboot worked... However it was stressful. Not sure what caused that. Gives me pause if kea is ready for production on pfSense. I enabled it to get rid of the warning. Maybe should have held off on the warning until Kea was feature-parity and production-ready.
-
