Ismael Suarez Ismael_Suarez at coqui.com
Fri Jul 3 22:48:16 UTC 2020

Dont have ‘client-classes’ in my config. Not using reservations. Just simple subnets.

Used to have it setup in HA but now don’t. Still have de HA_server1 for each subnet. Think that may be bothering somehow?


From: Conor Mullen <conormullen908 at gmail.com>
Sent: Friday, July 3, 2020 6:32 PM
To: Ismael Suarez
Cc: kea-users at lists.isc.org
Subject: Re: [Kea-users] ALLOC_ENGINE_V4_ALLOC_FAIL

Hey Ismael,

I saw a similar error message when I'd broken my ipv4 host reservations in the mysql hosts table. I had subnets with required client classes and when I broke the host reservation for a specific mac address (I had passed in a malformed user-context value) it spit out that same error since it didn't register the mac in question as having a valid reservation. Are you using client classes to gate your subnets? How are you defining reservations?

On Fri, Jul 3, 2020, 5:08 PM Ismael Suarez <Ismael_Suarez at coqui.com<mailto:Ismael_Suarez at coqui.com>> wrote:
Getting the following message:

2020-07-03 16:58:22.354 WARN  [kea-dhcp4.alloc-engine/3131] ALLOC_ENGINE_V4_ALLOC_FAIL [hwtype=1 aa:bb:cc:dd:ee:ff], cid=[aa:bb:cc:dd:ee:ff], tid=0xa5d749bc: failed to allocate an IPv4 address after 0 attempt(s)

In the documentation I see it reads:


%1: failed to allocate an IPv4 address after %2 attempt(s)

The DHCP allocation engine gave up trying to allocate an IPv4 address after the specified number of attempts. This probably means that the address pool from which the allocation is being attempted is either empty, or very nearly empty. As a result, the client will have been refused a lease. The first argument includes the client identification information. This message may indicate that your address pool is too small for the number of clients you are trying to service and should be expanded. Alternatively, if the you know that the number of concurrently active clients is less than the addresses you have available, you may want to consider reducing the lease lifetime. In this way, addresses allocated to clients that are no longer active on the network will become available sooner.

But the leases DB (MySQL) is empty. How can I force kea to reload / reset leases to start fresh?

It was working all good, until I added a few more subnets for further testing, then moved a client to another network/subnet and started seeing the message. Maybe the subnet_id's got mixed or something down that line?

Thanks again everyone!


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 at lists.isc.org<mailto:Kea-users at lists.isc.org>

More information about the Kea-users mailing list