[Kea-users] Infinite lease not stored in postgresql DB

Thomas Markwalder tmark at isc.org
Thu Jun 6 18:49:53 UTC 2019


Please see section 4.3.6 of Kea Admin Guide:

https://jenkins.isc.org/job/Kea_doc/guide/kea-guide.html#idm139894053942032



On 6/6/19 12:56 PM, Sten Carlsen wrote:
> This was just a quick check for obvious things, I have nor used 
> database backends. I am trying to learn because I see obvious 
> advantages in my setting.
>
>
> -- 
> Best regards
>
> Sten Carlsen
>
> No improvements come from shouting:
>
>       "MALE BOVINE MANURE!!!"
>
> On 6 Jun 2019, at 18.24, Laurent Aubert (laaubert) <laaubert at cisco.com 
> <mailto:laaubert at cisco.com>> wrote:
>
>> Thanks Sten for your reply.
>>
>> In our understanding the tool kea-admin lease-init, initialize the 
>> PostgresDB with the right schema defined for Kea
>>
>> The way data is stored in PostgresDB is defined by Kea schema, which 
>> is defined here:
>>
>> https://github.com/isc-projects/kea/blob/master/src/share/database/scripts/pgsql/dhcpdb_create.pgsql
>>
>> Where valid_lifetime is define as:
>>
>> valid_lifetime BIGINT,
>>
>> And according to PostgreSQL doc is:
>>
>> bigint 8 bytes  large-range integer -9223372036854775808 to 
>> +9223372036854775807
>>
>> So is there a problem with the schema for PostgreSQL ?
>>
>> Thanks,
>>
>> Laurent.
>>
>> *From: *Kea-users <kea-users-bounces at lists.isc.org 
>> <mailto:kea-users-bounces at lists.isc.org>> on behalf of Sten Carlsen 
>> <stenc at s-carlsen.dk <mailto:stenc at s-carlsen.dk>>
>> *Date: *Thursday, June 6, 2019 at 5:20 PM
>> *To: *"kea-users at lists.isc.org <mailto:kea-users at lists.isc.org>" 
>> <kea-users at lists.isc.org <mailto:kea-users at lists.isc.org>>
>> *Subject: *Re: [Kea-users] Infinite lease not stored in postgresql DB
>>
>> On 06/06/2019 13.02, Laurent Aubert (laaubert) wrote:
>>
>>     Hi,
>>
>>     We deployed KEA 1.5 with a postgresql DB without any issue. We
>>     have an application which asks for IP addresses with an infinite
>>     lease.
>>
>>     When KEA receives the request, we see the following error:
>>
>>     2019 <tel:2019>-06-06 09:05:02.566 ERROR
>>     [kea-dhcp4.alloc-engine/259] ALLOC_ENGINE_V4_ALLOC_ERROR
>>     [hwtype=1 00:00:00:00:00:00],
>>     cid=[ff:00:00:00:00:00:02:00:00:00:09:01:10:49:52:38:30:39:47:2d:4c:54:45:2d:47:41:2d:4b:39:02:0
>>     b:4a:4d:58:32:30:32:33:58:30:30:30], tid=0x8aed1f: error during
>>     attempt to allocate an IPv4 address: Could not create bind array
>>     from Lease4:192.168.89.2 <http://192.168.89.2>, reason: Time
>>     value is too large:5854779197 <tel:5854779197>
>>
>> How is your definition of the lease time field in the database? this 
>> value requires 33 bits to be stored.
>>
>>     Everything works fine if we use csv file to store the leases
>>     instead of postgres.
>>
>> Yes, not limited by a fixed number of bits.
>>
>>     Any idea why such leases can’t be stored in the DB ?
>>
>> Sten
>>
>
> _______________________________________________
> Kea-users mailing list
> Kea-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/kea-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20190606/21bfd861/attachment-0001.html>


More information about the Kea-users mailing list