Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    kea-dhcp4 Kea DHCP Server broken

    DHCP and DNS
    10
    11
    2.9k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • chudakC
      chudak
      last edited by chudak

      FYI

      After upgrading to + 23.09.1 my kea-dhcp4 Kea DHCP Server won't start at all

      ERROR [kea-dhcp4.dhcp4.0x14d4cda12000 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

      Update: it seems it has nothing to do with 23.09.1 upgrade. Kea DHCP breaks after adding a new DHCP Static Mappings via ServicesDHCP ServerLAN

      1 Reply Last reply Reply Quote 0
      • jimpJ jimp moved this topic from Problems Installing or Upgrading pfSense Software on
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        https://redmine.pfsense.org/issues/14977

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        lindheL 1 Reply Last reply Reply Quote 1
        • QinnQ
          Qinn
          last edited by Qinn

          Will this file be removed due to a reboot, as it is in

          /tmp/kea4-ctrl-socket.lock
          

          Hardeware: Intel(R) Celeron(R) J4125 CPU @ 2.00GHz 102 GB mSATA SSD (ZFS)
          Firmware: Latest-stable-pfSense CE (amd64)
          Packages: pfBlockerNG devel-beta (beta tester) - Avahi - Notes - Ntopng - PIMD/udpbroadcastrelay - Service Watchdog - System Patches

          1 Reply Last reply Reply Quote 0
          • I
            itinfo
            last edited by

            chudak,

            Thanks for the insight. I had one static IP Mapping on LAN interface(1) and none on the other(2). 2 would start but 1 would not if 'enabled.'

            Your suggestion work - thanks

            The Bug#14977 remains open and I hope it is a part of the next release.

            KEA represents 5 of the current 29 'Bugs'

            https://redmine.pfsense.org/projects/pfsense/issues?page=2&query_id=164

            1 Reply Last reply Reply Quote 0
            • brezlordB
              brezlord
              last edited by

              This is still a problem.

              ERROR [kea-dhcp4.dhcp4.0xed0fd212000] 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 
              

              Not sure if there is still a bug open.

              1 Reply Last reply Reply Quote 1
              • P
                propeto13
                last edited by propeto13

                before:
                093a4fbb-563a-4a96-89e6-703fd376e06c-Screenshot 2025-02-05 083421.png

                Diagnostics > Command Prompt >

                Execute Shell Command

                rm /tmp/kea4-ctrl-socket.lock
                

                Back to Dashboard and START the kea-dhcp4 service

                after:
                53e5cfe7-8d1c-4d72-b5bc-6fb1c4844e90-image.png

                -this is the way.

                GertjanG 1 Reply Last reply Reply Quote 0
                • GertjanG
                  Gertjan @propeto13
                  last edited by

                  @propeto13

                  Noop.
                  See for yourself :

                  @chudak said in kea-dhcp4 Kea DHCP Server broken:

                  After upgrading to + 23.09.1

                  and that was : 9 Dec 2023, 20:38 so 14 months ago (!)
                  @chudak uses 24.11 = pfSense plus, available since a couple of month so he has the latest 'kea' pfSense implementation, and it works pretty well. No core dumping = no need to (re)start, no need to remove files manually.

                  No "help me" PM's please. Use the forum, the community will thank you.
                  Edit : and where are the logs ??

                  1 Reply Last reply Reply Quote 0
                  • lindheL
                    lindhe @jimp
                    last edited by

                    @jimp Are you sure it's https://redmine.pfsense.org/issues/14977 ?

                    That issue has been resolved for months and I'm on 24.11 and I'm experiencing this issue... I've read a couple of threads here and many people seem to be reporting similar problems and that Redmine issue has come up a couple of times. But it's marked as "Resolved" which is clearly not the case, if that is indeed the issue people are experiencing. Should we open a new issue?

                    Is Kea a beta feature or stable release? I've had nothing but problems with it, think I have to move back to the old one that works.

                    L 1 Reply Last reply Reply Quote 0
                    • L
                      Lobout @lindhe
                      last edited by

                      @lindhe i'm seeing the issue as well on 24.11

                      1 Reply Last reply Reply Quote 0
                      • D
                        Dmc
                        last edited by

                        Ive been going nuts about this. im experiencing the same issue.

                        Kea DHCP servers service has been stopped and I do not have a kea4-ctrl-socket.lock in my tmp. I only see dhcdpconfigure.lock - not sure if its a good idea to remove that

                        D 1 Reply Last reply Reply Quote 0
                        • D
                          Dmc @Dmc
                          last edited by

                          Well, not sure when i switched of to changing my DHCP server backend from ISC to Kea but that resolved it

                          For who may be wondering why their DHCP is not assigning leases
                          Step 1: Status > services > check if your dhcpd services are running or not
                          Step 2: In case they were not (like for me) Advanced > Networking > Set Server backend to ISC

                          Strange thing is despite using numerous 1-2month old backups, this sitting appears to not changed. I guess its something that isn't backed up?

                          Anyways, was a fun headscratcher

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post
                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.