Package version on debian is still 1.1.0 on all branches. I sent an email to the maintainer as 1.3.0 is the recommended release and 1.1.0 is some kind of "please do not use this anymore"-release.
PS: I am on MariaDB 10.2 on both server and client. This might be the problem. I did not fix the problem yet as all leases are static. I will look into this the coming weeks. Kind regards Kevin 2018-03-19 14:26 GMT+01:00 Jason Guy <[email protected]>: > Hi Kevin, > > What version of mysql are you using? I have no problems with mysql 5.7 > (client and server). Also, have you initialized the database? > > Finally, I assume you are using version 1.1 because that it the only > version available on Debian Apt... I am still trying to have the maintainer > take more of my patches, and push the 1.3 packages to the testing repo, but > it is not going well. If anyone knows the maintainer for this package, or > has any advice about how to get more traction with the debian maintainer, I > would be grateful. I have done a lot of work to patch the 1.1 package to > become the 1.3 package, and I am using in my testing. But I would like to > make this available to all. :) > > Cheers, > Jason > > > On Mon, Mar 19, 2018 at 9:22 AM, Thomas Markwalder <[email protected]> wrote: > >> Hello Kevin: >> >> Kea is now up to version 1.3.0 with many new features added since 1.1.0 >> so you may wish to consider upgrading. However, Kea 1.1.0 should function >> using MySQL for lease storage. Kea servers can emit a great deal of >> logging detail, provided you have it enabled. With sufficient logging >> enabled, you should see some sort of response from Kea to client packets. >> Even if Kea elects to drop a packet, you should still it's arrival logged >> and an explanation for why it was dropped. >> >> I would suggest, as a starting point that you dial up the logging >> detail. The following logger configuration will give you maximum output to >> stdout (for more information on logging please see the Logging chapter in >> the Kea Admin guide): >> >> >> "Logging": >> { >> "loggers": [ >> { >> "name": "kea-dhcp4", >> "output_options": [ >> { >> "output": "stdout" >> } >> ], >> "severity": "INFO", >> "debuglevel":99 >> } >> ] >> } >> >> I have attached a log excerpt from a Kea 1.1.0 server I configured to use >> MySQL lease storage so you can see what to expect. >> >> >> >> Regards, >> >> Thomas Markwalder >> ISC Software Engineering >> >> >> >> On 03/18/2018 06:02 PM, Kevin Olbrich wrote: >> >> Hi, >> >> I set the following as my lease-db: >> >> "lease-database": { >> "type": "mysql", >> "name": "dc_dhcp", >> "host": "192.168.30.2", >> "user": "dc_dhcp", >> "password": "xxxxxxxxxxxxxx" >> # "type": "memfile", >> # "persist": true, >> # "name": "/tmp/kea-leases4.csv", >> # "lfc-interval": 1800 >> }, >> >> If I use MySQL, no lease is ever created. The server also never answers >> any DHCP request. >> >> Changing from mysql to memfile (commented out code above), everything >> works fine. >> No error is logged, "it just dont work" with mysql. >> >> root@dhcp01:~# kea-dhcp4 -v >> 1.1.0 >> >> Debian Stretch, main repo. >> >> Is this a known issue? >> >> Kind regards, >> Kevin >> >> >> _______________________________________________ >> Kea-users mailing >> [email protected]https://lists.isc.org/mailman/listinfo/kea-users >> >> >> >> _______________________________________________ >> Kea-users mailing list >> [email protected] >> https://lists.isc.org/mailman/listinfo/kea-users >> >> > > _______________________________________________ > Kea-users mailing list > [email protected] > https://lists.isc.org/mailman/listinfo/kea-users > >
_______________________________________________ Kea-users mailing list [email protected] https://lists.isc.org/mailman/listinfo/kea-users
