[Kea-users] 1.3.0 beta not working with mysql
Locked
12
12
 
|
Hi all I'm having problems with the current beta not working with a 'mysql' server, I've built this version against the current MariaDB version (and the required devel versions) - all these servers are CentOS7 (fully updated): Installed Packages Name : MariaDB-server Arch : x86_64 Version : 10.2.9 Release : 1.el7.centos Size : 456 M Repo : installed Summary : MariaDB: a very fast and robust SQL database server Installed Packages Name : MariaDB-devel Arch : x86_64 Version : 10.2.9 Release : 1.el7.centos Size : 39 M Repo : installed # Percona cluster dnf info Percona-XtraDB-cluster-57 Using metadata from Wed Oct 4 11:54:00 2017 The database was created as per the documentation and all the tables and stored procedures exist, this is a single server. However when a machine requests an IP I'm seeing the following errors in the log file: 2017-10-05 18:16:10.273 INFO [kea-dhcp4.dhcp4/24862] DHCP4_STARTED Kea DHCPv4 server version 1.3.0-beta started 2017-10-05 18:16:19.020 INFO [kea-dhcp4.leases/24862] DHCP4_LEASE_ADVERT [hwtype=1 00:0c:29:bc:bc:18], cid=[01:00:0c:29:bc:bc:18], tid=0x2c0f9a70: lease 192.168.1.160 will be advertised 2017-10-05 18:16:19.021 INFO [kea-dhcp4.leases/24862] DHCP4_LEASE_ADVERT [hwtype=1 00:0c:29:bc:bc:18], cid=[01:00:0c:29:bc:bc:18], tid=0x2c0f9a70: lease 192.168.1.161 will be advertised 2017-10-05 18:16:19.029 ERROR [kea-dhcp4.alloc-engine/24862] ALLOC_ENGINE_V4_ALLOC_ERROR [hwtype=1 00:0c:29:bc:bc:18], cid=[01:00:0c:29:bc:bc:18], tid=0xa6d4566b: error during attempt to allocate an IPv4 address: unable to bind parameters for <INSERT INTO lease4(address, hwaddr, client_id, valid_lifetime, expire, subnet_id, fqdn_fwd, fqdn_rev, hostname, state) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?)>, reason: (error code 0) I'm also trying to get this working with a Percona XtraDB cluster and having the same problem, this a a five server cluster: Installed Packages Name : Percona-XtraDB-Cluster-57 Arch : x86_64 Epoch : 0 Version : 5.7.19 Release : 29.22.1.el7 Size : 0.0 Repo : @System From repo : percona-release-x86_64 2017-10-05 18:06:44.996 INFO [kea-dhcp4.leases/16988] DHCP4_INIT_REBOOT [hwtype=1 00:0c:29:bc:bc:18], cid=[01:00:0c:29:bc:bc:18], tid=0x9ddd43c: client is in INIT-REBOOT state and requests address 192.168.1.161 2017-10-05 18:06:52.548 INFO [kea-dhcp4.leases/16988] DHCP4_INIT_REBOOT [hwtype=1 da:d9:a8:4c:30:9d], cid=[01:da:d9:a8:4c:30:9d], tid=0x1299a707: client is in INIT-REBOOT state and requests address 192.168.1.170 2017-10-05 18:07:00.225 INFO [kea-dhcp4.leases/16988] DHCP4_LEASE_ADVERT [hwtype=1 00:0c:29:bc:bc:18], cid=[01:00:0c:29:bc:bc:18], tid=0x989c660b: lease 192.168.1.160 will be advertised 2017-10-05 18:07:00.227 INFO [kea-dhcp4.leases/16988] DHCP4_LEASE_ADVERT [hwtype=1 00:0c:29:bc:bc:18], cid=[01:00:0c:29:bc:bc:18], tid=0x989c660b: lease 192.168.1.161 will be advertised 2017-10-05 18:07:00.228 ERROR [kea-dhcp4.alloc-engine/16988] ALLOC_ENGINE_V4_ALLOC_ERROR [hwtype=1 00:0c:29:bc:bc:18], cid=[01:00:0c:29:bc:bc:18], tid=0xed6a4f7f: error during attempt to allocate an IPv4 address: unable to bind parameters for <INSERT INTO lease4(address, hwaddr, client_id, valid_lifetime, expire, subnet_id, fqdn_fwd, fqdn_rev, hostname, state) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?)>, reason: (error code 0) In both of those cases on the cluster and the single server the error messages just keep repeating. There is also nothing in the leases table. Does anyone currently use a DB for lease data? Is there any more information I can provide about this problem? Is this likely to be something I've missed in building kea? Kea 1.3 beta does work OK using a file for lease storage. :) Regards Bill _______________________________________________ Kea-users mailing list [hidden email] https://lists.isc.org/mailman/listinfo/kea-users |
Re: [Kea-users] 1.3.0 beta not working with mysql
|
|
Hello, can you show us reservation you put into database? Wlodek On 05/10/2017 18:52, Bill Pye wrote:
_______________________________________________ Kea-users mailing list [hidden email] https://lists.isc.org/mailman/listinfo/kea-users |
|
|
Hi Am I missing something that obvious and basic, do I need to create something in the lease table? Regards Bill From: "Wlodek Wencel" <[hidden email]>
_______________________________________________ Kea-users mailing list [hidden email] https://lists.isc.org/mailman/listinfo/kea-users |
Re: [Kea-users] 1.3.0 beta not working with mysql
|
|
Hi Bill:
No, you don't need anything pre-inserted into the lease table(s). What's puzzling is the error code of 0 being reported. We are invoking mysql_stmt_bind_param (a mysql client library func) and it is failing BUT the mysql library error code is 0. There is/was a mysql client library bug where that was true but for mysql_stmt_execute(). This occurred when a client using prepared statements got disconnected for being idle and was configured to use auto-reconnect. Upon reconnect we would try to use our now invalid prepared statements. We addresses this with ticket: https://kea.isc.org/ticket/5354 But the symptoms for that were slightly different than you report. Part of that resolution of that ticket was to code kea to 1: turn of auto-reconnect and 2: set the idle timeout to an extremely large value. Prior to setting it we were subject the global value, which by default is 28800 seconds but the user had configured his system to set to 60 seconds. I find it hard to see how your environment could be circumventing those changes. I only mention it now because of the error code being 0. Normally, mysql client library functions always return a non-zero error code when they fail. It makes it doubly frustrating because client side errors like this are not logged by the server. So a couple of questions: 1. Is this just a normal, dynamic client (i.e. no host reservations involved) ? 2. How long after Kea starts up is it before the client interaction begins ? 3. I'm assuming this happens every time a client request comes in? Thanks, Thomas Markwalder ISC Software Engineering On 10/5/17 2:00 PM, Bill Pye wrote: > Hi > > Am I missing something that obvious and basic, do I need to create > something in the lease table? > > Regards > > Bill > > ------------------------------------------------------------------------ > > *From: *"Wlodek Wencel" <[hidden email]> > *To: *"kea-users" <[hidden email]> > *Sent: *Thursday, 5 October, 2017 19:27:06 > *Subject: *Re: [Kea-users] 1.3.0 beta not working with mysql > > Hello, > > can you show us reservation you put into database? > > Wlodek > > > On 05/10/2017 18:52, Bill Pye wrote: > > Hi all > > I'm having problems with the current beta not working with a > 'mysql' server, I've built this version against the current > MariaDB version (and the required devel versions) - all these > servers are CentOS7 (fully updated): > > Installed Packages > Name : MariaDB-server > Arch : x86_64 > Version : 10.2.9 > Release : 1.el7.centos > Size : 456 M > Repo : installed > Summary : MariaDB: a very fast and robust SQL database server > > Installed Packages > Name : MariaDB-devel > Arch : x86_64 > Version : 10.2.9 > Release : 1.el7.centos > Size : 39 M > Repo : installed > > # Percona cluster > > dnf info Percona-XtraDB-cluster-57 > Using metadata from Wed Oct 4 11:54:00 2017 > > The database was created as per the documentation and all the > tables and stored procedures exist, this is a single server. > However when a machine requests an IP I'm seeing the following > errors in the log file: > > 2017-10-05 18:16:10.273 INFO [kea-dhcp4.dhcp4/24862] > DHCP4_STARTED Kea DHCPv4 server version 1.3.0-beta started > > 2017-10-05 18:16:19.020 INFO [kea-dhcp4.leases/24862] > DHCP4_LEASE_ADVERT [hwtype=1 00:0c:29:bc:bc:18], > cid=[01:00:0c:29:bc:bc:18], tid=0x2c0f9a70: lease > 192.168.1.160 will be advertised > 2017-10-05 18:16:19.021 INFO [kea-dhcp4.leases/24862] > DHCP4_LEASE_ADVERT [hwtype=1 00:0c:29:bc:bc:18], > cid=[01:00:0c:29:bc:bc:18], tid=0x2c0f9a70: lease > 192.168.1.161 will be advertised > 2017-10-05 18:16:19.029 ERROR [kea-dhcp4.alloc-engine/24862] > ALLOC_ENGINE_V4_ALLOC_ERROR [hwtype=1 00:0c:29:bc:bc:18], > cid=[01:00:0c:29:bc:bc:18], tid=0xa6d4566b: error during > attempt to allocate an IPv4 address: unable to bind parameters > for <INSERT INTO lease4(address, hwaddr, client_id, > valid_lifetime, expire, subnet_id, fqdn_fwd, fqdn_rev, > hostname, state) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?)>, > reason: (error code 0) > > I'm also trying to get this working with a Percona XtraDB > cluster and having the same problem, this a a five server cluster: > > Installed Packages > Name : Percona-XtraDB-Cluster-57 > Arch : x86_64 > Epoch : 0 > Version : 5.7.19 > Release : 29.22.1.el7 > Size : 0.0 > Repo : @System > From repo : percona-release-x86_64 > > 2017-10-05 18:06:44.996 INFO [kea-dhcp4.leases/16988] > DHCP4_INIT_REBOOT [hwtype=1 00:0c:29:bc:bc:18], > cid=[01:00:0c:29:bc:bc:18], tid=0x9ddd43c: client is in > INIT-REBOOT state and requests address 192.168.1.161 > 2017-10-05 18:06:52.548 INFO [kea-dhcp4.leases/16988] > DHCP4_INIT_REBOOT [hwtype=1 da:d9:a8:4c:30:9d], > cid=[01:da:d9:a8:4c:30:9d], tid=0x1299a707: client is in > INIT-REBOOT state and requests address 192.168.1.170 > 2017-10-05 18:07:00.225 INFO [kea-dhcp4.leases/16988] > DHCP4_LEASE_ADVERT [hwtype=1 00:0c:29:bc:bc:18], > cid=[01:00:0c:29:bc:bc:18], tid=0x989c660b: lease > 192.168.1.160 will be advertised > 2017-10-05 18:07:00.227 INFO [kea-dhcp4.leases/16988] > DHCP4_LEASE_ADVERT [hwtype=1 00:0c:29:bc:bc:18], > cid=[01:00:0c:29:bc:bc:18], tid=0x989c660b: lease > 192.168.1.161 will be advertised > 2017-10-05 18:07:00.228 ERROR [kea-dhcp4.alloc-engine/16988] > ALLOC_ENGINE_V4_ALLOC_ERROR [hwtype=1 00:0c:29:bc:bc:18], > cid=[01:00:0c:29:bc:bc:18], tid=0xed6a4f7f: error during > attempt to allocate an IPv4 address: unable to bind parameters > for <INSERT INTO lease4(address, hwaddr, client_id, > valid_lifetime, expire, subnet_id, fqdn_fwd, fqdn_rev, > hostname, state) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?)>, > reason: (error code 0) > > In both of those cases on the cluster and the single server > the error messages just keep repeating. There is also nothing > in the leases table. > > Does anyone currently use a DB for lease data? Is there any > more information I can provide about this problem? Is this > likely to be something I've missed in building kea? Kea 1.3 > beta does work OK using a file for lease storage. :) > > Regards > > > Bill > > > > > > > > > > _______________________________________________ > 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 > > > > _______________________________________________ > 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 |
Re: [Kea-users] 1.3.0 beta not working with mysql
|
|
In reply to this post by Bill Pye
Hi Bill:
I've attached a test patch if you're willing. Per MariaDB the max value for --wait-timeout is 2147483, and we are exceeding that. I'm wondering if our attempt to set it is failing silently. The patch I sent you attempts to set it to a number well under their max but much larger than their default. Thanks, Thomas _______________________________________________ Kea-users mailing list [hidden email] https://lists.isc.org/mailman/listinfo/kea-users |
timeout.diff (1K) |
|
Hi Thomas
Yes, I'll give that a go but I'm afraid you'll have to give me the steps to apply it. Regards Bill ----- Original Message ----- > From: "Thomas Markwalder" <[hidden email]> > To: "kea-users" <[hidden email]> > Sent: Friday, 6 October, 2017 14:00:36 > Subject: Re: [Kea-users] 1.3.0 beta not working with mysql > Hi Bill: > > I've attached a test patch if you're willing. Per MariaDB the max > value for --wait-timeout is 2147483, and we are exceeding that. I'm > wondering if our attempt to set it is failing silently. The patch I > sent you attempts to set it to a number well under their max but much > larger than their default. > > Thanks, > > Thomas > > > > > _______________________________________________ > 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 |
Re: [Kea-users] 1.3.0 beta not working with mysql
|
|
Hey Bill:
Sure, rather than try to use git apply, you can just make the alteration by editing the file with any text editor. You would then need to rerun make and make install. 1. Edit this file: <wherever you unrolled kea tar ball>src/lib/dhcpsrv/mysql_connection.cc Change line 175 from this: const char *wait_time = "SET SESSION wait_timeout = 30 * 86400"; to this: const char *wait_time = "SET SESSION wait_timeout = 214000"; Save it, then rerun make and make install. Thanks, Thomas On 10/6/17 9:06 AM, Bill Pye wrote: > Hi Thomas > > Yes, I'll give that a go but I'm afraid you'll have to give me the steps to apply it. > > > Regards > > > Bill > > ----- Original Message ----- >> From: "Thomas Markwalder" <[hidden email]> >> To: "kea-users" <[hidden email]> >> Sent: Friday, 6 October, 2017 14:00:36 >> Subject: Re: [Kea-users] 1.3.0 beta not working with mysql >> Hi Bill: >> >> I've attached a test patch if you're willing. Per MariaDB the max >> value for --wait-timeout is 2147483, and we are exceeding that. I'm >> wondering if our attempt to set it is failing silently. The patch I >> sent you attempts to set it to a number well under their max but much >> larger than their default. >> >> Thanks, >> >> Thomas >> >> >> >> >> _______________________________________________ >> 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 _______________________________________________ Kea-users mailing list [hidden email] https://lists.isc.org/mailman/listinfo/kea-users |
|
|
Hi Thomas
Done that and built it on a CentOS7 server, installed it and pointed the DB to a single MariaDB server with the same results: 2017-10-06 16:51:48.304 ERROR [kea-dhcp4.alloc-engine/2899] ALLOC_ENGINE_V4_ALLOC_ERROR [hwtype=1 00:0c:29:bc:bc:18], cid=[01:00:0c:29:bc:bc:18], tid=0xf8e3db07: error during attempt to allocate an IPv4 address: unable to bind parameters for <INSERT INTO lease4(address, hwaddr, client_id, valid_lifetime, expire, subnet_id, fqdn_fwd, fqdn_rev, hostname, state) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?)>, reason: (error code 0) Details off the build: kea-dhcp4 -V 1.3.0-beta tarball linked with: log4cplus 1.1.3 OpenSSL 1.0.2k-fips 26 Jan 2017 database: MySQL backend 5.1, library 10.2.9 PostgreSQL backend 3.1, library 90223 Memfile backend 2.0 If there is anything else you want me to try then just shout. Regards Bill ----- Original Message ----- > From: "Thomas Markwalder" <[hidden email]> > To: "kea-users" <[hidden email]> > Sent: Friday, 6 October, 2017 15:54:57 > Subject: Re: [Kea-users] 1.3.0 beta not working with mysql > Hey Bill: > > Sure, rather than try to use git apply, you can just make the alteration > by editing the file with any text editor. You would then need to rerun > make and make install. > > 1. Edit this file: <wherever you unrolled kea tar > ball>src/lib/dhcpsrv/mysql_connection.cc > > Change line 175 from this: > > const char *wait_time = "SET SESSION wait_timeout = 30 * 86400"; > > to this: > > const char *wait_time = "SET SESSION wait_timeout = 214000"; > > Save it, then rerun make and make install. > > Thanks, > > Thomas > > On 10/6/17 9:06 AM, Bill Pye wrote: >> Hi Thomas >> >> Yes, I'll give that a go but I'm afraid you'll have to give me the steps to >> apply it. >> >> >> Regards >> >> >> Bill >> >> ----- Original Message ----- >>> From: "Thomas Markwalder" <[hidden email]> >>> To: "kea-users" <[hidden email]> >>> Sent: Friday, 6 October, 2017 14:00:36 >>> Subject: Re: [Kea-users] 1.3.0 beta not working with mysql >>> Hi Bill: >>> >>> I've attached a test patch if you're willing. Per MariaDB the max >>> value for --wait-timeout is 2147483, and we are exceeding that. I'm >>> wondering if our attempt to set it is failing silently. The patch I >>> sent you attempts to set it to a number well under their max but much >>> larger than their default. >>> >>> Thanks, >>> >>> Thomas >>> >>> >>> >>> >>> _______________________________________________ >>> 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 > > > _______________________________________________ > 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 |
Re: [Kea-users] 1.3.0 beta not working with mysql
|
|
Hi Bill:
Ok, thanks. I'm building out a Centos 7 VM with MariaDB. I personally have have tested 1.3 agains MySQL and Postgres. Not MariaDB though. I know the latter is "supposed to be binary replacement for MySQL" ... but sometimes reality is less than ideal ;). Can you tell me if there is any substantial amount of time elapsing between server startup and the first client attempt? Thanks Thomas On 10/6/17 10:57 AM, Bill Pye wrote: > Hi Thomas > > Done that and built it on a CentOS7 server, installed it and pointed the DB to a single MariaDB server with the same results: > > 2017-10-06 16:51:48.304 ERROR [kea-dhcp4.alloc-engine/2899] ALLOC_ENGINE_V4_ALLOC_ERROR [hwtype=1 00:0c:29:bc:bc:18], cid=[01:00:0c:29:bc:bc:18], tid=0xf8e3db07: error during attempt to allocate an IPv4 address: unable to bind parameters for <INSERT INTO lease4(address, hwaddr, client_id, valid_lifetime, expire, subnet_id, fqdn_fwd, fqdn_rev, hostname, state) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?)>, reason: (error code 0) > > Details off the build: > > kea-dhcp4 -V > 1.3.0-beta > tarball > linked with: > log4cplus 1.1.3 > OpenSSL 1.0.2k-fips 26 Jan 2017 > database: > MySQL backend 5.1, library 10.2.9 > PostgreSQL backend 3.1, library 90223 > Memfile backend 2.0 > > If there is anything else you want me to try then just shout. > > > Regards > > Bill > > ----- Original Message ----- >> From: "Thomas Markwalder" <[hidden email]> >> To: "kea-users" <[hidden email]> >> Sent: Friday, 6 October, 2017 15:54:57 >> Subject: Re: [Kea-users] 1.3.0 beta not working with mysql >> Hey Bill: >> >> Sure, rather than try to use git apply, you can just make the alteration >> by editing the file with any text editor. You would then need to rerun >> make and make install. >> >> 1. Edit this file: <wherever you unrolled kea tar >> ball>src/lib/dhcpsrv/mysql_connection.cc >> >> Change line 175 from this: >> >> const char *wait_time = "SET SESSION wait_timeout = 30 * 86400"; >> >> to this: >> >> const char *wait_time = "SET SESSION wait_timeout = 214000"; >> >> Save it, then rerun make and make install. >> >> Thanks, >> >> Thomas >> >> On 10/6/17 9:06 AM, Bill Pye wrote: >>> Hi Thomas >>> >>> Yes, I'll give that a go but I'm afraid you'll have to give me the steps to >>> apply it. >>> >>> >>> Regards >>> >>> >>> Bill >>> >>> ----- Original Message ----- >>>> From: "Thomas Markwalder" <[hidden email]> >>>> To: "kea-users" <[hidden email]> >>>> Sent: Friday, 6 October, 2017 14:00:36 >>>> Subject: Re: [Kea-users] 1.3.0 beta not working with mysql >>>> Hi Bill: >>>> >>>> I've attached a test patch if you're willing. Per MariaDB the max >>>> value for --wait-timeout is 2147483, and we are exceeding that. I'm >>>> wondering if our attempt to set it is failing silently. The patch I >>>> sent you attempts to set it to a number well under their max but much >>>> larger than their default. >>>> >>>> Thanks, >>>> >>>> Thomas >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> 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 >> >> _______________________________________________ >> 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 _______________________________________________ Kea-users mailing list [hidden email] https://lists.isc.org/mailman/listinfo/kea-users |
|
|
Hi Thomas
One glaring omission, I'm afraid. I don't use the standard kernel on CentOS but this one from ELrepo: 4.13.4-1.el7.elrepo.x86_64 The kea 1.2 version that I built was using the standard centos7 repository and therefore the kernel that came with it, it's only in the last few months I've moved to the newer kernel. I mentioned earlier that kea 1.1 from the epel repo works on this server with the current kernel that I'm using. The longest time between start kea and a client request is probably about ten minutes and just in case it matters, all the machines (apart from one workstation) are VMs either on ESXi or VMware Workstation. I've been doing these client tests with an openSUSE & a Win10 workstations on VMware workstation. Regards Bill ----- Original Message ----- > From: "Thomas Markwalder" <[hidden email]> > To: "kea-users" <[hidden email]> > Sent: Friday, 6 October, 2017 17:16:15 > Subject: Re: [Kea-users] 1.3.0 beta not working with mysql > Hi Bill: > > Ok, thanks. I'm building out a Centos 7 VM with MariaDB. I personally > have have tested 1.3 agains MySQL and Postgres. Not MariaDB though. I > know the latter is "supposed to be binary replacement for MySQL" ... but > sometimes reality is less than ideal ;). > > Can you tell me if there is any substantial amount of time elapsing > between server startup and the first client attempt? > > Thanks > > Thomas > > > On 10/6/17 10:57 AM, Bill Pye wrote: >> Hi Thomas >> >> Done that and built it on a CentOS7 server, installed it and pointed the DB to a >> single MariaDB server with the same results: >> >> 2017-10-06 16:51:48.304 ERROR [kea-dhcp4.alloc-engine/2899] >> ALLOC_ENGINE_V4_ALLOC_ERROR [hwtype=1 00:0c:29:bc:bc:18], >> cid=[01:00:0c:29:bc:bc:18], tid=0xf8e3db07: error during attempt to allocate an >> IPv4 address: unable to bind parameters for <INSERT INTO lease4(address, >> hwaddr, client_id, valid_lifetime, expire, subnet_id, fqdn_fwd, fqdn_rev, >> hostname, state) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?)>, reason: (error code >> 0) >> >> Details off the build: >> >> kea-dhcp4 -V >> 1.3.0-beta >> tarball >> linked with: >> log4cplus 1.1.3 >> OpenSSL 1.0.2k-fips 26 Jan 2017 >> database: >> MySQL backend 5.1, library 10.2.9 >> PostgreSQL backend 3.1, library 90223 >> Memfile backend 2.0 >> >> If there is anything else you want me to try then just shout. >> >> >> Regards >> >> Bill >> >> ----- Original Message ----- >>> From: "Thomas Markwalder" <[hidden email]> >>> To: "kea-users" <[hidden email]> >>> Sent: Friday, 6 October, 2017 15:54:57 >>> Subject: Re: [Kea-users] 1.3.0 beta not working with mysql >>> Hey Bill: >>> >>> Sure, rather than try to use git apply, you can just make the alteration >>> by editing the file with any text editor. You would then need to rerun >>> make and make install. >>> >>> 1. Edit this file: <wherever you unrolled kea tar >>> ball>src/lib/dhcpsrv/mysql_connection.cc >>> >>> Change line 175 from this: >>> >>> const char *wait_time = "SET SESSION wait_timeout = 30 * 86400"; >>> >>> to this: >>> >>> const char *wait_time = "SET SESSION wait_timeout = 214000"; >>> >>> Save it, then rerun make and make install. >>> >>> Thanks, >>> >>> Thomas >>> >>> On 10/6/17 9:06 AM, Bill Pye wrote: >>>> Hi Thomas >>>> >>>> Yes, I'll give that a go but I'm afraid you'll have to give me the steps to >>>> apply it. >>>> >>>> >>>> Regards >>>> >>>> >>>> Bill >>>> >>>> ----- Original Message ----- >>>>> From: "Thomas Markwalder" <[hidden email]> >>>>> To: "kea-users" <[hidden email]> >>>>> Sent: Friday, 6 October, 2017 14:00:36 >>>>> Subject: Re: [Kea-users] 1.3.0 beta not working with mysql >>>>> Hi Bill: >>>>> >>>>> I've attached a test patch if you're willing. Per MariaDB the max >>>>> value for --wait-timeout is 2147483, and we are exceeding that. I'm >>>>> wondering if our attempt to set it is failing silently. The patch I >>>>> sent you attempts to set it to a number well under their max but much >>>>> larger than their default. >>>>> >>>>> Thanks, >>>>> >>>>> Thomas >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>> >>> _______________________________________________ >>> 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 > > _______________________________________________ > 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 |
|
|
In reply to this post by Thomas Markwalder
Hi Thomas
An update on my 'problem' but let me start with a question - is there any maximum value for the "valid-lifetime" setting? I ask this because I've just noticed a slightly odd number set for that option and it was set as "604800", I can't imagine why I set it that high or if it was a typing error. I've set that to a more reasonable value of "86400" and restarted my kea 1.3 servers and pointed them to my Percona cluster, lo and behold they came up with no errors (all three of them). They're all sitting there responding to DHCP requests, to say I'm surprised is an understatement! I'll leave these running overnight and see what happens, is it worth upping the loglevel a bit? I currently have logging at "INFO" and a debug level of zero, which is the best for reasonably detailed info but doesn't flood the server? Regards Bill ----- Original Message ----- > From: "Thomas Markwalder" <[hidden email]> > To: "kea-users" <[hidden email]> > Sent: Friday, 6 October, 2017 17:16:15 > Subject: Re: [Kea-users] 1.3.0 beta not working with mysql > Hi Bill: > > Ok, thanks. I'm building out a Centos 7 VM with MariaDB. I personally > have have tested 1.3 agains MySQL and Postgres. Not MariaDB though. I > know the latter is "supposed to be binary replacement for MySQL" ... but > sometimes reality is less than ideal ;). > > Can you tell me if there is any substantial amount of time elapsing > between server startup and the first client attempt? > > Thanks > > Thomas > > > On 10/6/17 10:57 AM, Bill Pye wrote: Kea-users mailing list [hidden email] https://lists.isc.org/mailman/listinfo/kea-users |
Re: [Kea-users] 1.3.0 beta not working with mysql
|
|
It's stored as an unsigned integer, so in theory it's max is
|4294967295. Certainly much larger than 604800. For grins, I used that value on a machine running MySQL and it inserts leases just fine. Using the unsigned int max value, though blows up time calculations which manifests itself as this error: 2017-10-06 13:29:57.202 ERROR [kea-dhcp4.alloc-engine/1888] ALLOC_ENGINE_V4_ALLOC_ERROR [hwtype=1 08:00:27:99:72:be], cid=[no info], tid=0x489a9: error during attempt to allocate an IPv4 address: Could not create bind array from Lease4: 178.16.1.100, reason: Time value is too large: 5802278292 Clearly different from your whose reason is (error code 0). |On 10/6/17 12:37 PM, Bill Pye wrote:|| > Hi Thomas|| > > An update on my 'problem' but let me start with a question - is there any maximum value for the "valid-lifetime" setting? I ask this because I've just noticed a slightly odd number set for that option and it was set as "604800", I can't imagine why I set it that high or if it was a typing error. I've set that to a more reasonable value of "86400" and restarted my kea 1.3 servers and pointed them to my Percona cluster, lo and behold they came up with no errors (all three of them). They're all sitting there responding to DHCP requests, to say I'm surprised is an understatement! > > I'll leave these running overnight and see what happens, is it worth upping the loglevel a bit? I currently have logging at "INFO" and a debug level of zero, which is the best for reasonably detailed info but doesn't flood the server? > > > Regards > > > Bill > > ----- Original Message ----- >> From: "Thomas Markwalder" <[hidden email]> >> To: "kea-users" <[hidden email]> >> Sent: Friday, 6 October, 2017 17:16:15 >> Subject: Re: [Kea-users] 1.3.0 beta not working with mysql >> Hi Bill: >> >> Ok, thanks. I'm building out a Centos 7 VM with MariaDB. I personally >> have have tested 1.3 agains MySQL and Postgres. Not MariaDB though. I >> know the latter is "supposed to be binary replacement for MySQL" ... but >> sometimes reality is less than ideal ;). >> >> Can you tell me if there is any substantial amount of time elapsing >> between server startup and the first client attempt? >> >> Thanks >> >> Thomas >> >> >> On 10/6/17 10:57 AM, Bill Pye wrote: > _______________________________________________ > 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 |
Re: [Kea-users] 1.3.0 beta not working with mysql
|
|
Hi Bill:
Just following up with you. I was able to build out a Centos 7 VM with MariaDB. Kea builds fine, the unit tests all pass (which include pretty exhaustive testing of our supported backends). kea-dhcp4 comes and happily hands out leases with lifetimes of 604800 with no apparent issues. This was using the 1.3-beta code as is. I even verified that setting the wait_timeout to 30 * 86400 seems to work fine using the mysql command line client. I can't say why you saw what you did before. Doesn't make much sense. If you see it again let us know and we'll dig further. Regards, Thomas Markwalder ISC Software Engineering On 10/6/17 1:33 PM, Thomas Markwalder wrote: > It's stored as an unsigned integer, so in theory it's max is > |4294967295. Certainly much larger than 604800. For grins, I used that > value on a machine running MySQL and it inserts leases just fine. > > Using the unsigned int max value, though blows up time calculations > which manifests itself as this error: > > 2017-10-06 13:29:57.202 ERROR [kea-dhcp4.alloc-engine/1888] > ALLOC_ENGINE_V4_ALLOC_ERROR [hwtype=1 08:00:27:99:72:be], cid=[no info], > tid=0x489a9: error during attempt to allocate an IPv4 address: Could not > create bind array from Lease4: 178.16.1.100, reason: Time value is too > large: 5802278292 > > Clearly different from your whose reason is (error code 0). > > > |On 10/6/17 12:37 PM, Bill Pye wrote:|| >> Hi Thomas|| >> >> An update on my 'problem' but let me start with a question - is there any maximum value for the "valid-lifetime" setting? I ask this because I've just noticed a slightly odd number set for that option and it was set as "604800", I can't imagine why I set it that high or if it was a typing error. I've set that to a more reasonable value of "86400" and restarted my kea 1.3 servers and pointed them to my Percona cluster, lo and behold they came up with no errors (all three of them). They're all sitting there responding to DHCP requests, to say I'm surprised is an understatement! >> >> I'll leave these running overnight and see what happens, is it worth upping the loglevel a bit? I currently have logging at "INFO" and a debug level of zero, which is the best for reasonably detailed info but doesn't flood the server? >> >> >> Regards >> >> >> Bill >> >> ----- Original Message ----- >>> From: "Thomas Markwalder" <[hidden email]> >>> To: "kea-users" <[hidden email]> >>> Sent: Friday, 6 October, 2017 17:16:15 >>> Subject: Re: [Kea-users] 1.3.0 beta not working with mysql >>> Hi Bill: >>> >>> Ok, thanks. I'm building out a Centos 7 VM with MariaDB. I personally >>> have have tested 1.3 agains MySQL and Postgres. Not MariaDB though. I >>> know the latter is "supposed to be binary replacement for MySQL" ... but >>> sometimes reality is less than ideal ;). >>> >>> Can you tell me if there is any substantial amount of time elapsing >>> between server startup and the first client attempt? >>> >>> Thanks >>> >>> Thomas >>> >>> >>> On 10/6/17 10:57 AM, Bill Pye wrote: >> _______________________________________________ >> 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 _______________________________________________ Kea-users mailing list [hidden email] https://lists.isc.org/mailman/listinfo/kea-users |
|
|
Hi Thomas
Thanks for your follow-up. While I said that my installs of Percona & MariaDB were standard I did forget that I'd changed teh character set & collation to "urf8" & "utf8_general_ci" respectively. Just in case this had any effect (I know it shouldn't but...) I decided to install a new MariaDB totally basic with nothing else but the kea DB in it - this was on one of my current servers. I've spent the week-end trying to get something that made sense but not much luck, I'm afraid. Today I did some more tests on this single MariaDB server and basically came to the conclusion that the only version of kea that works using the db is kea-1.0. My last test a short while ago was with kea 1.3 built with the srpm provided by Rasmus Edgar, that didn't work and seemed to give the same error that I've mentioned before. I have a debug log file if that's of any use to you? Is there anything specific that I can do to get more information about this problem for you? Meanwhile, I could try with a more basic clean install of CentOS7/MariaDB and see if I get the same results as you. Regards Bill ----- Original Message ----- > From: "Thomas Markwalder" <[hidden email]> > To: "kea-users" <[hidden email]> > Sent: Monday, 9 October, 2017 14:29:37 > Subject: Re: [Kea-users] 1.3.0 beta not working with mysql > Hi Bill: > > Just following up with you. I was able to build out a Centos 7 VM with > MariaDB. Kea builds fine, the unit tests all pass (which include pretty > exhaustive testing of our supported backends). kea-dhcp4 comes and > happily hands out leases with lifetimes of 604800 with no apparent > issues. This was using the 1.3-beta code as is. I even verified that > setting the wait_timeout to 30 * 86400 seems to work fine using the > mysql command line client. > > I can't say why you saw what you did before. Doesn't make much sense. > If you see it again let us know and we'll dig further. > > Regards, > > Thomas Markwalder > ISC Software Engineering > > On 10/6/17 1:33 PM, Thomas Markwalder wrote: >> It's stored as an unsigned integer, so in theory it's max is >> |4294967295. Certainly much larger than 604800. For grins, I used that >> value on a machine running MySQL and it inserts leases just fine. >> >> Using the unsigned int max value, though blows up time calculations >> which manifests itself as this error: >> >> 2017-10-06 13:29:57.202 ERROR [kea-dhcp4.alloc-engine/1888] >> ALLOC_ENGINE_V4_ALLOC_ERROR [hwtype=1 08:00:27:99:72:be], cid=[no info], >> tid=0x489a9: error during attempt to allocate an IPv4 address: Could not >> create bind array from Lease4: 178.16.1.100, reason: Time value is too >> large: 5802278292 >> >> Clearly different from your whose reason is (error code 0). >> >> >> |On 10/6/17 12:37 PM, Bill Pye wrote:|| >>> Hi Thomas|| >>> >>> An update on my 'problem' but let me start with a question - is there any >>> maximum value for the "valid-lifetime" setting? I ask this because I've just >>> noticed a slightly odd number set for that option and it was set as "604800", I >>> can't imagine why I set it that high or if it was a typing error. I've set that >>> to a more reasonable value of "86400" and restarted my kea 1.3 servers and >>> pointed them to my Percona cluster, lo and behold they came up with no errors >>> (all three of them). They're all sitting there responding to DHCP requests, to >>> say I'm surprised is an understatement! >>> >>> I'll leave these running overnight and see what happens, is it worth upping the >>> loglevel a bit? I currently have logging at "INFO" and a debug level of zero, >>> which is the best for reasonably detailed info but doesn't flood the server? >>> >>> >>> Regards >>> >>> >>> Bill >>> >>> ----- Original Message ----- >>>> From: "Thomas Markwalder" <[hidden email]> >>>> To: "kea-users" <[hidden email]> >>>> Sent: Friday, 6 October, 2017 17:16:15 >>>> Subject: Re: [Kea-users] 1.3.0 beta not working with mysql >>>> Hi Bill: >>>> >>>> Ok, thanks. I'm building out a Centos 7 VM with MariaDB. I personally >>>> have have tested 1.3 agains MySQL and Postgres. Not MariaDB though. I >>>> know the latter is "supposed to be binary replacement for MySQL" ... but >>>> sometimes reality is less than ideal ;). >>>> >>>> Can you tell me if there is any substantial amount of time elapsing >>>> between server startup and the first client attempt? >>>> >>>> Thanks >>>> >>>> Thomas >>>> >>>> >>>> On 10/6/17 10:57 AM, Bill Pye wrote: >>> _______________________________________________ >>> 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 > > > _______________________________________________ > 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 |
|
|
In reply to this post by Thomas Markwalder
Hi Thomas
I've built a VM Centos& server, fully updated and just the MariaDB & epel repositories and fully updated. Unfortunately no luck, the same problem occurs. Is this, by any chance, a possible problem with my build of kea? Would you like me to send you my RPMs or perhaps you could send me yours? Regards Bill ----- Original Message ----- > From: "Thomas Markwalder" <[hidden email]> > To: "kea-users" <[hidden email]> > Sent: Monday, 9 October, 2017 14:29:37 > Subject: Re: [Kea-users] 1.3.0 beta not working with mysql > Hi Bill: > > Just following up with you. I was able to build out a Centos 7 VM with > MariaDB. Kea builds fine, the unit tests all pass (which include pretty > exhaustive testing of our supported backends). kea-dhcp4 comes and > happily hands out leases with lifetimes of 604800 with no apparent > issues. This was using the 1.3-beta code as is. I even verified that > setting the wait_timeout to 30 * 86400 seems to work fine using the > mysql command line client. > > I can't say why you saw what you did before. Doesn't make much sense. > If you see it again let us know and we'll dig further. > > Regards, > > Thomas Markwalder > ISC Software Engineering > Kea-users mailing list [hidden email] https://lists.isc.org/mailman/listinfo/kea-users |
Re: [Kea-users] 1.3.0 beta not working with mysql
|
|
Hi Bill:
I did not use RPMs, I installed from source. Please send us your RPMs. Where did you get these RPMs? Thanks, Thomas On 10/9/17 11:18 AM, Bill Pye wrote: > Hi Thomas > > I've built a VM Centos& server, fully updated and just the MariaDB & epel repositories and fully updated. Unfortunately no luck, the same problem occurs. Is this, by any chance, a possible problem with my build of kea? Would you like me to send you my RPMs or perhaps you could send me yours? > > > Regards > > > Bill > > ----- Original Message ----- >> From: "Thomas Markwalder" <[hidden email]> >> To: "kea-users" <[hidden email]> >> Sent: Monday, 9 October, 2017 14:29:37 >> Subject: Re: [Kea-users] 1.3.0 beta not working with mysql >> Hi Bill: >> >> Just following up with you. I was able to build out a Centos 7 VM with >> MariaDB. Kea builds fine, the unit tests all pass (which include pretty >> exhaustive testing of our supported backends). kea-dhcp4 comes and >> happily hands out leases with lifetimes of 604800 with no apparent >> issues. This was using the 1.3-beta code as is. I even verified that >> setting the wait_timeout to 30 * 86400 seems to work fine using the >> mysql command line client. >> >> I can't say why you saw what you did before. Doesn't make much sense. >> If you see it again let us know and we'll dig further. >> >> Regards, >> >> Thomas Markwalder >> ISC Software Engineering >> _______________________________________________ Kea-users mailing list [hidden email] https://lists.isc.org/mailman/listinfo/kea-users |
|
|
Hi Thomas
I initially built them myself from a Spec file that Rasmus provided and the downloaded source code, he later provided an srpm so I rebuilt it with that. The original list message (and links) is this: Hi Bill, You're welcome. Glad to help. Here's the srpms for 1.2.0 and 1.3.0-beta for those who are interested: 1.2.0: https://arch-ed.dk/srpms/kea-1.2.0/kea-1.2.0-1.el7.centos.src.rpm 1.3.0-beta: https://arch-ed.dk/srpms/kea-1.3.0-beta/kea-1.3.0-0.1.beta.el7.centos.src.rpm Br, Rasmus Where would you like me to send my rpm files, to the list? Regards Bill ----- Original Message ----- > From: "Thomas Markwalder" <[hidden email]> > To: "bill pye" <[hidden email]> > Cc: "kea-users" <[hidden email]> > Sent: Monday, 9 October, 2017 17:40:38 > Subject: Re: [Kea-users] 1.3.0 beta not working with mysql > Hi Bill: > > I did not use RPMs, I installed from source. Please send us your RPMs. > Where did you get these RPMs? > > Thanks, > > Thomas > > > On 10/9/17 11:18 AM, Bill Pye wrote: >> Hi Thomas >> >> I've built a VM Centos& server, fully updated and just the MariaDB & epel >> repositories and fully updated. Unfortunately no luck, the same problem occurs. >> Is this, by any chance, a possible problem with my build of kea? Would you like >> me to send you my RPMs or perhaps you could send me yours? >> >> >> Regards >> >> >> Bill >> >> ----- Original Message ----- >>> From: "Thomas Markwalder" <[hidden email]> >>> To: "kea-users" <[hidden email]> >>> Sent: Monday, 9 October, 2017 14:29:37 >>> Subject: Re: [Kea-users] 1.3.0 beta not working with mysql >>> Hi Bill: >>> >>> Just following up with you. I was able to build out a Centos 7 VM with >>> MariaDB. Kea builds fine, the unit tests all pass (which include pretty >>> exhaustive testing of our supported backends). kea-dhcp4 comes and >>> happily hands out leases with lifetimes of 604800 with no apparent >>> issues. This was using the 1.3-beta code as is. I even verified that >>> setting the wait_timeout to 30 * 86400 seems to work fine using the >>> mysql command line client. >>> >>> I can't say why you saw what you did before. Doesn't make much sense. >>> If you see it again let us know and we'll dig further. >>> >>> Regards, >>> >>> Thomas Markwalder >>> ISC Software Engineering Kea-users mailing list [hidden email] https://lists.isc.org/mailman/listinfo/kea-users |
Re: [Kea-users] 1.3.0 beta not working with mysql
|
|
Hi,
I just tested kea-1.3.0-beta kea-dhcp4 with my supplied srpm on CentOS 7.4 running mariadb 5.5.56 on the same host and using it as lease storage for dhcp4. It works. [root@rpmbuild-1 ~]# tail /var/log/kea-dhcp4.log 2017-10-09 20:19:00.802 INFO [kea-dhcp4.dhcp4/3870] DHCP4_STARTED Kea DHCPv4 server version 1.3.0-beta started 2017-10-09 20:19:27.429 INFO [kea-dhcp4.dhcp4/3870] DHCP4_SHUTDOWN server shutdown 2017-10-09 20:33:20.052 INFO [kea-dhcp4.dhcp4/1834] DHCP4_STARTED Kea DHCPv4 server version 1.3.0-beta started 2017-10-09 20:33:21.483 INFO [kea-dhcp4.leases/1834] DHCP4_LEASE_ADVERT [hwtype=1 08:00:27:f6:62:cb], cid=[ff:27:f6:62:cb:00:01:00:01:21:6e:7a:ad:08:00:27:f6:62:cb], tid=0xb90df951: lease 192.0.2.3 will be advertised 2017-10-09 20:33:21.490 INFO [kea-dhcp4.leases/1834] DHCP4_LEASE_ALLOC [hwtype=1 08:00:27:f6:62:cb], cid=[ff:27:f6:62:cb:00:01:00:01:21:6e:7a:ad:08:00:27:f6:62:cb], tid=0xb90df951: lease 192.0.2.3 has been allocated 2017-10-09 20:33:59.078 INFO [kea-dhcp4.leases/1834] DHCP4_LEASE_ADVERT [hwtype=1 08:00:27:f6:62:cb], cid=[ff:27:f6:62:cb:00:01:00:01:1e:59:e5:3c:08:00:27:f6:62:cb], tid=0xc09f4c43: lease 192.0.2.4 will be advertised 2017-10-09 20:33:59.080 INFO [kea-dhcp4.leases/1834] DHCP4_LEASE_ALLOC [hwtype=1 08:00:27:f6:62:cb], cid=[ff:27:f6:62:cb:00:01:00:01:1e:59:e5:3c:08:00:27:f6:62:cb], tid=0xc09f4c43: lease 192.0.2.4 has been allocated 2017-10-09 20:43:20.372 INFO [kea-dhcp4.dhcp4/1834] DHCP4_SHUTDOWN server shutdown MariaDB [kea_leases]> select * from lease4; +------------+--------+---------------------+----------------+---------------------+-----------+----------+----------+----------+-------+ | address | hwaddr | client_id | valid_lifetime | expire | subnet_id | fqdn_fwd | fqdn_rev | hostname | state | +------------+--------+---------------------+----------------+---------------------+-----------+----------+----------+----------+-------+ | 3221225987 | 'öbË | ÿ'öbË !n 'öbË | 3600 | 2017-10-09 21:33:21 | 1 | 0 | 0 | | 0 | | 3221225988 | 'öbË | ÿ'öbË Yå 'öbË | 3600 | 2017-10-09 21:33:59 | 1 | 0 | 0 | | 0 | +------------+--------+---------------------+----------------+---------------------+-----------+----------+----------+----------+-------+ 2 rows in set (0.00 sec) When creating the database tables I followed the guide here: http://kea.isc.org/docs/kea-guide.html#idp52513808 The kea.conf (which is the standard one adjusted and no comments) is pasted below: { "Dhcp4": { "interfaces-config": { "interfaces": [ "enp0s8" ] }, "control-socket": { "socket-type": "unix", "socket-name": "/tmp/kea-dhcp4-ctrl.sock" }, "lease-database": { "type": "mysql", "user": "kea_user", "password": "gaffel", "name": "kea_leases" }, "expired-leases-processing": { "reclaim-timer-wait-time": 10, "flush-reclaimed-timer-wait-time": 25, "hold-reclaimed-time": 3600, "max-reclaim-leases": 100, "max-reclaim-time": 250, "unwarned-reclaim-cycles": 5 }, "renew-timer": 900, "rebind-timer": 1800, "valid-lifetime": 3600, "option-data": [ { "name": "domain-name-servers", "data": "192.0.2.1, 192.0.2.2" }, { "code": 15, "data": "example.org" }, { "name": "domain-search", "data": "mydomain.example.com, example.com" }, { "name": "boot-file-name", "data": "EST5EDT4\\,M3.2.0/02:00\\,M11.1.0/02:00" }, { "name": "default-ip-ttl", "data": "0xf0" } ], "client-classes": [ { "name": "voip", "test": "substring(option[60].hex,0,6) == 'Aastra'", "next-server": "192.0.2.254", "server-hostname": "hal9000", "boot-file-name": "/dev/null" } ], "subnet4": [ { "subnet": "192.0.2.0/24", "pools": [ { "pool": "192.0.2.3 - 192.0.2.200" } ], "option-data": [ { "name": "routers", "data": "192.0.2.1" } ], "reservations": [ { "hw-address": "1a:1b:1c:1d:1e:1f", "ip-address": "192.0.2.201" }, { "client-id": "01:11:22:33:44:55:66", "ip-address": "192.0.2.202", "hostname": "special-snowflake" }, { "duid": "01:02:03:04:05", "ip-address": "192.0.2.203", "option-data": [ { "name": "domain-name-servers", "data": "10.1.1.202, 10.1.1.203" } ] }, { "client-id": "01:12:23:34:45:56:67", "ip-address": "192.0.2.204", "option-data": [ { "name": "vivso-suboptions", "data": "4491" }, { "name": "tftp-servers", "space": "vendor-4491", "data": "10.1.1.202, 10.1.1.203" } ] }, { "client-id": "01:0a:0b:0c:0d:0e:0f", "ip-address": "192.0.2.205", "next-server": "192.0.2.1", "server-hostname": "hal9000", "boot-file-name": "/dev/null" }, { "flex-id": "'s0mEVaLue'", "ip-address": "192.0.2.206" } ] } ] }, "Dhcp6": { "interfaces-config": { "interfaces": [ ] }, "control-socket": { "socket-type": "unix", "socket-name": "/tmp/kea-dhcp6-ctrl.sock" }, "lease-database": { "type": "memfile" }, "expired-leases-processing": { "reclaim-timer-wait-time": 10, "flush-reclaimed-timer-wait-time": 25, "hold-reclaimed-time": 3600, "max-reclaim-leases": 100, "max-reclaim-time": 250, "unwarned-reclaim-cycles": 5 }, "renew-timer": 1000, "rebind-timer": 2000, "preferred-lifetime": 3000, "valid-lifetime": 4000, "option-data": [ { "name": "dns-servers", "data": "2001:db8:2::45, 2001:db8:2::100" }, { "code": 12, "data": "2001:db8::1" }, { "name": "new-posix-timezone", "data": "EST5EDT4\\,M3.2.0/02:00\\,M11.1.0/02:00" }, { "name": "preference", "data": "0xf0" }, { "name": "bootfile-param", "data": "root=/dev/sda2, quiet, splash" } ], "subnet6": [ { "subnet": "2001:db8:1::/64", "pools": [ { "pool": "2001:db8:1::/80" } ], "pd-pools": [ { "prefix": "2001:db8:8::", "prefix-len": 56, "delegated-len": 64 } ], "option-data": [ { "name": "dns-servers", "data": "2001:db8:2::dead:beef, 2001:db8:2::cafe:babe" } ], "reservations": [ { "duid": "01:02:03:04:05:0A:0B:0C:0D:0E", "ip-addresses": [ "2001:db8:1::100" ] }, { "hw-address": "00:01:02:03:04:05", "ip-addresses": [ "2001:db8:1::101" ], "option-data": [ { "name": "dns-servers", "data": "3000:1::234" }, { "name": "nis-servers", "data": "3000:1::234" }], "client-classes": [ "special_snowflake", "office" ] }, { "duid": "01:02:03:04:05:06:07:08:09:0A", "ip-addresses": [ "2001:db8:1:cafe::1" ], "prefixes": [ "2001:db8:2:abcd::/64" ], "hostname": "foo.example.com", "option-data": [ { "name": "vendor-opts", "data": "4491" }, { "name": "tftp-servers", "space": "vendor-4491", "data": "3000:1::234" } ] }, { "flex-id": "'somevalue'", "ip-addresses": [ "2001:db8:1:cafe::2" ] } ] } ] }, "DhcpDdns": { "ip-address": "127.0.0.1", "port": 53001, "tsig-keys": [], "forward-ddns" : {}, "reverse-ddns" : {} }, "Control-agent": { "http-host": "127.0.0.1", "http-port": 8080, "control-sockets": { "dhcp4": { "socket-type": "unix", "socket-name": "/tmp/kea-dhcp4-ctrl.sock" }, "dhcp6": { "socket-type": "unix", "socket-name": "/tmp/kea-dhcp6-ctrl.sock" } }, "hooks-libraries": [ ] }, "Logging": { "loggers": [ { "name": "kea-dhcp4", "output_options": [ { "output": "/var/log/kea-dhcp4.log" } ], "severity": "INFO", "debuglevel": 0 }, { "name": "kea-dhcp6", "output_options": [ { "output": "/var/log/kea-dhcp6.log" } ], "severity": "INFO", "debuglevel": 0 }, { "name": "kea-dhcp-ddns", "output_options": [ { "output": "/var/log/kea-ddns.log" } ], "severity": "INFO", "debuglevel": 0 }, { "name": "kea-ctrl-agent", "output_options": [ { "output": "/var/log/kea-ctrl-agent.log" } ], "severity": "INFO", "debuglevel": 0 } ] } } Br, Rasmus Bill Pye skrev den 2017-10-09 18:19: > Hi Thomas > > I initially built them myself from a Spec file that Rasmus provided > and the downloaded source code, he later provided an srpm so I rebuilt > it with that. The original list message (and links) is this: > > Hi Bill, > > You're welcome. Glad to help. > > Here's the srpms for 1.2.0 and 1.3.0-beta for those who are interested: > > 1.2.0: > https://arch-ed.dk/srpms/kea-1.2.0/kea-1.2.0-1.el7.centos.src.rpm > > 1.3.0-beta: > https://arch-ed.dk/srpms/kea-1.3.0-beta/kea-1.3.0-0.1.beta.el7.centos.src.rpm > > Br, > > Rasmus > > Where would you like me to send my rpm files, to the list? > > > Regards > > > > Bill > ----- Original Message ----- >> From: "Thomas Markwalder" <[hidden email]> >> To: "bill pye" <[hidden email]> >> Cc: "kea-users" <[hidden email]> >> Sent: Monday, 9 October, 2017 17:40:38 >> Subject: Re: [Kea-users] 1.3.0 beta not working with mysql > >> Hi Bill: >> >> I did not use RPMs, I installed from source. Please send us your >> RPMs. >> Where did you get these RPMs? >> >> Thanks, >> >> Thomas >> >> >> On 10/9/17 11:18 AM, Bill Pye wrote: >>> Hi Thomas >>> >>> I've built a VM Centos& server, fully updated and just the MariaDB & >>> epel >>> repositories and fully updated. Unfortunately no luck, the same >>> problem occurs. >>> Is this, by any chance, a possible problem with my build of kea? >>> Would you like >>> me to send you my RPMs or perhaps you could send me yours? >>> >>> >>> Regards >>> >>> >>> Bill >>> >>> ----- Original Message ----- >>>> From: "Thomas Markwalder" <[hidden email]> >>>> To: "kea-users" <[hidden email]> >>>> Sent: Monday, 9 October, 2017 14:29:37 >>>> Subject: Re: [Kea-users] 1.3.0 beta not working with mysql >>>> Hi Bill: >>>> >>>> Just following up with you. I was able to build out a Centos 7 VM >>>> with >>>> MariaDB. Kea builds fine, the unit tests all pass (which include >>>> pretty >>>> exhaustive testing of our supported backends). kea-dhcp4 comes and >>>> happily hands out leases with lifetimes of 604800 with no apparent >>>> issues. This was using the 1.3-beta code as is. I even verified >>>> that >>>> setting the wait_timeout to 30 * 86400 seems to work fine using the >>>> mysql command line client. >>>> >>>> I can't say why you saw what you did before. Doesn't make much >>>> sense. >>>> If you see it again let us know and we'll dig further. >>>> >>>> Regards, >>>> >>>> Thomas Markwalder >>>> ISC Software Engineering > _______________________________________________ > 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 |
|
|
Hi Rasmus
Thanks for that info, I'm currently using MariaDB 10.2.9 and I'll try again tomorrow with the standard version of mariadb the same as yours and see how I get on with that. Regards Bill ----- Original Message ----- > From: "Rasmus Edgar" <[hidden email]> > To: "bill pye" <[hidden email]> > Cc: "kea-users" <[hidden email]> > Sent: Monday, 9 October, 2017 20:54:47 > Subject: Re: [Kea-users] 1.3.0 beta not working with mysql > Hi, > > I just tested kea-1.3.0-beta kea-dhcp4 with my supplied srpm on CentOS > 7.4 running mariadb 5.5.56 on the same host and using it as lease > storage for dhcp4. > > It works. > > [root@rpmbuild-1 ~]# tail /var/log/kea-dhcp4.log > 2017-10-09 20:19:00.802 INFO [kea-dhcp4.dhcp4/3870] DHCP4_STARTED Kea > DHCPv4 server version 1.3.0-beta started > 2017-10-09 20:19:27.429 INFO [kea-dhcp4.dhcp4/3870] DHCP4_SHUTDOWN > server shutdown > 2017-10-09 20:33:20.052 INFO [kea-dhcp4.dhcp4/1834] DHCP4_STARTED Kea > DHCPv4 server version 1.3.0-beta started > 2017-10-09 20:33:21.483 INFO [kea-dhcp4.leases/1834] DHCP4_LEASE_ADVERT > [hwtype=1 08:00:27:f6:62:cb], > cid=[ff:27:f6:62:cb:00:01:00:01:21:6e:7a:ad:08:00:27:f6:62:cb], > tid=0xb90df951: lease 192.0.2.3 will be advertised > 2017-10-09 20:33:21.490 INFO [kea-dhcp4.leases/1834] DHCP4_LEASE_ALLOC > [hwtype=1 08:00:27:f6:62:cb], > cid=[ff:27:f6:62:cb:00:01:00:01:21:6e:7a:ad:08:00:27:f6:62:cb], > tid=0xb90df951: lease 192.0.2.3 has been allocated > 2017-10-09 20:33:59.078 INFO [kea-dhcp4.leases/1834] DHCP4_LEASE_ADVERT > [hwtype=1 08:00:27:f6:62:cb], > cid=[ff:27:f6:62:cb:00:01:00:01:1e:59:e5:3c:08:00:27:f6:62:cb], > tid=0xc09f4c43: lease 192.0.2.4 will be advertised > 2017-10-09 20:33:59.080 INFO [kea-dhcp4.leases/1834] DHCP4_LEASE_ALLOC > [hwtype=1 08:00:27:f6:62:cb], > cid=[ff:27:f6:62:cb:00:01:00:01:1e:59:e5:3c:08:00:27:f6:62:cb], > tid=0xc09f4c43: lease 192.0.2.4 has been allocated > 2017-10-09 20:43:20.372 INFO [kea-dhcp4.dhcp4/1834] DHCP4_SHUTDOWN > server shutdown > > MariaDB [kea_leases]> select * from lease4; > +------------+--------+---------------------+----------------+---------------------+-----------+----------+----------+----------+-------+ >| address | hwaddr | client_id | valid_lifetime | expire > | subnet_id | fqdn_fwd | fqdn_rev | hostname | state | > +------------+--------+---------------------+----------------+---------------------+-----------+----------+----------+----------+-------+ >| 3221225987 | 'öbË | ÿ'öbË !n 'öbË | 3600 | > 2017-10-09 21:33:21 | 1 | 0 | 0 | | 0 >| >| 3221225988 | 'öbË | ÿ'öbË Yå 'öbË | 3600 | > 2017-10-09 21:33:59 | 1 | 0 | 0 | | 0 >| > +------------+--------+---------------------+----------------+---------------------+-----------+----------+----------+----------+-------+ > 2 rows in set (0.00 sec) > > When creating the database tables I followed the guide here: > http://kea.isc.org/docs/kea-guide.html#idp52513808 > > The kea.conf (which is the standard one adjusted and no comments) is > pasted below: > { > > "Dhcp4": { > "interfaces-config": { > "interfaces": [ "enp0s8" ] > > }, > > "control-socket": { > "socket-type": "unix", > "socket-name": "/tmp/kea-dhcp4-ctrl.sock" > }, > > "lease-database": { > "type": "mysql", > "user": "kea_user", > "password": "gaffel", > "name": "kea_leases" > }, > > > "expired-leases-processing": { > "reclaim-timer-wait-time": 10, > "flush-reclaimed-timer-wait-time": 25, > "hold-reclaimed-time": 3600, > "max-reclaim-leases": 100, > "max-reclaim-time": 250, > "unwarned-reclaim-cycles": 5 > }, > > "renew-timer": 900, > "rebind-timer": 1800, > "valid-lifetime": 3600, > > > "option-data": [ > { > "name": "domain-name-servers", > "data": "192.0.2.1, 192.0.2.2" > }, > > { > "code": 15, > "data": "example.org" > }, > > { > "name": "domain-search", > "data": "mydomain.example.com, example.com" > }, > > > { > "name": "boot-file-name", > "data": "EST5EDT4\\,M3.2.0/02:00\\,M11.1.0/02:00" > }, > > { > "name": "default-ip-ttl", > "data": "0xf0" > } > > ], > > > "client-classes": [ > { > "name": "voip", > > "test": "substring(option[60].hex,0,6) == 'Aastra'", > > "next-server": "192.0.2.254", > "server-hostname": "hal9000", > "boot-file-name": "/dev/null" > > } > ], > > > "subnet4": [ > { > "subnet": "192.0.2.0/24", > > "pools": [ { "pool": "192.0.2.3 - 192.0.2.200" } ], > > "option-data": [ > { > "name": "routers", > "data": "192.0.2.1" > } > ], > > "reservations": [ > > { > "hw-address": "1a:1b:1c:1d:1e:1f", > "ip-address": "192.0.2.201" > }, > > { > "client-id": "01:11:22:33:44:55:66", > "ip-address": "192.0.2.202", > "hostname": "special-snowflake" > }, > > { > "duid": "01:02:03:04:05", > "ip-address": "192.0.2.203", > "option-data": [ { > "name": "domain-name-servers", > "data": "10.1.1.202, 10.1.1.203" > } ] > }, > > { > "client-id": "01:12:23:34:45:56:67", > "ip-address": "192.0.2.204", > "option-data": [ > { > "name": "vivso-suboptions", > "data": "4491" > }, > { > "name": "tftp-servers", > "space": "vendor-4491", > "data": "10.1.1.202, 10.1.1.203" > } > ] > }, > { > "client-id": "01:0a:0b:0c:0d:0e:0f", > "ip-address": "192.0.2.205", > "next-server": "192.0.2.1", > "server-hostname": "hal9000", > "boot-file-name": "/dev/null" > }, > { > "flex-id": "'s0mEVaLue'", > "ip-address": "192.0.2.206" > } > ] > } > ] > > }, > > "Dhcp6": { > "interfaces-config": { > "interfaces": [ ] > }, > > "control-socket": { > "socket-type": "unix", > "socket-name": "/tmp/kea-dhcp6-ctrl.sock" > }, > > "lease-database": { > "type": "memfile" > }, > > > "expired-leases-processing": { > "reclaim-timer-wait-time": 10, > "flush-reclaimed-timer-wait-time": 25, > "hold-reclaimed-time": 3600, > "max-reclaim-leases": 100, > "max-reclaim-time": 250, > "unwarned-reclaim-cycles": 5 > }, > > "renew-timer": 1000, > "rebind-timer": 2000, > "preferred-lifetime": 3000, > "valid-lifetime": 4000, > > "option-data": [ > { > "name": "dns-servers", > "data": "2001:db8:2::45, 2001:db8:2::100" > }, > > { > "code": 12, > "data": "2001:db8::1" > }, > > > { > "name": "new-posix-timezone", > "data": "EST5EDT4\\,M3.2.0/02:00\\,M11.1.0/02:00" > }, > > { > "name": "preference", > "data": "0xf0" > }, > > { > "name": "bootfile-param", > "data": "root=/dev/sda2, quiet, splash" > } > ], > > "subnet6": [ > { > "subnet": "2001:db8:1::/64", > > "pools": [ { "pool": "2001:db8:1::/80" } ], > > "pd-pools": [ > { > "prefix": "2001:db8:8::", > "prefix-len": 56, > "delegated-len": 64 > > } > ], > "option-data": [ > { > "name": "dns-servers", > "data": "2001:db8:2::dead:beef, > 2001:db8:2::cafe:babe" > } > ], > > "reservations": [ > { > "duid": "01:02:03:04:05:0A:0B:0C:0D:0E", > "ip-addresses": [ "2001:db8:1::100" ] > }, > > { > "hw-address": "00:01:02:03:04:05", > "ip-addresses": [ "2001:db8:1::101" ], > "option-data": [ > { > "name": "dns-servers", > "data": "3000:1::234" > }, > { > "name": "nis-servers", > "data": "3000:1::234" > }], > > "client-classes": [ "special_snowflake", "office" ] > }, > > { > "duid": "01:02:03:04:05:06:07:08:09:0A", > "ip-addresses": [ "2001:db8:1:cafe::1" ], > "prefixes": [ "2001:db8:2:abcd::/64" ], > "hostname": "foo.example.com", > "option-data": [ > { > "name": "vendor-opts", > "data": "4491" > }, > { > "name": "tftp-servers", > "space": "vendor-4491", > "data": "3000:1::234" > } > ] > }, > > > { > "flex-id": "'somevalue'", > "ip-addresses": [ "2001:db8:1:cafe::2" ] > } > ] > } > ] > > > > > }, > > "DhcpDdns": > { > "ip-address": "127.0.0.1", > "port": 53001, > "tsig-keys": [], > "forward-ddns" : {}, > "reverse-ddns" : {} > }, > > "Control-agent": { > "http-host": "127.0.0.1", > "http-port": 8080, > > "control-sockets": { > "dhcp4": { > "socket-type": "unix", > "socket-name": "/tmp/kea-dhcp4-ctrl.sock" > }, > "dhcp6": { > "socket-type": "unix", > "socket-name": "/tmp/kea-dhcp6-ctrl.sock" > } > }, > > "hooks-libraries": [ > ] > }, > > "Logging": > { > "loggers": [ > { > "name": "kea-dhcp4", > "output_options": [ > { > "output": "/var/log/kea-dhcp4.log" > > > > } > ], > "severity": "INFO", > > "debuglevel": 0 > }, > { > "name": "kea-dhcp6", > "output_options": [ > { > "output": "/var/log/kea-dhcp6.log" > } > ], > "severity": "INFO", > "debuglevel": 0 > }, > { > "name": "kea-dhcp-ddns", > "output_options": [ > { > "output": "/var/log/kea-ddns.log" > } > ], > "severity": "INFO", > "debuglevel": 0 > }, > { > "name": "kea-ctrl-agent", > "output_options": [ > { > "output": "/var/log/kea-ctrl-agent.log" > } > ], > "severity": "INFO", > "debuglevel": 0 > } > ] > } > } > > Br, > Rasmus > > Bill Pye skrev den 2017-10-09 18:19: >> Hi Thomas >> >> I initially built them myself from a Spec file that Rasmus provided >> and the downloaded source code, he later provided an srpm so I rebuilt >> it with that. The original list message (and links) is this: >> >> Hi Bill, >> >> You're welcome. Glad to help. >> >> Here's the srpms for 1.2.0 and 1.3.0-beta for those who are interested: >> >> 1.2.0: >> https://arch-ed.dk/srpms/kea-1.2.0/kea-1.2.0-1.el7.centos.src.rpm >> >> 1.3.0-beta: >> https://arch-ed.dk/srpms/kea-1.3.0-beta/kea-1.3.0-0.1.beta.el7.centos.src.rpm >> >> Br, >> >> Rasmus >> >> Where would you like me to send my rpm files, to the list? >> >> >> Regards >> >> >> >> Bill >> ----- Original Message ----- >>> From: "Thomas Markwalder" <[hidden email]> >>> To: "bill pye" <[hidden email]> >>> Cc: "kea-users" <[hidden email]> >>> Sent: Monday, 9 October, 2017 17:40:38 >>> Subject: Re: [Kea-users] 1.3.0 beta not working with mysql >> >>> Hi Bill: >>> >>> I did not use RPMs, I installed from source. Please send us your >>> RPMs. >>> Where did you get these RPMs? >>> >>> Thanks, >>> >>> Thomas >>> >>> >>> On 10/9/17 11:18 AM, Bill Pye wrote: >>>> Hi Thomas >>>> >>>> I've built a VM Centos& server, fully updated and just the MariaDB & >>>> epel >>>> repositories and fully updated. Unfortunately no luck, the same >>>> problem occurs. >>>> Is this, by any chance, a possible problem with my build of kea? >>>> Would you like >>>> me to send you my RPMs or perhaps you could send me yours? >>>> >>>> >>>> Regards >>>> >>>> >>>> Bill >>>> >>>> ----- Original Message ----- >>>>> From: "Thomas Markwalder" <[hidden email]> >>>>> To: "kea-users" <[hidden email]> >>>>> Sent: Monday, 9 October, 2017 14:29:37 >>>>> Subject: Re: [Kea-users] 1.3.0 beta not working with mysql >>>>> Hi Bill: >>>>> >>>>> Just following up with you. I was able to build out a Centos 7 VM >>>>> with >>>>> MariaDB. Kea builds fine, the unit tests all pass (which include >>>>> pretty >>>>> exhaustive testing of our supported backends). kea-dhcp4 comes and >>>>> happily hands out leases with lifetimes of 604800 with no apparent >>>>> issues. This was using the 1.3-beta code as is. I even verified >>>>> that >>>>> setting the wait_timeout to 30 * 86400 seems to work fine using the >>>>> mysql command line client. >>>>> >>>>> I can't say why you saw what you did before. Doesn't make much >>>>> sense. >>>>> If you see it again let us know and we'll dig further. >>>>> >>>>> Regards, >>>>> >>>>> Thomas Markwalder >>>>> ISC Software Engineering >> _______________________________________________ >> 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 |
|
|
In reply to this post by Rasmus Edgar
Hi Rasmus & Thomas
I think we can put this problem down to user error although I really don't know what's caused it. I have a centos7 dedicated to just building software, I used that to build kea and although it built with apparently no errors and I couldn't see anything in the log file it would never run against a clean install of percona or mariadb no matter which version I used. Eventually I came to the conclusion that there was a problem with my build environment so I installed mock and built kea again in that environment- it built fine and after install it worked against all the versions of percona & mariadb that I had installed. I've done a few limited tests against Mariadb 10.2.29, 5.5.56 and my Percona Cluster - all without problems and creating correct records in the lease table. I also use Proxysql for HA against my percona cluster and the only problem with kea is trying to use the proxsql instance but that's only a minor inconvenience for now. I'd like to thank everyone that's helped me with spec files, srpms and your advice and details of kea config and installs. :) Regards Bill ----- Original Message ----- > From: "Rasmus Edgar" <[hidden email]> > To: "bill pye" <[hidden email]> > Cc: "kea-users" <[hidden email]> > Sent: Monday, 9 October, 2017 20:54:47 > Subject: Re: [Kea-users] 1.3.0 beta not working with mysql > Hi, > > I just tested kea-1.3.0-beta kea-dhcp4 with my supplied srpm on CentOS > 7.4 running mariadb 5.5.56 on the same host and using it as lease > storage for dhcp4. > > It works. > > [root@rpmbuild-1 ~]# tail /var/log/kea-dhcp4.log > 2017-10-09 20:19:00.802 INFO [kea-dhcp4.dhcp4/3870] DHCP4_STARTED Kea > DHCPv4 server version 1.3.0-beta started > 2017-10-09 20:19:27.429 INFO [kea-dhcp4.dhcp4/3870] DHCP4_SHUTDOWN > server shutdown > 2017-10-09 20:33:20.052 INFO [kea-dhcp4.dhcp4/1834] DHCP4_STARTED Kea > DHCPv4 server version 1.3.0-beta started > 2017-10-09 20:33:21.483 INFO [kea-dhcp4.leases/1834] DHCP4_LEASE_ADVERT > [hwtype=1 08:00:27:f6:62:cb], > cid=[ff:27:f6:62:cb:00:01:00:01:21:6e:7a:ad:08:00:27:f6:62:cb], > tid=0xb90df951: lease 192.0.2.3 will be advertised > 2017-10-09 20:33:21.490 INFO [kea-dhcp4.leases/1834] DHCP4_LEASE_ALLOC > [hwtype=1 08:00:27:f6:62:cb], > cid=[ff:27:f6:62:cb:00:01:00:01:21:6e:7a:ad:08:00:27:f6:62:cb], > tid=0xb90df951: lease 192.0.2.3 has been allocated > 2017-10-09 20:33:59.078 INFO [kea-dhcp4.leases/1834] DHCP4_LEASE_ADVERT > [hwtype=1 08:00:27:f6:62:cb], > cid=[ff:27:f6:62:cb:00:01:00:01:1e:59:e5:3c:08:00:27:f6:62:cb], > tid=0xc09f4c43: lease 192.0.2.4 will be advertised > 2017-10-09 20:33:59.080 INFO [kea-dhcp4.leases/1834] DHCP4_LEASE_ALLOC > [hwtype=1 08:00:27:f6:62:cb], > cid=[ff:27:f6:62:cb:00:01:00:01:1e:59:e5:3c:08:00:27:f6:62:cb], > tid=0xc09f4c43: lease 192.0.2.4 has been allocated > 2017-10-09 20:43:20.372 INFO [kea-dhcp4.dhcp4/1834] DHCP4_SHUTDOWN > server shutdown > > MariaDB [kea_leases]> select * from lease4; > +------------+--------+---------------------+----------------+---------------------+-----------+----------+----------+----------+-------+ >| address | hwaddr | client_id | valid_lifetime | expire > | subnet_id | fqdn_fwd | fqdn_rev | hostname | state | > +------------+--------+---------------------+----------------+---------------------+-----------+----------+----------+----------+-------+ >| 3221225987 | 'öbË | ÿ'öbË !n 'öbË | 3600 | > 2017-10-09 21:33:21 | 1 | 0 | 0 | | 0 >| >| 3221225988 | 'öbË | ÿ'öbË Yå 'öbË | 3600 | > 2017-10-09 21:33:59 | 1 | 0 | 0 | | 0 >| > +------------+--------+---------------------+----------------+---------------------+-----------+----------+----------+----------+-------+ > 2 rows in set (0.00 sec) > > When creating the database tables I followed the guide here: > http://kea.isc.org/docs/kea-guide.html#idp52513808 > > The kea.conf (which is the standard one adjusted and no comments) is > pasted below: > { > > "Dhcp4": { > "interfaces-config": { > "interfaces": [ "enp0s8" ] > > }, > > "control-socket": { > "socket-type": "unix", > "socket-name": "/tmp/kea-dhcp4-ctrl.sock" > }, > > "lease-database": { > "type": "mysql", > "user": "kea_user", > "password": "gaffel", > "name": "kea_leases" > }, > > > "expired-leases-processing": { > "reclaim-timer-wait-time": 10, > "flush-reclaimed-timer-wait-time": 25, > "hold-reclaimed-time": 3600, > "max-reclaim-leases": 100, > "max-reclaim-time": 250, > "unwarned-reclaim-cycles": 5 > }, > > "renew-timer": 900, > "rebind-timer": 1800, > "valid-lifetime": 3600, > > > "option-data": [ > { > "name": "domain-name-servers", > "data": "192.0.2.1, 192.0.2.2" > }, > > { > "code": 15, > "data": "example.org" > }, > > { > "name": "domain-search", > "data": "mydomain.example.com, example.com" > }, > > > { > "name": "boot-file-name", > "data": "EST5EDT4\\,M3.2.0/02:00\\,M11.1.0/02:00" > }, > > { > "name": "default-ip-ttl", > "data": "0xf0" > } > > ], > > > "client-classes": [ > { > "name": "voip", > > "test": "substring(option[60].hex,0,6) == 'Aastra'", > > "next-server": "192.0.2.254", > "server-hostname": "hal9000", > "boot-file-name": "/dev/null" > > } > ], > > > "subnet4": [ > { > "subnet": "192.0.2.0/24", > > "pools": [ { "pool": "192.0.2.3 - 192.0.2.200" } ], > > "option-data": [ > { > "name": "routers", > "data": "192.0.2.1" > } > ], > > "reservations": [ > > { > "hw-address": "1a:1b:1c:1d:1e:1f", > "ip-address": "192.0.2.201" > }, > > { > "client-id": "01:11:22:33:44:55:66", > "ip-address": "192.0.2.202", > "hostname": "special-snowflake" > }, > > { > "duid": "01:02:03:04:05", > "ip-address": "192.0.2.203", > "option-data": [ { > "name": "domain-name-servers", > "data": "10.1.1.202, 10.1.1.203" > } ] > }, > > { > "client-id": "01:12:23:34:45:56:67", > "ip-address": "192.0.2.204", > "option-data": [ > { > "name": "vivso-suboptions", > "data": "4491" > }, > { > "name": "tftp-servers", > "space": "vendor-4491", > "data": "10.1.1.202, 10.1.1.203" > } > ] > }, > { > "client-id": "01:0a:0b:0c:0d:0e:0f", > "ip-address": "192.0.2.205", > "next-server": "192.0.2.1", > "server-hostname": "hal9000", > "boot-file-name": "/dev/null" > }, > { > "flex-id": "'s0mEVaLue'", > "ip-address": "192.0.2.206" > } > ] > } > ] > > }, > > "Dhcp6": { > "interfaces-config": { > "interfaces": [ ] > }, > > "control-socket": { > "socket-type": "unix", > "socket-name": "/tmp/kea-dhcp6-ctrl.sock" > }, > > "lease-database": { > "type": "memfile" > }, > > > "expired-leases-processing": { > "reclaim-timer-wait-time": 10, > "flush-reclaimed-timer-wait-time": 25, > "hold-reclaimed-time": 3600, > "max-reclaim-leases": 100, > "max-reclaim-time": 250, > "unwarned-reclaim-cycles": 5 > }, > > "renew-timer": 1000, > "rebind-timer": 2000, > "preferred-lifetime": 3000, > "valid-lifetime": 4000, > > "option-data": [ > { > "name": "dns-servers", > "data": "2001:db8:2::45, 2001:db8:2::100" > }, > > { > "code": 12, > "data": "2001:db8::1" > }, > > > { > "name": "new-posix-timezone", > "data": "EST5EDT4\\,M3.2.0/02:00\\,M11.1.0/02:00" > }, > > { > "name": "preference", > "data": "0xf0" > }, > > { > "name": "bootfile-param", > "data": "root=/dev/sda2, quiet, splash" > } > ], > > "subnet6": [ > { > "subnet": "2001:db8:1::/64", > > "pools": [ { "pool": "2001:db8:1::/80" } ], > > "pd-pools": [ > { > "prefix": "2001:db8:8::", > "prefix-len": 56, > "delegated-len": 64 > > } > ], > "option-data": [ > { > "name": "dns-servers", > "data": "2001:db8:2::dead:beef, > 2001:db8:2::cafe:babe" > } > ], > > "reservations": [ > { > "duid": "01:02:03:04:05:0A:0B:0C:0D:0E", > "ip-addresses": [ "2001:db8:1::100" ] > }, > > { > "hw-address": "00:01:02:03:04:05", > "ip-addresses": [ "2001:db8:1::101" ], > "option-data": [ > { > "name": "dns-servers", > "data": "3000:1::234" > }, > { > "name": "nis-servers", > "data": "3000:1::234" > }], > > "client-classes": [ "special_snowflake", "office" ] > }, > > { > "duid": "01:02:03:04:05:06:07:08:09:0A", > "ip-addresses": [ "2001:db8:1:cafe::1" ], > "prefixes": [ "2001:db8:2:abcd::/64" ], > "hostname": "foo.example.com", > "option-data": [ > { > "name": "vendor-opts", > "data": "4491" > }, > { > "name": "tftp-servers", > "space": "vendor-4491", > "data": "3000:1::234" > } > ] > }, > > > { > "flex-id": "'somevalue'", > "ip-addresses": [ "2001:db8:1:cafe::2" ] > } > ] > } > ] > > > > > }, > > "DhcpDdns": > { > "ip-address": "127.0.0.1", > "port": 53001, > "tsig-keys": [], > "forward-ddns" : {}, > "reverse-ddns" : {} > }, > > "Control-agent": { > "http-host": "127.0.0.1", > "http-port": 8080, > > "control-sockets": { > "dhcp4": { > "socket-type": "unix", > "socket-name": "/tmp/kea-dhcp4-ctrl.sock" > }, > "dhcp6": { > "socket-type": "unix", > "socket-name": "/tmp/kea-dhcp6-ctrl.sock" > } > }, > > "hooks-libraries": [ > ] > }, > > "Logging": > { > "loggers": [ > { > "name": "kea-dhcp4", > "output_options": [ > { > "output": "/var/log/kea-dhcp4.log" > > > > } > ], > "severity": "INFO", > > "debuglevel": 0 > }, > { > "name": "kea-dhcp6", > "output_options": [ > { > "output": "/var/log/kea-dhcp6.log" > } > ], > "severity": "INFO", > "debuglevel": 0 > }, > { > "name": "kea-dhcp-ddns", > "output_options": [ > { > "output": "/var/log/kea-ddns.log" > } > ], > "severity": "INFO", > "debuglevel": 0 > }, > { > "name": "kea-ctrl-agent", > "output_options": [ > { > "output": "/var/log/kea-ctrl-agent.log" > } > ], > "severity": "INFO", > "debuglevel": 0 > } > ] > } > } > > Br, > Rasmus > > Bill Pye skrev den 2017-10-09 18:19: >> Hi Thomas >> >> I initially built them myself from a Spec file that Rasmus provided >> and the downloaded source code, he later provided an srpm so I rebuilt >> it with that. The original list message (and links) is this: >> >> Hi Bill, >> >> You're welcome. Glad to help. >> >> Here's the srpms for 1.2.0 and 1.3.0-beta for those who are interested: >> >> 1.2.0: >> https://arch-ed.dk/srpms/kea-1.2.0/kea-1.2.0-1.el7.centos.src.rpm >> >> 1.3.0-beta: >> https://arch-ed.dk/srpms/kea-1.3.0-beta/kea-1.3.0-0.1.beta.el7.centos.src.rpm >> >> Br, >> >> Rasmus >> >> Where would you like me to send my rpm files, to the list? >> >> >> Regards >> >> >> >> Bill >> ----- Original Message ----- >>> From: "Thomas Markwalder" <[hidden email]> >>> To: "bill pye" <[hidden email]> >>> Cc: "kea-users" <[hidden email]> >>> Sent: Monday, 9 October, 2017 17:40:38 >>> Subject: Re: [Kea-users] 1.3.0 beta not working with mysql >> >>> Hi Bill: >>> >>> I did not use RPMs, I installed from source. Please send us your >>> RPMs. >>> Where did you get these RPMs? >>> >>> Thanks, >>> >>> Thomas >>> >>> >>> On 10/9/17 11:18 AM, Bill Pye wrote: >>>> Hi Thomas >>>> >>>> I've built a VM Centos& server, fully updated and just the MariaDB & >>>> epel >>>> repositories and fully updated. Unfortunately no luck, the same >>>> problem occurs. >>>> Is this, by any chance, a possible problem with my build of kea? >>>> Would you like >>>> me to send you my RPMs or perhaps you could send me yours? >>>> >>>> >>>> Regards >>>> >>>> >>>> Bill >>>> >>>> ----- Original Message ----- >>>>> From: "Thomas Markwalder" <[hidden email]> >>>>> To: "kea-users" <[hidden email]> >>>>> Sent: Monday, 9 October, 2017 14:29:37 >>>>> Subject: Re: [Kea-users] 1.3.0 beta not working with mysql >>>>> Hi Bill: >>>>> >>>>> Just following up with you. I was able to build out a Centos 7 VM >>>>> with >>>>> MariaDB. Kea builds fine, the unit tests all pass (which include >>>>> pretty >>>>> exhaustive testing of our supported backends). kea-dhcp4 comes and >>>>> happily hands out leases with lifetimes of 604800 with no apparent >>>>> issues. This was using the 1.3-beta code as is. I even verified >>>>> that >>>>> setting the wait_timeout to 30 * 86400 seems to work fine using the >>>>> mysql command line client. >>>>> >>>>> I can't say why you saw what you did before. Doesn't make much >>>>> sense. >>>>> If you see it again let us know and we'll dig further. >>>>> >>>>> Regards, >>>>> >>>>> Thomas Markwalder >>>>> ISC Software Engineering >> _______________________________________________ >> 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 |
«
Return to Kea Users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |