[Kea-users] problem with Postgres leases after upgrade (I think)

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

[Kea-users] problem with Postgres leases after upgrade (I think)

Tim Howe
I had a working kea 1.3 server.  After upgrading to 1.5 and upgrading
my PostgreSQL schema, it appears as if Kea isn't able to correctly use
the new Pg schema(?)

The below errors seem to suggest that it doesn't like the data that is
in the hwtype column of the lease6 table.  In the database all that
data is blank (null?).

Is there some default value I can fill in that will allow it to get past this problem?



2019-04-30 17:12:11.800 DEBUG [kea-dhcp6.leases/10281] DHCP6_PROCESS_IA_NA_REQUEST duid=[00:03:00:01:c8:54:4b:54:e5:28], tid=0xcf349e: server is processing IA_NA option with iaid=1 and hint=(no hint)
2019-04-30 17:12:11.800 DEBUG [kea-dhcp6.dhcpsrv/10281] DHCPSRV_PGSQL_GET_IAID_DUID obtaining IPv4 leases for IAID 1 and DUID 00:03:00:01:c8:54:4b:54:e5:28, lease type 0
2019-04-30 17:12:11.801 ERROR [kea-dhcp6.alloc-engine/10281] ALLOC_ENGINE_V6_ALLOC_ERROR duid=[00:03:00:01:c8:54:4b:54:e5:28], tid=0xcf349e: error during attempt to allocate an IPv6 address: Could not convert data to Lease6, reason: Invalid data:[] for row: 0 col: 13,hwtype : bad lexical cast: source type value could not be interpreted as target
2019-04-30 17:12:11.801 DEBUG [kea-dhcp6.leases/10281] DHCP6_LEASE_ADVERT_FAIL duid=[00:03:00:01:c8:54:4b:54:e5:28], tid=0xcf349e: failed to advertise an address lease for iaid=1
2019-04-30 17:12:11.801 DEBUG [kea-dhcp6.options/10281] DHCP6_ADD_STATUS_CODE_FOR_IA duid=[00:03:00:01:c8:54:4b:54:e5:28], tid=0xcf349e: adding Status Code to IA with iaid=1: NoAddrsAvail(2) "Sorry, no address could be allocated."

--TimH
_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users
Reply | Threaded
Open this post in threaded view
|

Re: [Kea-users] problem with Postgres leases after upgrade (I think)

Tim Howe
On Tue, 30 Apr 2019 17:35:29 -0700
Tim Howe <[hidden email]> wrote:

> I had a working kea 1.3 server.  After upgrading to 1.5 and upgrading
> my PostgreSQL schema, it appears as if Kea isn't able to correctly use
> the new Pg schema(?)
>
> The below errors seem to suggest that it doesn't like the data that is
> in the hwtype column of the lease6 table.  In the database all that
> data is blank (null?).
>
> Is there some default value I can fill in that will allow it to get past this problem?
>
>
>
> 2019-04-30 17:12:11.800 DEBUG [kea-dhcp6.leases/10281] DHCP6_PROCESS_IA_NA_REQUEST duid=[00:03:00:01:c8:54:4b:54:e5:28], tid=0xcf349e: server is processing IA_NA option with iaid=1 and hint=(no hint)
> 2019-04-30 17:12:11.800 DEBUG [kea-dhcp6.dhcpsrv/10281] DHCPSRV_PGSQL_GET_IAID_DUID obtaining IPv4 leases for IAID 1 and DUID 00:03:00:01:c8:54:4b:54:e5:28, lease type 0
> 2019-04-30 17:12:11.801 ERROR [kea-dhcp6.alloc-engine/10281] ALLOC_ENGINE_V6_ALLOC_ERROR duid=[00:03:00:01:c8:54:4b:54:e5:28], tid=0xcf349e: error during attempt to allocate an IPv6 address: Could not convert data to Lease6, reason: Invalid data:[] for row: 0 col: 13,hwtype : bad lexical cast: source type value could not be interpreted as target
> 2019-04-30 17:12:11.801 DEBUG [kea-dhcp6.leases/10281] DHCP6_LEASE_ADVERT_FAIL duid=[00:03:00:01:c8:54:4b:54:e5:28], tid=0xcf349e: failed to advertise an address lease for iaid=1
> 2019-04-30 17:12:11.801 DEBUG [kea-dhcp6.options/10281] DHCP6_ADD_STATUS_CODE_FOR_IA duid=[00:03:00:01:c8:54:4b:54:e5:28], tid=0xcf349e: adding Status Code to IA with iaid=1: NoAddrsAvail(2) "Sorry, no address could be allocated."
>
> --TimH
> _______________________________________________
> Kea-users mailing list
> [hidden email]
> https://lists.isc.org/mailman/listinfo/kea-users


        I think the problem is in src/lib/dhcpsrv/pgsql_lease_mgr.cc

        I notice the state column is ignored here (around line 805).
Is my data different after schema upgrade than would be expected if I
started with 1.5?  Seems this is a data sanity check problem, but I
haven't looked at this code before.

--TimH
_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users
Reply | Threaded
Open this post in threaded view
|

Re: [Kea-users] problem with Postgres leases after upgrade (I think)

Brant Ian Stevens
Seeing the same...

Did you ever find a resolution? Need any more data collected?

2019-05-16 20:02:00.091 INFO  [kea-dhcp6.dhcp6/747] DHCP6_STARTED Kea DHCPv6 server version 1.5.0 started
2019-05-16 20:07:31.706 ERROR [kea-dhcp6.alloc-engine/747] ALLOC_ENGINE_V6_ALLOC_ERROR duid=[REMOVED, tid=0x5aecf0: error during attempt to allocate an IPv6 address: Could not convert data to Lease6, reason: Invalid data:[] for row: 0 col: 13,hwtype : bad lexical cast: source type value could not be interpreted as target
2019-05-16 20:07:32.660 ERROR [kea-dhcp6.alloc-engine/747] ALLOC_ENGINE_V6_ALLOC_ERROR duid=[REMOVED, tid=0x5aecf0: error during attempt to allocate an IPv6 address: Could not convert data to Lease6, reason: Invalid data:[] for row: 0 col: 13,hwtype : bad lexical cast: source type value could not be interpreted as target
2019-05-16 20:07:34.839 ERROR [kea-dhcp6.alloc-engine/747] ALLOC_ENGINE_V6_ALLOC_ERROR duid=[REMOVED, tid=0x5aecf0: error during attempt to allocate an IPv6 address: Could not convert data to Lease6, reason: Invalid data:[] for row: 0 col: 13,hwtype : bad lexical cast: source type value could not be interpreted as target
2019-05-16 20:07:39.404 ERROR [kea-dhcp6.alloc-engine/747] ALLOC_ENGINE_V6_ALLOC_ERROR duid=[REMOVED, tid=0x5aecf0: error during attempt to allocate an IPv6 address: Could not convert data to Lease6, reason: Invalid data:[] for row: 0 col: 13,hwtype : bad lexical cast: source type value could not be interpreted as target
2019-05-16 20:07:48.442 ERROR [kea-dhcp6.alloc-engine/747] ALLOC_ENGINE_V6_ALLOC_ERROR duid=[REMOVED, tid=0x5aecf0: error during attempt to allocate an IPv6 address: Could not convert data to Lease6, reason: Invalid data:[] for row: 0 col: 13,hwtype : bad lexical cast: source type value could not be interpreted as target
2019-05-16 20:08:05.809 ERROR [kea-dhcp6.alloc-engine/747] ALLOC_ENGINE_V6_ALLOC_ERROR duid=[REMOVED, tid=0x5aecf0: error during attempt to allocate an IPv6 address: Could not convert data to Lease6, reason: Invalid data:[] for row: 0 col: 13,hwtype : bad lexical cast: source type value could not be interpreted as target


--
--
Regards,
--
Brant I. Stevens, founder.
[hidden email]
o:212.882.1185. m:917.673.6536. f:917.525.4759.
https://www.sinewave.network



Tim Howe wrote on 4/30/19 8:50 PM:
On Tue, 30 Apr 2019 17:35:29 -0700
Tim Howe [hidden email] wrote:

I had a working kea 1.3 server.  After upgrading to 1.5 and upgrading
my PostgreSQL schema, it appears as if Kea isn't able to correctly use
the new Pg schema(?)

The below errors seem to suggest that it doesn't like the data that is
in the hwtype column of the lease6 table.  In the database all that
data is blank (null?).

Is there some default value I can fill in that will allow it to get past this problem?



2019-04-30 17:12:11.800 DEBUG [kea-dhcp6.leases/10281] DHCP6_PROCESS_IA_NA_REQUEST duid=[00:03:00:01:c8:54:4b:54:e5:28], tid=0xcf349e: server is processing IA_NA option with iaid=1 and hint=(no hint)
2019-04-30 17:12:11.800 DEBUG [kea-dhcp6.dhcpsrv/10281] DHCPSRV_PGSQL_GET_IAID_DUID obtaining IPv4 leases for IAID 1 and DUID 00:03:00:01:c8:54:4b:54:e5:28, lease type 0
2019-04-30 17:12:11.801 ERROR [kea-dhcp6.alloc-engine/10281] ALLOC_ENGINE_V6_ALLOC_ERROR duid=[00:03:00:01:c8:54:4b:54:e5:28], tid=0xcf349e: error during attempt to allocate an IPv6 address: Could not convert data to Lease6, reason: Invalid data:[] for row: 0 col: 13,hwtype : bad lexical cast: source type value could not be interpreted as target
2019-04-30 17:12:11.801 DEBUG [kea-dhcp6.leases/10281] DHCP6_LEASE_ADVERT_FAIL duid=[00:03:00:01:c8:54:4b:54:e5:28], tid=0xcf349e: failed to advertise an address lease for iaid=1
2019-04-30 17:12:11.801 DEBUG [kea-dhcp6.options/10281] DHCP6_ADD_STATUS_CODE_FOR_IA duid=[00:03:00:01:c8:54:4b:54:e5:28], tid=0xcf349e: adding Status Code to IA with iaid=1: NoAddrsAvail(2) "Sorry, no address could be allocated."

--TimH
_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users

	I think the problem is in src/lib/dhcpsrv/pgsql_lease_mgr.cc

	I notice the state column is ignored here (around line 805).
Is my data different after schema upgrade than would be expected if I
started with 1.5?  Seems this is a data sanity check problem, but I
haven't looked at this code before.

--TimH
_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users


_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users
Reply | Threaded
Open this post in threaded view
|

Re: [Kea-users] problem with Postgres leases after upgrade (I think)

Brant Ian Stevens
Forgive the top-post...

I noticed that this was happening on devices that had reservations.  New leases seem to go out without an issue.


Brant Ian Stevens wrote on 5/16/19 8:23 PM:
Seeing the same...

Did you ever find a resolution? Need any more data collected?

2019-05-16 20:02:00.091 INFO  [kea-dhcp6.dhcp6/747] DHCP6_STARTED Kea DHCPv6 server version 1.5.0 started
2019-05-16 20:07:31.706 ERROR [kea-dhcp6.alloc-engine/747] ALLOC_ENGINE_V6_ALLOC_ERROR duid=[REMOVED, tid=0x5aecf0: error during attempt to allocate an IPv6 address: Could not convert data to Lease6, reason: Invalid data:[] for row: 0 col: 13,hwtype : bad lexical cast: source type value could not be interpreted as target
2019-05-16 20:07:32.660 ERROR [kea-dhcp6.alloc-engine/747] ALLOC_ENGINE_V6_ALLOC_ERROR duid=[REMOVED, tid=0x5aecf0: error during attempt to allocate an IPv6 address: Could not convert data to Lease6, reason: Invalid data:[] for row: 0 col: 13,hwtype : bad lexical cast: source type value could not be interpreted as target
2019-05-16 20:07:34.839 ERROR [kea-dhcp6.alloc-engine/747] ALLOC_ENGINE_V6_ALLOC_ERROR duid=[REMOVED, tid=0x5aecf0: error during attempt to allocate an IPv6 address: Could not convert data to Lease6, reason: Invalid data:[] for row: 0 col: 13,hwtype : bad lexical cast: source type value could not be interpreted as target
2019-05-16 20:07:39.404 ERROR [kea-dhcp6.alloc-engine/747] ALLOC_ENGINE_V6_ALLOC_ERROR duid=[REMOVED, tid=0x5aecf0: error during attempt to allocate an IPv6 address: Could not convert data to Lease6, reason: Invalid data:[] for row: 0 col: 13,hwtype : bad lexical cast: source type value could not be interpreted as target
2019-05-16 20:07:48.442 ERROR [kea-dhcp6.alloc-engine/747] ALLOC_ENGINE_V6_ALLOC_ERROR duid=[REMOVED, tid=0x5aecf0: error during attempt to allocate an IPv6 address: Could not convert data to Lease6, reason: Invalid data:[] for row: 0 col: 13,hwtype : bad lexical cast: source type value could not be interpreted as target
2019-05-16 20:08:05.809 ERROR [kea-dhcp6.alloc-engine/747] ALLOC_ENGINE_V6_ALLOC_ERROR duid=[REMOVED, tid=0x5aecf0: error during attempt to allocate an IPv6 address: Could not convert data to Lease6, reason: Invalid data:[] for row: 0 col: 13,hwtype : bad lexical cast: source type value could not be interpreted as target


--
--
Regards,
--
Brant I. Stevens, founder.
[hidden email]
o:212.882.1185. m:917.673.6536. f:917.525.4759.
https://www.sinewave.network



Tim Howe wrote on 4/30/19 8:50 PM:
On Tue, 30 Apr 2019 17:35:29 -0700
Tim Howe [hidden email] wrote:

I had a working kea 1.3 server.  After upgrading to 1.5 and upgrading
my PostgreSQL schema, it appears as if Kea isn't able to correctly use
the new Pg schema(?)

The below errors seem to suggest that it doesn't like the data that is
in the hwtype column of the lease6 table.  In the database all that
data is blank (null?).

Is there some default value I can fill in that will allow it to get past this problem?



2019-04-30 17:12:11.800 DEBUG [kea-dhcp6.leases/10281] DHCP6_PROCESS_IA_NA_REQUEST duid=[00:03:00:01:c8:54:4b:54:e5:28], tid=0xcf349e: server is processing IA_NA option with iaid=1 and hint=(no hint)
2019-04-30 17:12:11.800 DEBUG [kea-dhcp6.dhcpsrv/10281] DHCPSRV_PGSQL_GET_IAID_DUID obtaining IPv4 leases for IAID 1 and DUID 00:03:00:01:c8:54:4b:54:e5:28, lease type 0
2019-04-30 17:12:11.801 ERROR [kea-dhcp6.alloc-engine/10281] ALLOC_ENGINE_V6_ALLOC_ERROR duid=[00:03:00:01:c8:54:4b:54:e5:28], tid=0xcf349e: error during attempt to allocate an IPv6 address: Could not convert data to Lease6, reason: Invalid data:[] for row: 0 col: 13,hwtype : bad lexical cast: source type value could not be interpreted as target
2019-04-30 17:12:11.801 DEBUG [kea-dhcp6.leases/10281] DHCP6_LEASE_ADVERT_FAIL duid=[00:03:00:01:c8:54:4b:54:e5:28], tid=0xcf349e: failed to advertise an address lease for iaid=1
2019-04-30 17:12:11.801 DEBUG [kea-dhcp6.options/10281] DHCP6_ADD_STATUS_CODE_FOR_IA duid=[00:03:00:01:c8:54:4b:54:e5:28], tid=0xcf349e: adding Status Code to IA with iaid=1: NoAddrsAvail(2) "Sorry, no address could be allocated."

--TimH
_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users
	I think the problem is in src/lib/dhcpsrv/pgsql_lease_mgr.cc

	I notice the state column is ignored here (around line 805).
Is my data different after schema upgrade than would be expected if I
started with 1.5?  Seems this is a data sanity check problem, but I
haven't looked at this code before.

--TimH
_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users



_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users
Reply | Threaded
Open this post in threaded view
|

Re: [Kea-users] problem with Postgres leases after upgrade (I think)

Tim Howe
In reply to this post by Brant Ian Stevens
On Thu, 16 May 2019 20:23:34 -0400
Brant Ian Stevens <[hidden email]> wrote:

> Seeing the same...
>
> Did you ever find a resolution? Need any more data collected?

        I was in a bit of hurry at the time, so I built an empty
database and new stuff was fine.  I did have to restart a number of
clients, though.

--TimH
_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users