<div dir="ltr">Hi Tomek,<div><br></div><div>The debian maintainer (Adam) is not responsive. I packaged 1.3.0, and nagged him for 6 months to update the repo. He finally did in January, but he has not integrated any of my fixes for 1.3.0 since January. I have been running my 1.3.0 package in production for 6 months, and asked him repeatedly to give me the permissions to update the repo, and push the packages to stable. I am not sure what I can do... he does not seem to be taking this seriously. What is the next step?</div><div><br></div><div>I will be starting the packaging of 1.4.0 next week. </div><div><br></div><div>Cheers,</div><div>Jason</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 13, 2018 at 11:15 AM, Tomek Mrugalski <span dir="ltr"><<a href="mailto:tomasz@isc.org" target="_blank">tomasz@isc.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">When talking to the Debian maintainer, you may also mention that 1.4.0<br>
is around the corner. Unless we hit something very unexpected, it should<br>
be released this Friday.<br>
<br>
Tomek<br>
<span class=""><br>
On 13/06/2018 16:32, Kevin Olbrich wrote:<br>
> Package version on debian is still 1.1.0 on all branches.<br>
> I sent an email to the maintainer as 1.3.0 is the recommended release<br>
> and 1.1.0 is some kind of "please do not use this anymore"-release.<br>
> <br>
> PS: I am on MariaDB 10.2 on both server and client. This might be the<br>
> problem. I did not fix the problem yet as all leases are static. I will<br>
> look into this the coming weeks.<br>
> <br>
> Kind regards<br>
> Kevin<br>
> <br>
> <br>
> <br>
> 2018-03-19 14:26 GMT+01:00 Jason Guy <<a href="mailto:jguy@cumulusnetworks.com">jguy@cumulusnetworks.com</a><br>
</span>> <mailto:<a href="mailto:jguy@cumulusnetworks.com">jguy@cumulusnetworks.<wbr>com</a>>>:<br>
<span class="">> <br>
> Hi Kevin,<br>
> <br>
> What version of mysql are you using? I have no problems with mysql<br>
> 5.7 (client and server). Also, have you initialized the database?<br>
> <br>
> Finally, I assume you are using version 1.1 because that it the only<br>
> version available on Debian Apt... I am still trying to have the<br>
> maintainer take more of my patches, and push the 1.3 packages to the<br>
> testing repo, but it is not going well. If anyone knows the<br>
> maintainer for this package, or has any advice about how to get more<br>
> traction with the debian maintainer, I would be grateful. I have<br>
> done a lot of work to patch the 1.1 package to become the 1.3<br>
> package, and I am using in my testing. But I would like to make this<br>
> available to all. :)<br>
> <br>
> Cheers,<br>
> Jason<br>
> <br>
> <br>
> On Mon, Mar 19, 2018 at 9:22 AM, Thomas Markwalder <<a href="mailto:tmark@isc.org">tmark@isc.org</a><br>
</span><div><div class="h5">> <mailto:<a href="mailto:tmark@isc.org">tmark@isc.org</a>>> wrote:<br>
> <br>
> Hello Kevin:<br>
> <br>
> Kea is now up to version 1.3.0 with many new features added<br>
> since 1.1.0 so you may wish to consider upgrading. However, Kea<br>
> 1.1.0 should function using MySQL for lease storage. Kea<br>
> servers can emit a great deal of logging detail, provided you<br>
> have it enabled. With sufficient logging enabled, you should<br>
> see some sort of response from Kea to client packets. Even if<br>
> Kea elects to drop a packet, you should still it's arrival<br>
> logged and an explanation for why it was dropped.<br>
> <br>
> I would suggest, as a starting point that you dial up the<br>
> logging detail. The following logger configuration will give<br>
> you maximum output to stdout (for more information on logging<br>
> please see the Logging chapter in the Kea Admin guide):<br>
> <br>
> <br>
> "Logging":<br>
> {<br>
> "loggers": [<br>
> {<br>
> "name": "kea-dhcp4",<br>
> "output_options": [<br>
> {<br>
> "output": "stdout"<br>
> }<br>
> ],<br>
> "severity": "INFO",<br>
> "debuglevel":99<br>
> }<br>
> ]<br>
> }<br>
> <br>
> I have attached a log excerpt from a Kea 1.1.0 server I<br>
> configured to use MySQL lease storage so you can see what to expect.<br>
> <br>
> <br>
> <br>
> Regards,<br>
> <br>
> Thomas Markwalder<br>
> ISC Software Engineering<br>
> <br>
> <br>
> <br>
> On 03/18/2018 06:02 PM, Kevin Olbrich wrote:<br>
>> Hi,<br>
>><br>
>> I set the following as my lease-db:<br>
>><br>
>> "lease-database": {<br>
>> "type": "mysql",<br>
>> "name": "dc_dhcp",<br>
>> "host": "192.168.30.2",<br>
>> "user": "dc_dhcp",<br>
>> "password": "xxxxxxxxxxxxxx"<br>
>> # "type": "memfile",<br>
>> # "persist": true,<br>
>> # "name": "/tmp/kea-leases4.csv",<br>
>> # "lfc-interval": 1800<br>
>> },<br>
>><br>
>> If I use MySQL, no lease is ever created. The server also<br>
>> never answers any DHCP request.<br>
>><br>
>> Changing from mysql to memfile (commented out code above),<br>
>> everything works fine.<br>
>> No error is logged, "it just dont work" with mysql.<br>
>><br>
>> root@dhcp01:~# kea-dhcp4 -v<br>
>> 1.1.0<br>
>><br>
>> Debian Stretch, main repo.<br>
>><br>
>> Is this a known issue?<br>
>><br>
>> Kind regards,<br>
>> Kevin<br>
>><br>
>><br>
>> ______________________________<wbr>_________________<br>
>> Kea-users mailing list<br>
</div></div>>> <a href="mailto:Kea-users@lists.isc.org">Kea-users@lists.isc.org</a> <mailto:<a href="mailto:Kea-users@lists.isc.org">Kea-users@lists.isc.<wbr>org</a>><br>
>> <a href="https://lists.isc.org/mailman/listinfo/kea-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/<wbr>listinfo/kea-users</a><br>
<span class="">>> <<a href="https://lists.isc.org/mailman/listinfo/kea-users" rel="noreferrer" target="_blank">https://lists.isc.org/<wbr>mailman/listinfo/kea-users</a>><br>
> <br>
> <br>
> ______________________________<wbr>_________________<br>
> Kea-users mailing list<br>
</span>> <a href="mailto:Kea-users@lists.isc.org">Kea-users@lists.isc.org</a> <mailto:<a href="mailto:Kea-users@lists.isc.org">Kea-users@lists.isc.<wbr>org</a>><br>
> <a href="https://lists.isc.org/mailman/listinfo/kea-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/<wbr>listinfo/kea-users</a><br>
<span class="">> <<a href="https://lists.isc.org/mailman/listinfo/kea-users" rel="noreferrer" target="_blank">https://lists.isc.org/<wbr>mailman/listinfo/kea-users</a>><br>
> <br>
> <br>
> <br>
> ______________________________<wbr>_________________<br>
> Kea-users mailing list<br>
</span>> <a href="mailto:Kea-users@lists.isc.org">Kea-users@lists.isc.org</a> <mailto:<a href="mailto:Kea-users@lists.isc.org">Kea-users@lists.isc.<wbr>org</a>><br>
> <a href="https://lists.isc.org/mailman/listinfo/kea-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/<wbr>listinfo/kea-users</a><br>
<div class="HOEnZb"><div class="h5">> <<a href="https://lists.isc.org/mailman/listinfo/kea-users" rel="noreferrer" target="_blank">https://lists.isc.org/<wbr>mailman/listinfo/kea-users</a>><br>
> <br>
> <br>
> <br>
> <br>
> ______________________________<wbr>_________________<br>
> Kea-users mailing list<br>
> <a href="mailto:Kea-users@lists.isc.org">Kea-users@lists.isc.org</a><br>
> <a href="https://lists.isc.org/mailman/listinfo/kea-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/<wbr>listinfo/kea-users</a><br>
> <br>
______________________________<wbr>_________________<br>
Kea-users mailing list<br>
<a href="mailto:Kea-users@lists.isc.org">Kea-users@lists.isc.org</a><br>
<a href="https://lists.isc.org/mailman/listinfo/kea-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/<wbr>listinfo/kea-users</a><br>
</div></div></blockquote></div><br></div>